2.3 KiB
2.3 KiB
AutoForge documentation
The implemented scope includes the accepted Step-01/Step-01A foundation, accepted Step-02/Step-02A vehicle-profile metadata, and the Step-03 synthetic diagnostic vertical slice with the Step-03A integrity/verification corrections. Worker completion/verification is reported separately from manual orchestrator acceptance; Step-03 is not accepted until that review.
- Architecture: actual nine-project graph, responsibilities, route ownership and provider/reference boundaries.
- Synthetic diagnostics protocol v1: request and response envelope, outcomes, validation, logical timing and bounded trace.
- Simulation definitions and state: profile binding, module inventory, service declarations, per-session DTC state and deterministic faults.
- ADR-0001: Headless .NET 10 foundation: historical foundation decisions; dual-shell/deferred-host decision superseded.
- ADR-0002: Single native shell and feature slices: one Client, two RCLs and modular-monolith composition.
- ADR-0003: Strict profile interchange v1: immutable profile revisions, strict versioned JSON and in-memory catalog.
- ADR-0004: Synthetic diagnostics boundaries: provider-neutral ports and explicit non-authentic protocol decision.
- Vehicle-profile schema v1: identity/revision, explicit unknowns, capability/provenance contracts, JSON policy and usage.
- Build and test: SDK/MAUI/Windows/WebView2 prerequisites, full solution/test commands and separate native-smoke workflow.
See the root README for product vision and implementation status, the roadmap for future milestones, and the historical/worker reports for their own execution evidence: Step-01, accepted Step-01A, Step-02, Step-02A and Step-03 worker report, Step-03A corrective worker report. Handoffs are manual; acceptance remains the orchestrator's responsibility.