Remove versioned roadmap from Passepartout docs

All version numbers stripped from roadmap across all brain documents:
- passepartout-economics.org: v0.x.x version table → phase-name-only table,
  v1.0.0 → 'neurosymbolic maturity', versioned text references → capability
  descriptions. Retained phase names (Phase 0-7) and line estimates as they
  describe capabilities, not version milestones.
- competitive-analysis-2026-05.org: version references removed
- time-estimates.org: v0.4.0 → 'initial state', v1.0.0 → 'neurosymbolic maturity'
- native-org-knowledge-base.org: v0.8.0-v0.9.0 → capability-based target
This commit is contained in:
Hermes
2026-05-23 06:24:20 +00:00
parent 43c8c886e9
commit 3f38e87f4f
4 changed files with 34 additions and 34 deletions

View File

@@ -4,9 +4,9 @@
#+title: Development Velocity and Timeline Estimates
#+filetags: :passepartout:economics:development:timeline:velocity:
At the observed velocity (v0.4.0 to v0.7.2 in a single session), the agent writes code and the symbolic engine verifies it at a cycle measured in minutes. The bottleneck is not coding speed — it is LLM API latency, ACL2 verification time, and human review of the 5% of edge cases Screamer flags.
At the observed velocity (initial TUI through to production readiness in a single session), the agent writes code and the symbolic engine verifies it at a cycle measured in minutes. The bottleneck is not coding speed — it is LLM API latency, ACL2 verification time, and human review of the 5% of edge cases Screamer flags.
**To v1.0.0 (neurosymbolic maturity, ~4,500 lines):** ~80 cycles, 3-5 weeks, ~2-3 hours of human review.
**To neurosymbolic maturity (~4,500 lines):** ~80 cycles, 3-5 weeks, ~2-3 hours of human review.
**To [[file:self-driving-lisp-machine.org][self-driving Lisp Machine]] (Logos + Stoa hardware, +~6,000 lines):** ~60 cycles, 2-4 weeks. The microcode must be loaded onto physical hardware and benchmarked, adding seconds per cycle.