The program is past the private-build stage. Its current public form includes the seven-book monograph series, v4 public observatory, Registry, TauLib, Publications artifacts, three public white-paper packages, Verify routes, Engage routes, and correction surfaces.
The roadmap is therefore not only about adding more material. It is about making the public object easier to inspect, easier to challenge, and easier to correct.
v4 stabilization
Stabilize the canonical v4 observatory: Discover, Program, Agenda, Corpus, Results, Verify, Impact, and Engage.
Corpus spine
Keep registry entries, aliases, IDs, result links, and publication references aligned as the program evolves.
Agenda surfaces
Keep Core Semantics, the source-pinned Structural Challenge Ledger, Kernel/Model/Reality, and Construction Roadmap synchronized with Corpus, Results, and Verify.
Formalization
Prioritize TauLib coverage for load-bearing kernel claims and public API surfaces that reviewers can audit.
Publication pipeline
Prepare Research Briefings, research notes, errata, and guided tours as durable open-access artifacts.
Inspection routes
Strengthen Verify, Assessment Protocols, AI-Assisted Discovery, prior-art positioning, and discipline-specific inspection routes.
Bibliography & Prior-Art Catalog
Extend bibliography metadata and connect prior-art clusters to the ten Construction Spine steps.
Construction Spine enrichment
Add prior-art and novelty positioning, construction challenges, and answer-shape rationale to each of the ten construction steps.
Core Semantics migration
Complete public terminology migration from Recovery Requirements to Core Semantics while preserving internal recovery/refusal item IDs.
Media package stabilization
Keep the three public packages — Open Research, Theory of Reality, Technical Blueprint — publication-ready and linked from Media, Program, and Publications.
Correction loop
Make changes traceable through release notes, manifests, checksums, and explicit status labels.
The most important roadmap question is not how quickly the program can expand. It is whether every expansion makes the research object more inspectable. Expansion without inspectability would be noise; inspectability without progress would be stasis. The roadmap needs both.
