RapidDraft Core¶
Operational source:
/Users/adeelyj/Library/CloudStorage/OneDrive-Personal/100_Knowledge/203_TextCAD/01_Product_Project_Management/00_Project_Management_n_skills/01_tracks/rapiddraft-core
This page is the local wiki mirror of the operational MASTER_PLAN.md and TRACKING.md.
Last updated¶
2026-06-18
Current overall score¶
RapidDraft Core overall score: 85 / 100
The score stays at 85 after the June 18 documentation refresh. The Theegarten QA/DraftLint/Agent
demo sprint is materially captured, and the source registry now makes the active repo/branch map
clearer. The score does not move up because later measure/edit work was investigation only, and
the remaining product gaps are still live-user validation, durable activity, realtime delivery,
comment carry-forward, and runtime-verification discipline.
Current posture¶
RapidDraft Core is the customer-facing product line for model review, manufacturability feedback, pilot-facing engineering workflows, and the shared review shell.
Current implementation evidence lives across:
/Users/adeelyj/code/rapiddraft/45_co2/rapiddraft_utumpitch/Users/adeelyj/code/rapiddraft/42_merged/rapiddraft_utumpitch- Theegarten and local-AI wiki surfaces under
/Users/adeelyj/code/rapiddraft wiki/wiki-rapiddraft - DraftLint adapter/source repos under
/Users/adeelyj/code/local ai server setup
Milestone scorecard¶
| Milestone | Score / 100 | Current state | Main remaining gap |
|---|---|---|---|
| Review-companion scope definition | 95 | Strong and documented | Keep discipline as more modes share the same shell. |
| Drawing-analysis lane definition | 64 | Partial and distributed | Still less integrated than model-review and DFM paths. |
| DFM-backed review flow | 86 | Materially working | Hosted/runtime confidence must keep pace with branch velocity. |
| Issue and review collaboration surface | 82 | Share-ready pilot MVP | Durable activity, realtime events, carry-forward/re-pin, broader non-STEP routing. |
| Implementation ownership map | 82 | Clear enough for current phase | Historical repo boundaries still need careful explanation. |
| Pilot-ready product baseline | 89 | Materially working | Needs live two-person validation and continued deployment clarity. |
Feature scorecard¶
| Feature track | Score / 100 | Current note |
|---|---|---|
| Change review | 61 | Meaningful but less mature than the DFM-backed review lane. |
| Drawing analysis | 54 | Present in product story, but not yet the strongest runtime lane. |
| Issue tracking | 72 | Pinned comments/replies/status/deep links exist; durable activity and carry-forward remain open. |
| DFM review | 86 | One of the clearest product strengths in the integrated shell. |
| Collaboration surface | 82 | CAD Drive is share-ready for a small trusted group, not yet a mature suite. |
| Pilot-facing workflow clarity | 91 | CAD Drive, Drawing Analysis/DraftLint, and Expert/DFM are the clearest current story. |
Active updates¶
2026-06-18 - GitHub activity and source-of-truth audit completed¶
The last month of GitHub/repo activity is captured in the operational audit:
01_tracks/rapiddraft-core/plans/260618_github-activity-docs-audit/README.md
The durable source map is:
04_playbooks/RAPIDDRAFT_REPO_SOURCE_REGISTRY.md
2026-06-18 - Measure and CAD edit investigation remains future work¶
Exact measurement is feasible using the existing canonical face/edge selection model plus OCCT worker patterns. CAD edit should be preview-and-accept candidate generation, not direct in-place editing. This does not raise the score yet because no endpoint, UI mode, or accepted edit workflow has shipped.
2026-06-03 - Theegarten QA demo branch reached testing-deploy smoke stage¶
The .io testing service has the Theegarten QA/DraftLint/Agent path, with QA inspection reporting
separated from model/component BOM artifacts. Remaining gaps are demo polish, authenticated smoke,
final screenshots, and export/approval polish.
Highest-value next actions¶
- Validate deployed Agent Home-to-Expert with a signed-in browser session.
- Validate CAD Drive with two real browser/user contexts before broader sharing.
- Keep the repo/source registry current before the next development sprint.
- Share the collaboration feature with a few trusted people and collect focused feedback.
- Preserve separation between implemented, locally validated, deployed, and runtime-verified.
Sources¶
- Operational Core master plan and tracker.
01_tracks/rapiddraft-core/plans/260618_github-activity-docs-audit/README.md04_playbooks/RAPIDDRAFT_REPO_SOURCE_REGISTRY.md