Milestones Dashboard

Executive summary of all project milestones from P0 through P5, with target dates, exit criteria, and current status.

March 23 Rebaseline

Use this precedence for milestone interpretation:

  1. 00-vision-and-success-criteria.md for canonical strategy/status.

  2. 03-phase-plan-p0-p5.md for execution and gate sequencing.

  3. This dashboard for milestone rollup reporting.

Execution notes:

  1. Primary distribution path is App Store .bundle.

  2. WiX/MSI is contingency-only and not the active primary path.

  3. Current milestone sequencing is dependency-driven by open validation/routing closure gates.

Milestones Table

ID

Phase

Start Date

Target Date

Exit Criteria (Definition of Done)

Owner

Status

Blockers / Dependencies

M1

P0

Jan 1, 2026

✅ Jan 20, 2026

ConstructiVision runs in VM on legacy machine; dry run successful in AutoCAD 2000; Upgraded Jan 27: Proxmox VM + Tailscale

@chadw

🟢 Green

None

M1.5

P1 Analysis

Jan 1, 2026

✅ Jan 20, 2026

Build artifacts archived; installer analysis complete; architecture decisions documented

@chadw

🟢 Green

None

M1.6

P1 Infra

Jan 21, 2026

✅ Jan 29, 2026

Proxmox VM migration; Tailscale remote access; SSH configured (ssh xp-103, ssh xp-111); GSC customer access ready

@chadw

🟢 Green

None 🆕

M1.7

P1 Parity

Apr 1, 2026

May 19-May 26, 2026

Doc 45 parity scorecard satisfied: ≥95% of 76 testable items PASS/PARTIAL; G1 + G4 zero-FAIL; DFMEA-036–042 dispositioned; master scorecard published

@chadw

⏳ Not Started

Depends on M1.6 closure and progcont routing reconstruction completion. See 45-tb11-parity-test-plan.

M2

P1 Installer

Feb 13, 2026

May 19-May 26, 2026

Validation closure gate complete and distribution GA candidate ready; M1.7 parity scorecard satisfied; full validation set closed with First Pass + Reviewed evidence; regression reruns complete across active configs

@chadw

🟡 YELLOW

App Store .bundle is primary path. M1.7 parity gate is prerequisite. Critical dependency remains progcont routing reconstruction plus Step 0-12 closure and regression reruns. Security testing cannot start before this gate is complete.

M2.5

P1 Integration

Apr 22, 2026

May 19-May 26, 2026

Integration and quality validation complete; output quality verified on x32 and x64; stable baseline for design phase

@chadw

⏳ Not Started

Depends on M2 closure and zero unresolved core regressions

M3

P2 Design

May 1, 2026

May 31, 2026

UI/UX review complete; code refactoring done; documentation suite complete

@chadw

⏳ Not Started

Depends on M2.5 completion and stable validated baseline

M4

P3 Security

Jun 1, 2026

Sep 30, 2026

Security audit passed; multi-version testing (2024, 2025, 2026); ADN membership active

@chadw

⏳ Not Started

Entry gate: full validation completion evidence, regression clear state, and DFMEA-linked high severity closure

M4.5

P3 Security

Sep 1, 2026

Sep 30, 2026

.bundle format migration complete; ready for code signing

@chadw

⏳ Not Started

Depends on M4 closure

M5

P4 Release

Oct 1, 2026

Nov 30, 2026

App Store submission complete; awaiting review

@chadw

⏳ Not Started

Depends on M4.5 completion; ADN membership; EULA/docs ready

M6

P4 Release

Nov 1, 2026

Dec 31, 2026

EV code signing applied; dual distribution live (direct + App Store); owner demo complete

@chadw + Web Dev

⏳ Not Started

Depends on M5 and staffing availability

M7

P5

Jan 1, 2027

Jun 30, 2027

AI enhancements: auto-fill forms + “EZ Button” panel book generation with integrated tests

TBD (AI/Dev)

⏳ Not Started

Depends on M6; staffing TBD

M8

Release

Dec 1, 2026

Dec 15, 2026

White Cap partner/demo rollout ready; World of Concrete 2027 (Jan 19–21) demo-ready by Dec 15 freeze

@chadw

🟡 Yellow

Depends on M6; marketing plan TBD

Marketing/Product Research Operating Checkpoint (March 23)

  1. 38-marketing-product-research-sprint.md is the active output pack for messaging, competitive framing, and research backlog.

  2. Marketing claims should be reviewed against 00/03 before external use.

  3. Product research priorities should be linked to milestone risk and dependency language.

  4. Operational execution docs: 24-go-to-market-partner-pilot-plan.md and 25-marketing-sales-enablement-pack.md.

