Architecture planning.
This folder turns the research and design documents into an implementation architecture shape.
It does not replace:
docs/research/, which records why options were selected or rejecteddocs/design/, which owns subsystem concepts, boundaries, and terminology- future implementation plans, which will own concrete tasks and code work
- Architecture Roadmap: dependency order for stabilizing the architecture before crate design or implementation planning.
- Architecture Decisions: compact decision notes for why the current architecture shape was selected.
- Engine Architecture: logical runtime components, ownership, and dependency direction before crate boundaries are chosen.
- Runtime Pipeline Architecture: request, process, effect, commit, observation, semantic, and resolution flow through the logical component structure.
- Crate Boundary Architecture: candidate Rust workspace and crate boundaries derived from authority ownership and dependency direction.
- Project Conventions: stable Rust workspace, dependency, ID, error, diagnostics, serialization, async, and accelerator policies that should be fixed before implementation details.
- Implementation Plan: high-level phased build order, implementation principles, and phase exit conditions.
- Implementation Execution Contract: mandatory agent workflow, public API guardrails, review gates, and phase completion checks for long-running implementation runs.
Recommended reading order:
roadmap.md -> ADR.md -> engine.md -> runtime-pipeline.md -> crates.md -> project-conventions.md -> implementation-plan.md -> implementation-execution-contract.md
Planned later:
- detailed phase-local plans as implementation begins.