You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Issue #12 is staged into isolated contracts, communication, host, and orchestration slices so the Uno workbench can stay presentation-only.";
10
+
"Issue #12 builds on the #11 foundation contracts and stages host and orchestration work behind isolated runtime slices so the Uno app stays presentation-only.";
11
11
privateconststringDeterministicProbePrompt=
12
12
"Summarize the runtime foundation readiness for a local-first session that may require approval.";
13
13
privateconststringDeterministicClientStatusSummary="Always available for in-repo and CI validation.";
Copy file name to clipboardExpand all lines: docs/ADR/ADR-0003-vertical-slices-and-ui-only-uno-app.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ We will use these architectural defaults for implementation work going forward:
32
32
-`DotPilot.Core` for contracts, typed identifiers, and public slice interfaces
33
33
-`DotPilot.Runtime` for provider-independent runtime implementations and future host integration seams
34
34
3. Feature code must be organized as vertical slices under `Features/<FeatureName>/...`, not as shared horizontal `Services`, `Models`, or `Helpers` buckets.
35
-
4. Epic `#12` starts with a `RuntimeFoundation` slice that sequences issues `#22`, `#23`, `#24`, and `#25` behind a stable contract surface before live Orleans or provider integration.
35
+
4. Epic `#11` establishes the shared `ControlPlaneDomain` and `RuntimeCommunication` slices, and epic `#12` builds on that foundation for runtime-host and orchestration work.
36
36
5. CI-safe agent-flow verification must use a deterministic in-repo runtime client as a first-class implementation of the same public contracts, not a mock or hand-wired test double.
37
37
6. Tests that require real `Codex`, `Claude Code`, or `GitHub Copilot` toolchains may run only when the corresponding toolchain is available; their absence must not weaken the provider-independent baseline.
38
38
@@ -81,7 +81,7 @@ CI does not guarantee those toolchains, so the repo would lose an honest agent-f
81
81
82
82
- The Uno app gets cleaner and stays focused on operator-facing concerns.
83
83
- Future slices can land without merging unrelated feature logic into shared buckets.
84
-
- Contracts for `#12` become reusable across UI, runtime, and tests.
84
+
- Contracts from epic `#11` become reusable across UI, runtime, and tests before epic `#12` begins live runtime integration.
85
85
- CI keeps a real provider-independent verification path through the deterministic runtime client.
Copy file name to clipboardExpand all lines: docs/Architecture.md
+43-14Lines changed: 43 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Architecture Overview
2
2
3
-
Goal: give humans and agents a fast map of the active `DotPilot` solution, the current `Uno Platform` shell, the workbench foundation for epic `#13`, the Toolchain Center for epic `#14`, and the vertical-slice runtime foundation that starts epic `#12`.
3
+
Goal: give humans and agents a fast map of the active `DotPilot` solution, the current `Uno Platform` shell, the foundation contracts from epic `#11`, the workbench foundation for epic `#13`, the Toolchain Center for epic `#14`, and the runtime-host backlog that builds on those contracts in epic `#12`.
4
4
5
5
This file is the required start-here architecture map for non-trivial tasks.
6
6
@@ -10,15 +10,14 @@ This file is the required start-here architecture map for non-trivial tasks.
10
10
-**Presentation boundary:**[../DotPilot/](../DotPilot/) is now the presentation host only. It owns XAML, routing, desktop startup, and UI composition, while non-UI feature logic moves into separate DLLs.
11
11
-**Workbench boundary:** epic [#13](https://github.com/managedcode/dotPilot/issues/13) is landing as a `Workbench` slice that will provide repository navigation, file inspection, artifact and log inspection, and a unified settings shell without moving that behavior into page code-behind.
12
12
-**Toolchain Center boundary:** epic [#14](https://github.com/managedcode/dotPilot/issues/14) now lives as a `ToolchainCenter` slice. [../DotPilot.Core/Features/ToolchainCenter](../DotPilot.Core/Features/ToolchainCenter) defines the readiness, diagnostics, configuration, action, and polling contracts; [../DotPilot.Runtime/Features/ToolchainCenter](../DotPilot.Runtime/Features/ToolchainCenter) probes local provider CLIs for `Codex`, `Claude Code`, and `GitHub Copilot`; the Uno app surfaces the slice through the settings shell.
13
+
-**Foundation contract boundary:** epic [#11](https://github.com/managedcode/dotPilot/issues/11) is represented through [../DotPilot.Core/Features/ControlPlaneDomain](../DotPilot.Core/Features/ControlPlaneDomain) and [../DotPilot.Core/Features/RuntimeCommunication](../DotPilot.Core/Features/RuntimeCommunication). These slices define the shared agent/session/tool model and the `ManagedCode.Communication` result/problem language that later runtime work reuses.
13
14
-**Runtime foundation boundary:**[../DotPilot.Core/](../DotPilot.Core/) owns issue-aligned contracts, typed identifiers, and public slice interfaces; [../DotPilot.Runtime/](../DotPilot.Runtime/) owns provider-independent runtime implementations such as the deterministic test client, toolchain probing, and future embedded-host integration points.
14
-
-**Domain slice boundary:** issue [#22](https://github.com/managedcode/dotPilot/issues/22) now lives in `DotPilot.Core/Features/ControlPlaneDomain`, which defines the shared agent, session, fleet, provider, runtime, approval, artifact, telemetry, and evaluation model that later slices reuse.
15
-
-**Communication slice boundary:** issue [#23](https://github.com/managedcode/dotPilot/issues/23) lives in `DotPilot.Core/Features/RuntimeCommunication`, which defines the shared `ManagedCode.Communication` result/problem language for runtime public boundaries.
16
-
-**First implementation slice:** epic [#12](https://github.com/managedcode/dotPilot/issues/12) is represented locally through the `RuntimeFoundation` slice, which sequences issues `#22`, `#23`, `#24`, and `#25` behind a stable contract surface instead of mixing runtime work into the Uno app.
15
+
-**Embedded runtime backlog boundary:** epic [#12](https://github.com/managedcode/dotPilot/issues/12) now builds on the epic `#11` foundation contracts through the `RuntimeFoundation` slice instead of treating issues `#22` and `#23` as runtime-host work.
17
16
-**Automated verification:**[../DotPilot.Tests/](../DotPilot.Tests/) covers API-style and contract flows through the new DLL boundaries; [../DotPilot.UITests/](../DotPilot.UITests/) covers the visible workbench flow, Toolchain Center, and runtime-foundation UI surface. Provider-independent flows must pass in CI through deterministic or environment-agnostic checks, while provider-specific checks can run only when the matching toolchain is available.
18
17
19
18
## Scoping
20
19
21
-
-**In scope for the current repository state:** the Uno workbench shell, the new `DotPilot.Core` and `DotPilot.Runtime` libraries, the runtime-foundation slice, and the automated validation boundaries around them.
20
+
-**In scope for the current repository state:** the Uno workbench shell, the `DotPilot.Core` and `DotPilot.Runtime` libraries, the epic `#11` foundation-contract slices, the runtime-foundation planning surface for epic `#12`, and the automated validation boundaries around them.
22
21
-**In scope for future implementation:** embedded Orleans hosting, `Microsoft Agent Framework`, provider adapters, persistence, telemetry, evaluation, Git tooling, and local runtimes.
23
22
-**Out of scope in the current slice:** full Orleans hosting, live provider execution, remote workers, and cloud-only control-plane services.
-`Feature spec` — [Agent Control Plane Experience](./Features/agent-control-plane-experience.md)
@@ -237,7 +265,8 @@ flowchart LR
237
265
238
266
- The Uno app must remain a presentation-only host instead of becoming a dump for runtime logic.
239
267
- Feature work should land as vertical slices with isolated contracts and implementations, not as shared horizontal folders.
240
-
- Epic `#12` starts with contracts, sequencing, deterministic runtime coverage, and UI exposure before live Orleans or provider integration.
268
+
- Epic `#11` establishes the reusable contract and communication foundation before epic `#12` begins embedded runtime-host work.
269
+
- Epic `#12` builds on that foundation instead of re-owning issues `#22` and `#23`.
241
270
- Epic `#14` makes external-provider toolchain readiness explicit before session creation, so install, auth, diagnostics, and configuration state stays visible instead of being inferred later.
242
271
- CI must stay meaningful without external provider CLIs by using the in-repo deterministic runtime client.
243
272
- Real provider checks may run only when the corresponding toolchain is present and discoverable.
0 commit comments