Status Legend

Symbol

Meaning

🟢 Green

On track; no blockers

🟡 Yellow

At risk; minor blockers or timeline pressure

🔴 Red

Blocked; cannot proceed without intervention

⏳ Not Started

Awaiting upstream completion

Key Dependencies

  • M1 → M1.5: P0 baseline → Analysis & Setup phase

  • M1.6 → M1.7: Infrastructure complete → Parity validation gate (45-tb11-parity-test-plan)

  • M1.7 → M2: Parity scorecard satisfied → Validation closure and GA candidate readiness

  • M1.5 → M2: Analysis complete → Installer Development (4 weeks)

  • M2 → M2.5: Validation closure gate → Integration & Bug Fixing

  • M2.5 → M3: Integration complete → Design Improvement phase

  • M3 → M4: Design complete + full validation closure evidence → Security & Testing phase

  • M4 → M4.5: Security audit → .bundle migration

  • M4.5 → M5: .bundle complete → App Store submission

  • M5 → M6: App Store submitted → Final Release & Demo

  • M6 → M7: Release complete → Web/AI development (P5)

  • M6 → M8: M8 freeze is now at risk if M6 slips; use M5 output as minimum demo-safe package for Dec 15, 2026 freeze

Critical Path (Updated March 4, 2026)

The critical path narrative below is historical and should be interpreted through the March 23 rebaseline above.

WiX ABORTED (Feb 28). Distribution pivoted to VLX .bundle format for Autodesk App Store. P0 automated validation sprint (Mar 1-4): 18 bugs found/fixed (Bugs 22-38), P0 Steps 0-2 PASS on 5/6 VM configs. Win10 PB11 ABANDONED (Bug 37 — WinHelp incompatible). TB11 source-mode only for Win10.

M1 (P0) ✅ Jan 1-20, 2026
  ↓
M1.5 (Analysis & Setup) ✅ Jan 1-20, 2026
  ↓
M1.6 (Proxmox Infrastructure) ✅ Jan 21-29, 2026
  ├── Tower → Proxmox VM migration
  ├── Tailscale VPN configured
  └── SSH configured (Bitvise) → 6 VMs
  ↓
P1 Analysis Phase ✅ COMPLETE Feb 13, 2026
  ├── ✅ CV3.60 + AC2000 installed on XP, Vista, Win7 (all pass)
  ├── ✅ 8 installer bugs cataloged (root cause: profile detection)
  ├── ✅ Complete v11 installer specification (41 files, exact registry)
  ├── ✅ 9 monitoring files captured and cross-analyzed
  ├── ✅ Win10 32-bit: FULL STACK WORKING (Feb 13)
  ├── ✅ Auto-config script: Configure-ConstructiVision.ps1
  ├── ✅ Win10 64-bit: FULL STACK WORKING (Feb 17 — after Wow6432Node COM fix)
  └── ❌ P1 InstallShield sprint: ABORTED (low ROI)
  ↓
v3.60 Source Recovery ✅ COMPLETE Feb 16, 2026
  ├── ✅ 12 missing AutoLISP modules recovered from v3.60 archive
  ├── ✅ 3 crash paths fixed (wd_dlg, wc_dlg, wall_dlg) — light-tested OK
  ├── ✅ TB11-01x32 build: 134 → 195 files
  ├── ✅ Nightly deployment pipeline (Git sparse checkout + junction)
  └── ✅ 4 VMs auto-pulling at 22:00 (108, 109, 201, 202)
  ↓
Win10 x64 COM Fix ✅ COMPLETE Feb 17, 2026
  ├── ✅ 103 AutoCAD CLSIDs copied to Wow6432Node
  ├── ✅ 104 IAcad COM Interfaces copied to Wow6432Node
  ├── ✅ 6 ProgIDs copied to Wow6432Node
  ├── ✅ Shortcuts recreated (Plot Style Table Wizard, Add-A-Plotter Wizard)
  ├── ✅ Project Files search path added for ConstructiVision
  └── ✅ csv command runs, drawings loading successfully
  ↓
