Skip to content

Techstack

Operational source:

/Users/adeelyj/Library/CloudStorage/OneDrive-Personal/100_Knowledge/203_TextCAD/01_Product_Project_Management/00_Project_Management_n_skills/01_tracks/techstack

This page is the local wiki mirror of the operational MASTER_PLAN.md and TRACKING.md.

Last updated

2026-06-18

Current overall score

Techstack overall score: 80 / 100

The score stays at 80. June 18 improved operating clarity, not runtime capability: the repo source registry now maps app, website, wiki, DraftLint, and local-AI work; the wiki-source consolidation findings are parked; and the user preference is recorded that wiki publishing edits should happen in the local wiki-rapiddraft checkout.

Current posture

Techstack owns the shared runtime and service boundary behind RapidDraft Core and Studio: backend services, typed tool integration, desktop child services, runtime paths, live CAD control, hosted collaboration, DraftLint gateway, local-AI/Knowledge, and platform-level plumbing.

Milestone scorecard

Milestone Score / 100 Current state Main remaining gap
Backend and service map 66 Partial to working One complete platform map still missing.
Typed-tool boundary 79 Working Tool/interface contracts not fully centralized.
CAD desktop service integration 84 Working Native host lacks drawing-loop parity.
Runtime environment stability 76 Foundation exists Multiple host modes and assumptions remain.
Shared model/data path governance 78 Working foundation Off-platform copies and restore rehearsal still need hardening.
Diagnostics and hardening 74 Working but incomplete Realtime collaboration observability, local-AI vision routing, restore drills.
Native NX host migration 58 Foundation exists Review-loop commands not yet ported.
Hosted collaboration runtime 76 Pilot-usable Needs live two-user verification and durable eventing.
Local AI knowledge/runtime 65 Useful platform layer Multimodal LiteLLM route and product-grade Knowledge still need work.

Feature scorecard

Feature track Score / 100 Current note
Backend runtime 79 Product auth, collab DB, readiness, and DraftLint gateway support hosted flows.
CAD desktop service 84 Managed NX live host proves direct session control.
NX live control 68 Managed path works; native path still kernel-stage.
Typed tools 75 Shared JSON contracts span more than one host model.
Service contracts 69 Collaboration and detector responsibilities clearer; platform map still missing.
Environment portability 64 Better local/prod paths, but NX-specific assumptions remain.
Diagnostics 72 Health/readiness, backups, and YOLO scripts help; restore/realtime gaps remain.
Platform documentation 77 Backup, DraftLint/CVAT, and repo-source docs are stronger.
Hosted collaboration runtime 76 Share links/grants/session/store are in place; eventing and verification next.
Local AI / knowledge layer 65 Fedora stack healthy; product behavior should move to custom RapidDraft Knowledge.

Active updates

2026-06-18 - Repo source registry and wiki-boundary audit captured

The source registry is:

04_playbooks/RAPIDDRAFT_REPO_SOURCE_REGISTRY.md

The wiki consolidation findings are parked in:

01_tracks/techstack/plans/260618_wiki-source-consolidation-audit/README.md

For now, wiki publishing edits should use:

/Users/adeelyj/code/rapiddraft wiki/wiki-rapiddraft

OneDrive remains the operational project-management source for plans, trackers, decisions, lessons, handovers, and playbooks.

2026-06-03 - DraftLint YOLO gateway and CVAT Nuclio stabilization

CVAT keeps native Nuclio AI Tools. RapidDraft and DraftLint use draftlint-gateway.rapiddraft.ai. Detector 26 is the preferred Specialist Ensemble. The weak point is now local-AI vision routing, not YOLO serving.

Highest-value next actions

  1. Fix DraftLint local-AI vision routing with a real multimodal LiteLLM route.
  2. Keep the detector-default fallback hardening clean and deployable.
  3. Verify hosted CAD Drive with two user/browser contexts.
  4. Harden Railway startup against transient Postgres private-network failures.
  5. Revive/refactor localai-rag into RapidDraft Knowledge.
  6. Execute backup/restore rehearsals before broader pilots.
  7. Keep RAPIDDRAFT_REPO_SOURCE_REGISTRY.md current when sources/branches change.
  8. Resume the wiki-source consolidation audit later.

Sources

  • Operational Techstack master plan and tracker.
  • 04_playbooks/RAPIDDRAFT_REPO_SOURCE_REGISTRY.md
  • 01_tracks/techstack/plans/260618_wiki-source-consolidation-audit/README.md