AutoForge/docs/README.md

28 lines
1.6 KiB
Markdown

# AutoForge documentation
The implemented scope is the accepted Step-01/Step-01A foundation plus
Step-02's validated synthetic vehicle-profile metadata slice. Step-02 worker
and Step-02A corrective verification are complete; manual orchestrator
acceptance of Step-02 remains pending.
- [Architecture](architecture.md): actual seven-project graph, Client/UI/RCL
ownership, feature-slice organization, target selection and profile catalog.
- [ADR-0001: Headless .NET 10 foundation](adr-0001-headless-foundation.md):
historical foundation decisions, with dual-shell/deferred-host superseded.
- [ADR-0002: Single native shell and feature slices](adr-0002-single-shell-vsa.md):
one Client, two RCLs and the modular-monolith composition.
- [ADR-0003: Strict profile interchange v1](adr-0003-profile-interchange-v1.md):
immutable profile revisions, strict versioned JSON and in-memory catalog.
- [Vehicle-profile schema v1](vehicle-profile-schema-v1.md): identity/revision,
explicit unknowns, capability/provenance contracts, JSON policy and usage.
- [Build and test](build-and-test.md): SDK/MAUI/Windows/WebView2 prerequisites,
exact commands, rendered/native verification, evidence and limitations.
See the [root README](../README.md) for product vision and implementation status,
the [roadmap](../prompts/ROADMAP.md) for future milestones, the
[Step-01 historical report](../prompts/Step-01-Report.md), the
[accepted Step-01A report](../prompts/Step-01A-Report.md) and
[Step-02 worker report](../prompts/Step-02-Report.md) and
[Step-02A corrective report](../prompts/Step-02A-Report.md) for execution evidence.
Manual acceptance remains the orchestrator's responsibility.