Bug Fixing & Quality Validation 🚧 ACTIVE Feb 17 - Mar 4
  ├── ✅ 18 bugs found and 17 fixed (Bugs 22-38)
  ├── ✅ AutoIT P0 validation automation (Steps 0-2)
  ├── ✅ OCR comparison pipeline for screenshot verification
  ├── ✅ P0 Steps 0-2 PASS on 5/6 VM configs (OCR verified)
  ├── ✅ Win10 PB11 ABANDONED (Bug 37 — WinHelp)
  ├── 🚧 Bug 38 (x64 ACAD path) fixed, awaiting retest
  └── 🚧 Progcont routing reconstruction (VLX/source mismatch)
  ↓
WiX Installer ❌ ABORTED Feb 28, 2026
  └── Pivoted to VLX .bundle for Autodesk App Store
  ↓
M2 (Distribution GA) 🚧 Mar 4 - Mar 31, 2026 — REVISED
  ├── Week 12-13: Complete P0 validation (Step 3+)
  ├── Week 13-14: .bundle packaging prototype
  ├── Week 14: Alpha testing + GA release
  └── ⚠️ M1.7 Parity Gate (doc 45): ≥95% of 76 items PASS/PARTIAL before M2 closes
  ↓
M2.5 (Integration & Quality Validation) ⏳ Apr 1 - Apr 30, 2026
  ├── Output quality validation on x32 and x64
  ├── .bundle installer tested on both architectures
  ├── Progcont routing reconstruction for source-mode
  └── Stabilization & testing
  ↓
M3 (Design Improvement) → May 1 - May 30, 2026
  ↓
M4 (Security & Testing) → Jun 1 - Sep 30, 2026
  ↓
M4.5 (.bundle Migration) → Sep 1 - Sep 30, 2026 (parallel with M4)
  ↓
M5 (App Store Submit) → Oct 1 - Nov 30, 2026
  ↓
M6 (Final Release & Demo) → Nov 1 - Dec 31, 2026
  ↓
M8 (Demo Ready) → Dec 1 - Dec 15, 2026 (freeze date for WOC 2027)

Timeline Impact: P1 Analysis COMPLETE (8 weeks). v3.60 source recovery COMPLETE (Feb 16). Win10 x64 COM fix COMPLETE (Feb 17). WiX ABORTED (Feb 28) — pivoted to .bundle distribution. P0 automated validation sprint (Mar 1-4): 18 bugs found, 17 fixed, 5/6 configs PASS. Critical discovery: VLX was compiled from source code that doesn’t exist in repo — progcont routing reconstruction required. M2 target (Mar 31) at risk — .bundle packaging not yet started.

March 23 Rebaseline Milestone Windows

Use these windows as the active planning baseline for sequence and dependencies:

  1. M2: Apr 7-Apr 21, 2026

  2. M2.5: May 19-May 26, 2026

  3. M3: May 31, 2026

  4. M4: Jun 1-Sep 30, 2026

  5. M5: Oct 1-Nov 30, 2026

Hard gate: M4 security testing cannot start until M2 validation closure is complete for all active configs, including Step 0-12 completion and regression reruns with First Pass + Reviewed evidence pairs.


Risk Adjustments

Original Risk (Now Mitigated) ✅

If source code parity cannot be closed via patch (M2 blocker)

Update: Installer modernization (WiX) addresses this by providing stable deployment platform before design work.

Installer Development Complexity — RESOLVED Feb 13 ✅

Status: 🟢 RESOLVED — Win10 compatibility validated, WiX development starting

Issue (CLOSED): Multiple compatibility layers broken by Windows security evolution

  1. isDcc Decompilation Failure: → BYPASSED — proceeding directly to WiX

  2. Windows Security Improvements: → RESOLVED: Works as Administrator on XP/Vista/Win7/Win10x32

  3. Cross-Version Incompatibility: → VALIDATED: Legacy installer works on XP/Vista/Win7, CV works on Win10x32 with auto-config

  4. 64-bit COM Failure:RESOLVED Feb 17: Total Uninstall placed COM registrations in wrong hive; Wow6432Node fix applied (103 CLSIDs, 104 Interfaces, 6 ProgIDs)

Feb 17 Resolution Summary:

  • ✅ CV3.60 + AC2000 installed successfully on XP, Vista, Win7, Win10x32, AND Win10x64

  • ✅ Win10x32 full stack working: AC2000 + CV + COM automation

  • Win10x64 full stack working: AC2000 + CV + COM automation (after Wow6432Node registry fix)

  • ✅ Auto-config script created: Configure-ConstructiVision.ps1

  • ✅ P1 InstallShield sprint ABORTED (.rul recompilation has low ROI — proceed to WiX directly)

  • Both x32 and x64 builds crash-free — program runs and loads drawings

  • 🚧 Bug fixing and output quality validation in progress

  • 🔜 Alpha/beta testing planned for March

