RapidDraft Core¶
Operational source:
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\rapiddraft-core
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:
100means complete, validated, and stable for current scope90-99means strong and working, but still carrying meaningful gaps75-89means materially working, but still missing important completeness50-74means real foundation exists, major parts are still absent- below
50means early, partial, or mostly planned
For this hybrid product-definition track, a score of 100 requires product definition plus
clear implementation ownership plus active source evidence from repos or delivered assets.
Evidence sources reviewed¶
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\rapiddraft-core\MASTER_PLAN.mdC:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\docs\01_RapidDraft\_INDEX.mdC:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\docs\00_Meta\Projects_Map.mdD:\02_Code\45_merged_macos_colabui_dfmanimD:\02_Code\45_merged_macos_colabui_dfmanim\docs\contracts\collaboration-local-dev.mdD:\02_Code\45_merged_macos_colabui_dfmanim\web\src\components\CollaborationWorkspace.tsxD:\02_Code\45_merged_macos_colabui_dfmanim\server\collab_review_store.pyC:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\cad-intelligence\handover\260408_railway-one-service-simplification.mdC:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\cad-intelligence\handover\260408_rule-driven-review-preparation-pipeline-plan.md
Current overall score¶
RapidDraft Core overall score: 85 / 100
Why the score is not higher:
RapidDraft Core now has a much clearer runtime identity and a materially stronger pilot-facing
workflow than it did in March. Collaboration is no longer only a future positioning claim: CAD
Drive has a dedicated workspace, database-backed model documents, share links, pinned comments,
replies, revisions, and version-origin chips. app.rapiddraft.ai is now the Stytch-gated product
domain, pilots.rapiddraft.ai redirects there, and hosted DraftLint runs through the IONOS
detector gateway with scan limits. The score is still held back by live external verification,
durable backend activity, realtime event delivery, carry-forward UX, and runtime-verification
discipline.
Milestone scorecard¶
| Milestone | Score / 100 | Current state | What it helps achieve | Main remaining gap |
|---|---|---|---|---|
| 1. Review-companion scope definition | 95 | Strong and documented | Keeps the product boundary understandable for pilots and engineering work. | Needs continued discipline as more modes share the same shell. |
| 2. Drawing-analysis lane definition | 64 | Partial and distributed | Brings drawing validation into the Core story. | Still less integrated than the model-review and DFM paths. |
| 3. DFM-backed review flow | 86 | Materially working | Connects manufacturability intelligence to the customer-facing review story. | Hosted/runtime confidence must keep pace with branch velocity. |
| 4. Issue and review collaboration surface | 82 | Share-ready pilot MVP | Makes RapidDraft a collaboration product rather than a one-shot checker. | CAD Drive now supports share links, pinned comments/replies, markdown, revisions, and short-poll refresh. Backend email access grants exist, but the visible pilot share flow is being simplified around links first. Durable activity, realtime events, carry-forward/re-pin, and broader non-STEP routing remain open. |
| 5. Implementation ownership map | 82 | Clear enough for current phase | Prevents confusion about which repo is the real Core runtime. | Historical repo boundaries still need careful explanation in some docs. |
| 6. Pilot-ready product baseline | 89 | Materially working | Makes Core presentable for real pilot conversations and workflows. | Ready for a small trusted collaboration share on app.rapiddraft.ai, with Stytch auth and hosted DraftLint live. Still needs live two-person validation before broader pilot rollout, and the production launcher simplification is still queued in Railway. |
Feature scorecard¶
| Feature track | Score / 100 | What it helps achieve | Current note |
|---|---|---|---|
| Change review | 61 | Gives users a concrete review-centric entry point. | Still meaningful, but less mature than the DFM-backed review lane. |
| Drawing analysis | 54 | Broadens Core beyond model review. | Present in the product story, but not yet the strongest active runtime lane. |
| Issue tracking | 72 | Makes decisions traceable over time. | Pinned comments/replies, status, assignee, resolve/reopen, markdown, deep links, and revision-origin tags now exist; durable activity and carry-forward behavior are still missing. |
| DFM review | 86 | Connects design review to manufacturability. | Now one of the clearest product strengths in the integrated shell. |
| Collaboration surface | 82 | Reinforces the collaboration-first positioning. | CAD Drive is now a real shareable workspace for a small trusted group: upload/open, share link, comment, reply, upload v2, and inspect versions. Invite/admin UI should not be foregrounded until it is deliberately reintroduced. |
| Pilot-facing workflow clarity | 91 | Makes the product legible for customer and pilot conversations. | The clearest current external story is CAD Drive collaboration first, Drawing Analysis/DraftLint second, Expert/DFM as the deeper layer. A production visibility flag now enforces this shape once Railway serves the queued deploy. |
Current headline assessment¶
RapidDraft Core is now a real integrated product surface, not just a product-definition layer
spread across older repos. The merged shell, shared app/pilots runtime story, stronger DFM
workflow, and dedicated CAD Drive collaboration workspace moved this track meaningfully forward.
The next gap is not ownership confusion. It is making the collaboration share trial feel calm and trustworthy for real people while preserving runtime trust and clear rollout language.
Active rollout updates¶
2026-04-29 - CAD Drive becomes the current Core pilot wedge¶
The Core score moved from 79 to 85 because collaboration moved from planned/positioned to a
usable product surface. The active repo now has a dedicated CAD Drive workspace, product sign-in,
database-backed model documents/revisions/tickets, share links, owned/shared access foundations,
and version-aware comments. This is enough for a small trusted share today, but not yet enough to
call the collaboration system mature.
2026-04-29 - Hosted app auth, DraftLint, and public-surface cleanup¶
app.rapiddraft.ai is now the public app domain for the newer Railway runtime, with Stytch
existing-user auth replacing Cloudflare Access. pilots.rapiddraft.ai redirects there. DraftLint
is live in gateway mode through the IONOS detector gateway and scan limits are active.
The repo also contains a production visibility layer that hides pinned standards, Batch Mode, and
Design Review from public builds while keeping them in local development. This keeps the deployed
app from looking like an internal mode launcher. The change is committed as 1af25e4, but Railway
was still queued at last verification, so document it as pushed/local-build-validated rather than
live.
Highest-value next actions¶
- Validate the deployed CAD Drive flow with two real browser/user contexts before sending links.
- Share the collaboration feature today with a few trusted people and collect focused feedback on upload, sign-in, share links, comments, versions, and DraftLint scan.
- Patch only collaboration share blockers this week; defer deeper DFM, bounded edits, and Studio convergence unless they block the trial.
- Maintain explicit separation between implemented, locally validated, deployed, and runtime-verified when documenting product readiness.
Sources¶
C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\rapiddraft-core\MASTER_PLAN.mdC:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\00_Project_Management_n_skills\01_tracks\rapiddraft-core\TRACKING.md