2026 Timeline (Week-by-Week)

Last Updated: March 23, 2026 - Risk-adjusted rebaseline applied. Validation closure and regression reruns are required before security testing can start. Milestone windows are dependency-driven, not calendar-only commitments.

March 23 Rebaseline Snapshot

This section is authoritative for current sequencing until full timeline reconciliation is finished.

  1. Canonical status source: 00-vision-and-success-criteria.md.

  2. Canonical execution source: 03-phase-plan-p0-p5.md.

  3. Primary distribution path: App Store .bundle.

  4. Active critical dependency: progcont routing reconstruction and downstream validation closure.

  5. Milestone dates are dependency-driven and should not be treated as fixed if blockers remain open.

March 23 Through Q4 2026 Execution Sequence

  1. Close current validation blocker and release-gate prerequisites.

  2. Complete .bundle assembly and submission-readiness artifacts.

  3. Advance phase gates only after blocker closure and documented acceptance criteria.

  4. Keep P2+ dates conditional on P1 gate completion.

Active Rebaseline Windows (March 23)

Milestone

Active window

Gate note

M2

Apr 7-Apr 21, 2026

Full validation closure gate complete (Step 0-12 + regression reruns)

M2.5

May 19-May 26, 2026

Integration baseline stabilized

M3

May 31, 2026

Design gate closes on validated baseline

M4

Jun 1-Sep 30, 2026

Security testing and audit window

M5

Oct 1-Nov 30, 2026

App Store submission window

Hard gate: security testing does not begin until full validation completion evidence is present for all active configurations.

Historical Context

Sections below remain useful as historical planning records, but may contain date assumptions superseded by the March 23 rebaseline.

Note: This plan is a working draft. Some technical details (exact file provenance, build parity, vendor timelines, pricing, and Autodesk product capabilities) may need verification as we inventory the full legacy tree and validate behavior in modern environments.

Schedule philosophy

We run a weekly cadence with:

  • 1 weekly update

  • 1 build artifact whenever meaningful progress lands

  • explicit phase gates (P1→P2→P3→P4)

  • Q4 dedicated to stabilization + partner demo readiness

This timeline is written as a plan, not a promise. The biggest schedule swing factor is P2 parity closure.

Budget Milestones (January 27, 2026)

When

Item

Cost

Notes

Q1 2026

WiX Toolset 4.x

$0

FREE - selected over $500-2000 alternatives

Q2 2026

Code Signing (OV)

$200/yr

Sectigo - needed before GA release

Jun 2026

AutoCAD 2026 License

$1,865

Required for P3 testing

Sep 2026

Autodesk Dev Network

$500/yr

App Store access

Nov 2026

Code Signing (EV)

$400/yr

Optional upgrade for instant trust

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

Macro timeline (quarters)

Q1 2026 (Jan–Mar): P1 execution + distribution strategy pivot 🔧

  • ✅ Build artifacts archived (Completed 2026-01-16)

  • ✅ Installer analysis complete, WiX decision documented (Completed 2026-01-20)

  • ✅ isDcc decompilation of v3.60 InstallShield → setup.rul (4,163 lines)

  • ✅ Cost analysis complete - WiX (FREE) selected over $500-2000 alternatives 💰

  • ✅ Proxmox VM infrastructure - Tower converted, Tailscale + LegacyUpdate.net (Jan 27) 🖥️

  • ✅ Multi-OS testing COMPLETE (Feb 10) - XP/Vista/Win7 all passed, 9 bugs documented

  • ✅ Win10 testing COMPLETE (Feb 13-17) - Win10x32 fully working, Win10x64 fully working (after Wow6432Node COM fix Feb 17)

  • ✅ Total Uninstall inventory validated - 152 files, 5.5 MB as WiX payload source

  • ✅ Auto-config script created - Configure-ConstructiVision.ps1 handles AutoCAD integration

  • ⏹️ P1 InstallShield Sprint ABORTED (Feb 13) - Low ROI, proceeding directly to WiX

  • ❌ WiX Installer Development ABORTED (Feb 28) - Distribution pivoted to VLX .bundle format for Autodesk App Store

  • ✅ P0 Automated Validation Sprint (Mar 1-4): AutoIT test automation built, 18 bugs found and 17 fixed (Bugs 22-38), P0 Steps 0-2 PASS on 5/6 VM configs

  • ✅ Architecture Discovery (Mar 1): VLX was compiled from source code not in repo — progcont routing mismatch between VLX and source mode

  • ⚠️ Win10 PB11 ABANDONED (Bug 37): WinHelp() compiled into VLX, Win10 removed WinHlp32.exe — TB11 source-mode only for Win10

  • Active Mar 5+: P0 Steps 3-6, progcont reconstruction (5-10 day dev effort), then Steps 7-12

  • Target Mar 31: Distribution GA release → Revised: P0 baseline completion (Mar 24-31)

