# ADR-0001: Headless .NET 10 foundation and explicit targets - Date: 2026-10-28 - Status: foundation decisions retained; host-timing decision superseded by [ADR-0002](adr-0002-single-shell-vsa.md) - Scope: repository and application foundation only ## Context This ADR records the original 2026-10-28 Step-01 foundation decision, before the owner's later architectural realignment. At that time the repository contained only its product vision and ignore rules, and the planned hosts were standalone Blazor WebAssembly plus Windows-first MAUI Blazor Hybrid. The dual-host and deferred-host decision is historical and is explicitly superseded by ADR-0002; the platform-neutral foundation, explicit-target and honest-error decisions remain in force. ## Decision 1. Use .NET 10/C# with a single solution under `src`, Core and Application libraries, and unit/integration test projects under `src/tests`. Keep technical documentation in `docs` and manual handoffs in `prompts`. 2. Keep Core platform-neutral and dependency-free. Application depends inward on Core, with only the DI abstractions needed for its composition extension. The concrete DI container belongs only to integration tests in this step. 3. Implement a genuine metadata-selection use case first. Each request supplies its provider identifier and defined target kind. Never infer a kind, default a provider or fall back between simulation, replay and physical hardware. Snapshot registrations, reject ambiguity, and return explicit failures. 4. Do not equate metadata with connection, capability or authorization. Add no transport, driver, command sender, write operation or real provider. 5. **Superseded by ADR-0002:** stage both standalone WASM and Windows-first MAUI Hybrid until Step-05. The owner instead requires one initial Windows-first MAUI Blazor Hybrid Client and two purposeful UI/Components RCLs now. 6. Use the installed .NET 10.0.402 SDK with stable, same-feature-band patch roll-forward only, centralized direct package pins and one VSTest/xUnit stack. Run real tests, without hardware/cloud dependencies. ## Consequences - At the time of this decision there was no interactive application startup command; Step-01A subsequently adds the actual native Client. - The original four purposeful projects are retained and extended by Step-01A with Client/UI/Components. - Synthetic metadata tests prove selection semantics and actual DI composition, not simulation, replay, diagnostics or physical device availability. - Feature-organized Application and UI slices can consume the resolver without owning domain truth. An isolated simulation oracle must not leak into UI paths. - Initial future hardware integration is read-only. Physical programming requires separate authorization/evidence; no selection or simulation approval grants it. - Test tooling uses the SDK's xUnit v2 template family. v2 remains maintained for critical fixes, while new framework features are developed in v3. A future framework migration should be deliberate, not mix VSTest and MTP accidentally. See the [current architecture](architecture.md), [ADR-0002](adr-0002-single-shell-vsa.md) and [build/test policy](build-and-test.md) for current composition and verification.