Impact: M2 timeline rebaselined to Apr 7-Apr 21 due to dependency closure risk. WiX is contingency-only; App Store .bundle remains primary.

Plan (Feb 17 → Mar 31):

  • Week 9 (Feb 13-20): WiX project setup, import file inventory (152 files, 5.5 MB)

  • Week 10-11: Core functionality, auto-config integration, code signing

  • Week 12: Bug fixing + output quality validation (x32 and x64)

  • Week 13: Alpha/beta testing with internal resources

  • Week 14: Polish, docs, GA release

If AutoCAD 2026 access is delayed (M4 blocker):

  • Consider building on latest available version (2025) with notes on compatibility

  • Defer M4 to Q1 2027 if access unavailable by Aug 2026

New Risk: App Store Rejection

If Autodesk App Store rejects submission (M5):

  • Mitigation: Launch with direct download only (primary channel)

  • Impact: No timeline delay, but reduced market reach

  • Allow 2 review cycles (4 weeks) built into schedule


Budget Summary (January 27, 2026)

Installer & Signing Costs

Item

Cost

Notes

WiX Toolset 4.x

$0

FREE - MIT license ✅

Code Signing (OV)

$200/year

Sectigo - builds SmartScreen reputation

Code Signing (EV)

$400/year

Optional - instant trust, hardware token

Selected: WiX + OV Signing = $200/year total

Cost Savings vs Alternatives

Alternative

Cost

Savings with WiX

InstallShield 12

~$500

$500 saved

InstallShield 2024

~$2,000+/year

$2,000+ saved

Advanced Installer

~$500/year

$500 saved

See: installer-modernization-decision.md for full cost analysis. (archived)


P1 Workstreams (Current Focus - Updated Feb 9, 2026)

As of 2026-02-13, the following initiatives are now active (revised after Win10 compatibility testing):

Analysis & Setup Phase (Jan 21 - Feb 13) ✅ COMPLETE

Week 1 (Jan 21-27): Legacy Environment Baseline ✅ COMPLETED

  • Set up InstallShield 5.x in XP VM, import setup.rul

  • VM snapshots + WinDiff analysis

  • Document bug findings (profile detection, AutoCAD check)

  • Deliverables: Baselined environment, diff report, documented bugs

Week 2 (Jan 27 - Feb 3): Gap Analysis ✅ COMPLETED

  • ⚠️ No original v7.0 .ins file exists — must analyze differences

  • Inspect existing v7.0/v11 installation on desktop machine

  • Compare v3.60 paths to v7.0 actual state

  • Deliverables: Complete installer spec for WiX, file/registry manifest

Week 3 (Feb 3-10): Nero Analysis (COMPLETED - Lessons Learned)

  • Analyzed Nero 1.0 installer to validate isDcc workflow

  • Critical Discovery: isDcc bytecode output (10,031 lines) won’t compile

  • Solution Found: InstallShield wizard approach generates clean 606-line .rul that compiles

  • ✅ Documented lesson: Decompiler useful for understanding, not for rebuilding

  • Root Cause Identified: Windows security improvements (UAC, SmartScreen, code signing) broke cross-version compatibility; each OS needs targeted installer or WiX migration

  • Schedule Impact: VLX recompilation deferred; multi-OS testing delayed 2 weeks

  • Deliverables: Nero study report, isDcc vs wizard comparison, Windows compatibility root cause analysis

Week 4-5 (Feb 10-13): Multi-OS Testing + Win10 Validation — ✅ COMPLETE

  • CV3.60 + AC2000 installed on XP, Vista, Win7, AND Win10x32 — no UAC issues as Administrator

  • 8 installer bugs cataloged with root cause analysis and severity ratings

  • 9 monitoring files captured (Total Uninstall + Inctrl5 + Regshot × 3 VMs)

  • Complete v11 installer specification — 41 files, exact registry entries, 6 “do NOT” rules

  • ✅ Proxmox snapshots: cv360-installed-20260210 on all VMs

  • Win10 32-bit FULL STACK WORKING (Feb 13): AC2000 + CV + COM automation

  • Auto-config script created: Configure-ConstructiVision.ps1

  • ⚠️ Win10 64-bit: AC2000 runs but COM automation fails (needs 64-bit AutoCAD)

  • Decision Point Feb 13: ✅ Pass confirmed on all target OSes. 64-bit needs modern AutoCAD.

  • Deliverables: ✅ CV360-Installation-Analysis.md, 9 monitoring data files, v11 installer spec, auto-config script