Q2 2026 (Apr—Jun): Validation closure + integration and design transition

  • P1–P2 sub-dialog feature validation (59 manual workflows from doc 31)- Comprehensive parity validation (45-tb11-parity-test-plan) — 92 tests, 7 gates:

    • Weeks 17–18: G1 (Menu Routing) + G2 (Dialog Appearance) + G7 (Infrastructure)

    • Weeks 19–20: G3 (Field Functionality) + G4 (Data Persistence / XRecord)

    • Weeks 21–22: G5 (Drawing Operations) + G6 (Print & Output)

    • Weeks 23–24: G8 (Regression sweep) + scorecard close-out

    • Week 25: M2 parity gate decision (≥95% of 76 testable items PASS/PARTIAL)- VLX compilation from validated source (deferred until P1 stable)

  • .bundle packaging for Autodesk App Store

  • NanoCAD 25 + AutoCAD 2026 compatibility testing

  • Lock “2026 baseline” when parity achieved

  • Rebaselined target window: Apr 7-Apr 21 for M2 gate close, then May 19-May 26 for M2.5 integration closure

Q3-Q4 2026 (Jul—Nov): P3 modern AutoCAD compatibility, security testing, and ADN prep

  • Run cleanly on AutoCAD 2026

  • Modern packaging (.bundle format) + UI adjustments 🆕

  • Regression suite runs on target

  • Join ADN Developer tier (~$500/year for technical support) 🆕

  • Prepare Autodesk App Store submission (screenshots, docs, EULA) 🆕

  • Request early AutoCAD 2027 access 🆕

  • Sunset VM-based distribution model (replace with direct install) 🆕

  • Security testing window rebaselined: Jun 1-Sep 30, 2026 (M4)

Q4 2026 (Nov—Dec): P4 hybrid cloud + dual distribution + demo hardening

  • Subscription foundations + artifact pipeline

  • Autodesk App Store submission & review (Oct 1-Nov 30 submission window; allow 2 cycles = 4 weeks) 🆕

  • Dual distribution channels live: 🆕

    • Direct download (WiX MSI installer) - primary

    • Autodesk App Store - secondary

  • Stabilization, performance, “demo polish”

  • White Cap demo readiness (target)

  • World of Concrete readiness by end of 2026 (stable, rehearsed, packaged)

Suggested 2026 week plan (high-level)

Weeks 1–4 (Jan, Target 2026-01-31): P1 foundation + installer rebuild sprint start 🔧

  • ✅ Build artifacts (v3.60 + v11) archived and documented (Completed 2026-01-16)

  • ✅ Installer analysis complete, WiX decision documented (Completed 2026-01-20) 🔧

  • ✅ isDcc decompilation produced setup.rul (4,163 lines of InstallScript)

  • ✅ Proxmox VM migration complete (2026-01-27) 🖥️

    • Tower computer converted to Proxmox VM (only running legacy copy)

    • Tailscale VPN + LegacyUpdate.net configured

    • Greater Seattle Concrete remote access in progress

    • Replaces VirtualBox on dev laptop (limited resources, no backup)

  • Week 4 (Jan 21-27): v3.60 installer rebuild from setup.rul 🔧

    • InstallShield 5.x environment setup in XP VM

    • RUL import, compilation, first test run

    • Pre/post install diff with WinDiff

    • Bug fixes (registry profile detection, AutoCAD running check)

  • Target 2026-01-27: v3.60 installer compiles and runs in XP VM ✅

  • Target 2026-02-14: Greater Seattle Concrete remote access validated

  • Target 2026-03-31: UI screenshot capture and menu tree building

