Key building blocks in the shipped architecture:
| Block | Responsibility | Primary callers | Must not own |
|---|---|---|---|
|
Select tracked files, assign section ownership, detect overlaps, and build the deterministic bundle plan. |
|
Rendering, artifact verification, or note governance. |
|
Render section outputs, spans, structured plans, hashes, and token counts through the kernel-owned proof path. |
|
File selection policy or adapter-specific output shapes. |
|
Write and read canonical manifest truth, including artifact metadata, trust metadata, and derived review exports. |
|
Live workspace inspection or note mutation. |
|
Validate, verify, and extract bundles against manifest truth and checksum evidence. |
|
MCP policy decisions or oracle diagnostics. |
|
Parse, validate, score, and maintain the durable cognition graph. |
|
Proof-path rendering or artifact truth. |
|
Expose scoped live workspace inspection, diagnostics, and policy-backed operator guidance. |
|
Promotable proof claims. |
|
Expose oracle/reference diagnostics and parity comparison. |
Expert diagnostics, parity tests |
Ordinary |
See Implementation Reference
for the deeper contributor map and
Internal API Contract for
stable seams such as RenderEngine, StructuredRenderPlan,
TokenizerProvider, and ScannerPipeline.
Rule
Ordinary bundle, validate, verify, and extract flows do not rely on the oracle seam. That separation is a runtime rule, not just a documentation preference.
Dependency Direction
The ordinary proof path flows from planning to rendering to manifest materialization to validation, verification, and extraction. Live workspace tooling may inspect or preview that path, but it does not become artifact truth. Notes may inform a bundle through configured inputs and gates, but note quality is still conditional knowledge rather than proof.