Week 6-8 (Feb 10-13): P1 InstallShield Sprint — ❌ ABORTED (LOW ROI)

  • ✅ setup.rul decompilation attempted via isDcc

  • ✅ Wizard approach tested with Nero 1.0 project

  • Decision: .rul recompilation has low ROI — proceed directly to WiX

  • ❌ VLX recompilation PASSED — existing VLX files work on Win10x32

  • ❌ v11 bridge installer PASSED — WiX will be the bridge

  • Rationale: Win10 compatibility validated without InstallShield changes; WiX provides modern MSI with better long-term maintainability

  • Impact: No timeline delay — WiX development starts NOW (Feb 13)

WiX Installer Development Phase (Feb 13 - Mar 31) 🚧 NOW ACTIVE

  • Week 9 (Feb 13-20): WiX Foundation

    • WiX project setup and initial MSI structure

    • Import file list from Total Uninstall inventory (152 files, 5.5 MB)

    • Basic installer UI and branding

  • Week 10 (Feb 20-27): Core Functionality

    • AutoCAD prerequisite detection

    • File deployment to Program Files

    • Post-install PowerShell script execution (auto-config)

    • Registry configuration via Configure-ConstructiVision.ps1

  • Week 11 (Feb 27-Mar 6): Advanced Features

    • Uninstall support with clean removal

    • Process detection with Windows Restart Manager

    • Code signing certificate integration

    • Error handling and rollback

  • Week 12 (Mar 6-13): 64-bit AutoCAD Testing

    • Purchase 64-bit AutoCAD license (2010+ required)

    • Install on Win10x64 test VM (VM 109)

    • Test CV VLX loading and execution

  • Week 13 (Mar 13-20): Alpha/Beta Testing

    • Deploy WiX installer to internal resources

    • Document all bugs and issues found

    • Test on clean machines

  • Week 14 (Mar 20-31): Polish & GA Release

    • Fix bugs found in testing

    • MSI validation tests

    • User documentation, IT deployment guide

  • Target: Mar 31, 2026 - WiX installer GA complete + 64-bit AutoCAD validated

Integration & 64-bit Phase (Apr 1 - Apr 30) ⏳ AFTER WIX

  • Week 15 (Apr 1-7): 64-bit AutoCAD Compatibility Testing

    • Test ConstructiVision VLX with 64-bit AutoCAD 2010+

    • Determine if VLX recompilation required for x64

    • Document compatibility issues and breaking changes

  • Week 16 (Apr 8-14): WiX x64 Installer

    • Create x64-specific MSI variant

    • Test on Win10x64 with 64-bit AutoCAD

    • Address any 64-bit-specific registry paths

  • Week 17 (Apr 15-21): Bug Fixing Sprint

    • Address issues found in alpha/beta testing

    • Fix hard errors from 64-bit testing

    • Regression testing on XP/Vista/Win7/Win10x32/Win10x64

  • Week 18 (Apr 22-30): Stabilization & Testing

    • Integration testing with both installers

    • Performance testing and optimization

    • Documentation updates

    • Decision Point Apr 30: Stable baseline achieved → proceed to Design phase

  • Target: Apr 30, 2026 - Stable baseline for design improvements

Windows Compatibility Testing ✅ COMPLETE (Feb 13)

Platform Compatibility Matrix:

Platform

AutoCAD 2000

ConstructiVision

COM Automation

Status

Windows XP

✅ Works

✅ Works

✅ Works

Fully Supported

Windows Vista

✅ Works

✅ Works

✅ Works

Fully Supported

Windows 7

✅ Works

⚠️ pcAnywhere bug

✅ Works

Limited

Win10 32-bit

✅ Works

✅ Works

✅ Works

Fully Supported

Win10 64-bit

✅ Runs

✅ Works

❌ Fails

Needs 64-bit AutoCAD

Result: >95% success on 32-bit platforms. 64-bit requires modern AutoCAD (planned March).

UI Documentation (Design Improvement Phase)

  • Capture complete menu/command hierarchy

  • Build user input tree for modernization planning

  • Screenshot all dialog boxes and workflows

  • Note: UI/visual changes deferred to M3 (May); April focuses on functional compatibility only


Last Updated: 2026-03-04 (WiX ABORTED → .bundle pivot; P0 Steps 0-2 PASS on 5/6 configs; 18 bugs found, 17 fixed; Win10 PB11 abandoned; Bug 38 fix awaiting retest) Next Review: Week of 2026-03-10 (VM 109 retest + P0 Step 3 + .bundle prototype)