Weeks 5–8 (Feb, Target 2026-02-28): Installer sprint continuation + compatibility testing 🔧

  • Week 5 (Jan 27 - Feb 3): v7.0 installer reverse engineering 🔧

    • Inspect existing v7.0/v11 desktop installation

    • Compare v3.60 vs v7.0 files, registry, paths

    • Document target state specification

    • Draft v7.0 installer script (may not compile)

  • Week 6 (Feb 3-10): Nero Analysis (Lessons Learned) 🔍

    • Analyzed Nero 1.0 installer to validate isDcc workflow

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

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

    • Documented lesson: Decompiler useful for understanding, not rebuilding

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

  • Week 7 (Feb 10-16): Multi-OS Testing ✅ MAJOR SUCCESS

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

    • ✅ 8 installer bugs cataloged with root cause analysis (profile detection = #1 bug)

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

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

    • ✅ Bug 2 (UAC) downgraded to Low — works fine as Administrator

    • See: CV360-Installation-Analysis.md (archived)

  • Week 8 (Feb 10-13): Win10 Testing + P1 Sprint Decision ✅ COMPLETE

    • ✅ Win10 32-bit: Full stack working (AutoCAD 2000 + CV + auto-config script)

    • ✅ Win10 64-bit: Tested via Total Uninstall restore — COM automation fails with AC2000

    • ✅ Auto-configuration script created: scripts/Configure-ConstructiVision.ps1

    • ✅ P1 InstallShield Sprint ABORTED — Low ROI on .rul recompilation

    • ✅ Legacy installer validated through Win10x32 — no rebuild needed

    • ✅ Total Uninstall restore validated as deployment method

    • 🚧 Decision: Proceed directly to WiX using validated components

    • Next: 64-bit AutoCAD purchase (Mar 2026) to enable Win10x64 support

  • Target 2026-02-10: ✅ Multi-OS compatibility validated (XP/Vista/Win7) — AHEAD OF SCHEDULE

  • Target 2026-02-17: Win10 32-bit eval VM operational

  • Target 2026-02-24: v11 bridge installer prototype; comprehensive menu testing

Weeks 9–13 (Feb 13 - Mar, Target 2026-03-31): Bug fixing sprint + P0 validation + .bundle pivot 🔧

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

    • WiX project setup started but distribution strategy pivoted

    • Decision (Feb 28): WiX ABORTED → VLX .bundle format for Autodesk App Store

  • Week 10-11 (Feb 20 - Mar 3): TB11 Source-Mode Bug Fixing Sprint 🚧

    • ✅ csv.lsp replaces csvmenu.lsp as Startup Suite entry (1:1 VLX swap)

    • ✅ acaddoc.lsp per-document loader for source-mode TB11

    • ✅ Rewrote progopts, slope_dlg, btch_dlg to match golden VLX behavior

    • ✅ 18 bugs found and 17 fixed (Bugs 22-38)

    • ✅ Architecture Discovery (Mar 1): CSV.VLX compiled from source not in repo — progcont routing mismatch

  • Week 12 (Mar 3-7): P0 Automated Validation Sprint ✅

    • ✅ AutoIT scripts created: cv-p0-step0.au3, cv-p0-step1.au3, cv-p0-step2.au3

    • ✅ OCR comparison pipeline for screenshot verification

    • ✅ P0 Steps 0-2 PASS on 5/6 VM configs (Configs A-E)

    • ✅ VM 108 (Win10 x32) and VM 109 (Win10 x64) deployed and tested

    • ✅ Win10 PB11 ABANDONED (Bug 37 — WinHelp). TB11 source-mode only.

    • ❌ Config F (VM 109 x64) Step 2 FAIL — Bug 38 (ACAD path → stale acad2000 subdir). Fixed, awaiting retest.

    • Test plan status (Mar 5): 48% complete (85/177 items). P0 at 27% (17/62). Full plan 92 items remaining.

  • Week 13 (Mar 10-14): P0 Steps 3-6 (Drawing & Dialog Verification) 🚧

    • Retest VM 109 (Config F) Step 2 after Bug 38 fix

    • P0 Step 3: Open CSB001.dwg via command line (4 configs)

    • P0 Step 4: csv command on panel drawing (4 configs)

    • P0 Step 5: Open CSBsite1.dwg with XRef resolution (4 configs)

    • P0 Step 6: csv on site drawing (4 configs)

  • Weeks 14-15 (Mar 17-28): Progcont Reconstruction 🚧 CRITICAL PATH

    • Reverse-engineer VLX’s progcont routing logic (md_dlg.lsp/md_dlg.dcl)

    • Implement progcont reading in source-mode csv.lsp

    • This is development, not testing — estimated 5-10 working days

    • Must complete before Steps 7-12 can proceed on Config D (TB11)

  • Weeks 15-16 (Mar 24-31): P0 Steps 7-12 + Graduation 🚧

    • Steps 7-12: Individual menu items with progcont routing (6 steps × 4 configs = 24 tests)

    • Graduation: Full cv-menu-validation.au3 across all 4 configs

    • Depends on: Progcont reconstruction completing successfully

  • Target 2026-03-31 (exponential): P0 baseline complete, begin P1 workflows

  • Target 2026-03-31 (linear): P0 baseline complete (tight — progcont is the swing factor)

Weeks 17–20 (Apr, Target 2026-04-30): P1-P2 Workflow Validation + VLX/Bundle + Parity Gates G1–G4 🔧

Parity test execution follows 45-tb11-parity-test-plan:

  • Week 17 (Apr 1-7): G1 Menu Routing (17 progcont paths) + G7 Infrastructure (startup, SFSP, profile)

  • Week 18 (Apr 8-14): G2 Dialog Appearance (visual parity against PB11 golden screenshots)

  • Week 19 (Apr 15-21): G3 Field Functionality (inputs, toggles, dropdowns, calculations)

  • Week 20 (Apr 22-28): G4 Data Persistence (NOD XRecord read/write round-trip)

  • Week 17 (Apr 1-7): P1 Critical Workflows (11 items)

    • P-02, P-03: Panel creation with dimensions and openings

    • P-13: Weld connections (wc_dlg — 5 pages, 615 controls)

    • P-14/P-15: Pick points and brace points

    • P-20, P-21: Full-feature panel + edit existing panel

    • B-01/B-02, B-07: Batch print/redraw + materials list

    • E-01/E-02: Engineering export (Dayton/Meadow-Burke CSV)

    • S-01, U-06: Site drawing + registration

  • Week 18 (Apr 8-14): P2 High Workflows + Demo Tests (13 items)

    • P-04/P-05: Doors and blockouts

    • P-10, P-22: Chamfer + copy panel

    • S-02, S-05: Grid lines (208 edit boxes) + attach panels

    • E-04/E-05, U-03: Import .pan/.pnl + WC Edit

    • Demo test: Full 8-step end-to-end on 4 platforms

  • Week 19 (Apr 15-21): VLX Compilation + NanoCAD/AC2026 Compat (9 items)

    • Compile TB11 source → csv.vlx (deferred until P1 stable)

    • NanoCAD 25 compatibility testing (5 items)

    • AutoCAD 2026 source-mode testing on VM 109

  • Week 20 (Apr 22-30): .bundle Packaging + Distribution GA 🔧

    • Package .bundle for Autodesk App Store

    • Test .bundle installation on clean VM

    • Create NanoCAD distribution package (LSP-only)

    • Uninstaller testing (5 platforms)

    • Documentation, deployment guide, release candidate

  • Target 2026-04-15 (exponential): Distribution GA release (.bundle format)

  • Target 2026-04-30 (linear): Distribution GA release (.bundle format)

  • Decision Point: GA release achieved → proceed to modern AutoCAD compat (P3)

Weeks 21–26 (May—Jun, Target 2026-06-30): P3 Modern AutoCAD Compatibility

  • AutoCAD 2020+ compatibility testing (2020, 2022, 2024, 2026)

  • Update deprecated AutoCAD API calls where needed

  • Modern packaging refinements (.bundle format)

  • UI/menu adaptations for modern AutoCAD ribbon interface

  • Performance + reliability improvements

  • Acquire AutoCAD 2026 license ($1,865) if not already done

  • Regression suite runs across all platforms

  • Lock “2026 baseline” when parity achieved

Weeks 27—34 (Jul—Aug): P3 exit + ADN prep + App Store submission

  • Join ADN Developer tier (~$500/year for technical support)

  • Prepare Autodesk App Store submission (screenshots, docs, EULA)

  • Request early AutoCAD 2027 access

  • Sunset VM-based distribution model (replace with direct install)

  • P3 complete criteria met

Weeks 35—38 (Sep): P4 foundations

  • P4 architecture and entitlement MVP begins

  • begin demo storyboard for partners

Weeks 39—46 (Oct—Nov): P4 build-out + demo hardening

  • artifact pipeline MVP

  • upgrade/update experience

  • White Cap demo rehearsal cycles

Weeks 47—52 (Dec): Freeze + polish + readiness

  • stability and bug fixes

  • demo scripts locked

  • release candidate build packaged

  • “ready by end of 2026” checkpoint

Date realism note (World of Concrete)

World of Concrete 2027 is scheduled for January 19—21, 2027 (Education: Jan 18—21). The intent is:

  • Demo freeze by December 15, 2026 to ensure stable, demo-ready product

  • Rehearsal cadence: monthly demos starting July 2026, weekly starting October 2026