Techstack¶

Operational source:

C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\techstack

This page mirrors the detailed operational tracking for this track so the deployed wiki shows the same score tables as the source TRACKING.md.

Last updated¶

2026-04-29

Scoring model¶

This track uses milestone and feature scorecards.

Score guide:

100 means complete, validated, and stable for current scope
90-99 means strong and working, but still carrying meaningful gaps
75-89 means materially working, but still missing important completeness
50-74 means real foundation exists, major parts are still absent
below 50 means early, partial, or mostly planned

For this code-heavy platform track, 100 requires implementation plus clear runtime or integration evidence.

Evidence sources reviewed¶

C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\techstack\MASTER_PLAN.md
D:\02_Code\33_DraftLint_Backend\README.md
D:\02_Code\33_DraftLint_Backend\TODO.md
D:\02_Code\34_RapidDraft_CADWorkbench_Service\README.md
D:\02_Code\47_NXconnection\README.md
D:\02_Code\47_NXconnection\NATIVE_CPP_HOST_ARCHITECTURE.md
D:\02_Code\47_NXconnection\native\NxLiveHostCpp.cpp
D:\02_Code\47_NXconnection\scripts\build-nx-live-cpp.ps1
D:\02_Code\45_merged_macos_colabui_dfmanim\docs\contracts\collaboration-local-dev.md
D:\02_Code\45_merged_macos_colabui_dfmanim\server\collab_review_store.py
D:\02_Code\45_merged_macos_colabui_dfmanim\server\main.py
D:\02_Code\39_radical_tauri_selfdev\plans\MASTER_PLAN.md
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\docs\06_Infrastructure_Research\_INDEX.md

Current overall score¶

Techstack overall score: 75 / 100

Why the score is not higher: There is now more than generic platform plumbing here: the managed NX live host can drive the visible NX session, the native NX Open C++ host has been brought up as a real kernel-stage prototype, and the RapidDraft collaboration runtime now has product auth, database-backed model/revision/comment/share state, local SQLite dev fallback, and health/readiness signals. The score is not higher because the native host still lacks full drawing-loop parity, section-view automation remains hard, and the collaboration runtime still needs live two-user verification plus durable activity/realtime event delivery.

Milestone scorecard¶

Milestone	Score / 100	Current state	What it helps achieve	Main remaining gap
1. Backend and service map	64	Partial to working	Clarifies what each runtime component is responsible for.	A single end-to-end platform map is still missing, especially across Core collaboration and desktop CAD control.
2. Typed-tool boundary	79	Working	Keeps Studio orchestration and agent actions explicit.	Tool/interface contracts are stronger, but still not fully centralized.
3. CAD desktop service integration	84	Working	Gives the shell live desktop CAD capability through a controllable runtime surface.	The native host has not yet reached drawing-loop parity.
4. Runtime environment stability	74	Foundation exists	Keeps local execution and session targeting predictable.	Collaboration has clearer local/prod env paths now; multiple host modes and NX-specific assumptions still exist.
5. Shared model/data path governance	70	Working foundation	Makes shared stores and provenance manageable.	Collaboration state now has database-backed model documents/revisions/artifacts, but object storage, backups, and one written data contract still need hardening.
6. Diagnostics and hardening	64	Working but incomplete	Makes failures more understandable and easier to recover from.	Health/readiness improved for hosted collaboration; NX section-view associativity and realtime collaboration observability remain brittle.
7. Native NX host migration	58	Foundation exists	Creates the long-term high-access control path for the visible NX session.	Only the kernel commands are native today; review-loop commands are not yet ported.
8. Hosted collaboration runtime	76	Pilot-usable	Lets RapidDraft support real multi-user CAD Drive sharing instead of local-only state.	Needs live two-user production verification, durable backend activity, SSE/WebSocket, backup rehearsal, and clearer non-STEP import routing.

Feature scorecard¶

Feature track	Score / 100	What it helps achieve	Current note
Backend runtime	78	Gives the product a functional service backbone.	Stronger than before: product auth, collab DB, share/access routes, and readiness signals now support the CAD Drive trial.
CAD desktop service	84	Bridges desktop CAD capability into the product.	The managed NX live host now proves real direct session control.
NX live control	68	Lets the agent drive the exact visible NX session instead of detached helpers.	Managed path works; native path is still kernel-stage.
Typed tools	75	Makes AI actions explicit and bounded across transports.	Shared JSON contracts now span more than one host model.
Service contracts	67	Prevents ambiguity between runtime components.	Collaboration contracts are clearer, but one complete platform map is still missing.
Environment portability	62	Makes local setup less brittle.	Local collaboration DB setup and session registration help, but NX-specific assumptions remain.
Diagnostics	63	Makes failures understandable and repairable.	Better than before with health/readiness checks, though section failures and realtime collaboration gaps remain hard.
Platform documentation	67	Helps future maintainers and agents reason about the runtime.	The NX live-host story is now materially documented, not just implicit in code.
Hosted collaboration runtime	76	Supports the current share-with-a-few-people priority.	Stytch/session, DB-backed collaboration store, share links, grants, and local dev docs are in place; live two-user verification and durable eventing are next.

Current headline assessment¶

Techstack now includes two real platform stories: live-control paths into desktop CAD, and a database-backed hosted collaboration runtime for CAD Drive. The current score reflects that both are materially real now, but neither is fully mature: the native NX migration is still incomplete, and the collaboration runtime still needs live two-user verification, durable activity, realtime delivery, and backup/recovery hardening.

Active rollout updates¶

2026-04-29 - Hosted collaboration runtime added to scoring¶

The collaboration share trial makes hosted runtime confidence a first-class Techstack concern this week. The code now has health/readiness endpoints, product session/auth plumbing, database-backed collaboration objects, model access grants, share links, and a local SQLite fallback for full collaboration development.

Highest-value next actions¶

Verify the hosted CAD Drive runtime for today's share: readiness, auth, database, model volume, share links, access grants, comments, and version upload across two browser/user contexts.
Add durable backend activity and SSE/WebSocket delivery after the trusted-share blockers are clear.
Rehearse backup/restore for collaboration state before broader pilots.
Port the review drawing loop from the managed host into the native NX Open C++ host.
Publish one platform map that spans DraftLint, CAD Workbench Service, Studio, NX live control, and RapidDraft Core collaboration.

Sources¶

C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\techstack\MASTER_PLAN.md
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\techstack\TRACKING.md