Written narrative
Roadmap pages are valuable when they separate what exists from what is intended. Each phase should list artifacts, evidence, failure modes, and claim limits before the next phase is allowed.
Six phases
A prototype is not teleodynamic until split, merge, add, retire, and no-op decisions are resource-gated, locally justified, appended to immutable logs, and visible in phase plots.
Build smallest first. Do not begin with the biggest model.
| Phase | Mechanism | Evidence / warning |
|---|---|---|
| Phase 0: Minimal Substrate | Fixed structure, fast loop only. | Evidence: confusion clusters and uncertainty spikes. Warning: do not claim teleodynamic structure yet. |
| Phase 1: Resource Economy | Synthetic gain, decay, viability floors, action costs, blocked-action telemetry. | Actions block when resource is low and re-enable after predictive success. |
| Phase 2: Slow Loop Integration | Split and no-op operators. | No-op wins when no affordable split improves cost. |
| Phase 3: Operator Expansion | Merge, retire, and one domain-specific operator. | Complexity plateaus after utility drops. |
| Phase 4: Phase Detection | Error-complexity trajectories, action rates, resource utilization, no-op dominance. | Prune candidates can be explained by dependency and utility traces. |
| Phase 5: Auditability | Export slow-loop traces with triggers, candidates, resource deltas, expected gains, and final justifications. | A third party can reconstruct why a representation was added or retired. |
The roadmap is strict because vague “adaptive” claims are not enough.
A prototype is not teleodynamic until split, merge, add, retire, and no-op decisions are resource-gated, locally justified, appended to immutable logs, and visible in phase plots.
Deep route polish
The roadmap visual turns the research idea into staged public milestones with do-not-claim limits at each phase.
Roadmap pages are valuable when they separate what exists from what is intended. Each phase should list artifacts, evidence, failure modes, and claim limits before the next phase is allowed.
A phase can introduce a trace logger, but it should not claim broad agency until evaluation, review, and resource closure evidence exist.
| Focus | What to inspect |
|---|---|
| Phase artifact | What should exist after the phase. |
| Acceptance evidence | What should be tested or inspected. |
| Claim limit | What must not be said yet. |
Treat future roadmap items as planned work unless the archive and changelog show delivery.