AutoForge/docs/README.md

53 lines
3.2 KiB
Markdown

# AutoForge documentation
The implemented scope includes the accepted Step-01/Step-01A foundation,
accepted Step-02/Step-02A vehicle-profile metadata, the accepted Step-03
synthetic diagnostic vertical slice with its integrity corrections, the accepted
Step-04/04A/04B synthetic dynamics work, the accepted Step-05/05A/05B
session-owned live dashboard, and the worker-complete Step-06 Imperial-default
display-unit preference (pending manual orchestrator review).
- [Architecture](architecture.md): actual nine-project graph, responsibilities,
route ownership and provider/reference boundaries.
- [Synthetic diagnostics protocol v1](synthetic-diagnostics-v1.md): request and
response envelope, outcomes, validation, logical timing and bounded trace.
- [Synthetic diagnostics protocol v2](synthetic-diagnostics-v2.md): explicit
run/configuration-bound dynamic telemetry while retaining strict v1 static
behavior.
- [Simulation definitions and state](simulation.md): profile binding, module
inventory, fixed-step model, configuration identity, scenario and protocol
boundaries.
- [Live dashboard usage and contracts](live-dashboard.md): configuration limits,
verified bindings, quality/range/freshness, ownership, display-unit
preference/conversions and v1/v2 sample context.
- [ADR-0001: Headless .NET 10 foundation](adr-0001-headless-foundation.md):
historical foundation decisions; dual-shell/deferred-host decision superseded.
- [ADR-0002: Single native shell and feature slices](adr-0002-single-shell-vsa.md):
one Client, two RCLs and 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.
- [ADR-0004: Synthetic diagnostics boundaries](adr-0004-synthetic-diagnostics.md):
provider-neutral ports and explicit non-authentic protocol decision.
- [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,
full solution/test commands and separate native-smoke workflow.
See the [root README](../README.md) for product vision and implementation
status, the [roadmap](../prompts/ROADMAP.md) for future milestones, and the
historical/worker reports for their own execution evidence:
[Step-01](../prompts/Step-01-Report.md),
[accepted Step-01A](../prompts/Step-01A-Report.md),
[Step-02](../prompts/Step-02-Report.md),
[Step-02A](../prompts/Step-02A-Report.md) and
[Step-03 worker report](../prompts/Step-03-Report.md),
[Step-03A corrective worker report](../prompts/Step-03A-Report.md),
[Step-03B corrective worker report](../prompts/Step-03B-Report.md), and
[Step-04 worker report](../prompts/Step-04-Report.md),
[Step-04A corrective worker report](../prompts/Step-04A-Report.md),
[Step-04B corrective worker report](../prompts/Step-04B-Report.md), and
[Step-05A corrective worker report](../prompts/Step-05A-Report.md),
[Step-05B corrective worker report](../prompts/Step-05B-Report.md), and
[Step-06 worker report](../prompts/Step-06-Report.md).
Handoffs are manual; acceptance remains the orchestrator's responsibility.