feat: deliver seed-driven Agent Capacity Provider infrastructure #773

Runtime and journal owner checkpoint — 2026-10-29

Accepted independent owner evidence now includes SDK .44 (#508), Deployment .133 (#1068), Agent .35 (#562), API .16 (#658), UI .24 (#108), Identity .10 (#61) and Admin .13 (#154), all in their respective repositories. Exact producer/archive identities and the twenty native Agent providers are recorded in accepted documentation PR #850 (merge 5e854ef). This is not a final assembled Capacity Provider: Agent .35 still pins Deployment .127, API .16 pins .130, and Platform #817 remains immutable earlier assembly evidence.

Documentation slice criteria:

• Refresh Agent architecture capability status against accepted owner exports and current hosted evidence.
• Add a source/archive evidence reference and exact twenty-provider class/capability/module catalogue.
• Distinguish native seed journal from pending live coordinator/authority and preserve repository/Keycloak ownership.
• Verify relative links, fences, exact hash lengths, provider inventory, normal layout/readability checks and current unit command.
• Complete documentation PR docs: refresh native runtime and seed journal evidence (#773) #850 hosted gates and final review: all 28 exact-head checks pass at fd6e0bb; twenty provider rows exactly match accepted owner metadata.

Draft Deployment #1070 binds retained runtime policy to the actual QEMU launch; finite-policy positive qualification is not yet accepted. Both diagnostic foundations failed before attestation. Current successor source 4beb6c55caa8a04213c9885229d6a66f5b63088a fixes six demonstrated double-hyphen option-alias omissions and temporarily captures bounded creation stderr to identify the primary shim initialization error. Remove temporary tracing and qualify the untouched production path before acceptance; .134 remains frozen and .135 is not yet packed. Preserve all VM/resource/cleanup assertions and time limits. Profile publication, virgin pool, setup/egress, live enrollment, seed coordination, CLI and exact final assembly remain unfinished. Real Work/models/accounting remain Task 10. All issues, including #678, stay open; no production/legacy changes.

Earlier checkpoints below are historical and do not override this status.

Active Task 3D implementation checkpoint — 2026-10-28

The original ready review set remains integrated (21 PRs plus repairs #805/#806); all verified merged branches were cleaned in the previous review. This continuation adds bounded, unmerged review candidates: SDK #494 environment contracts, SDK #495 fenced capacity/readiness, Agent #530 independent strict build and Agent #531 native private probe authority. They are ready with current owner CI; existing SDK #493 activity contracts also remains ready.

Draft Agent #532 exposes native environment preparation: actual setup → fresh authority → verification → fresh authority, exact guest/runner/environment/entry/network receipt binding, safe errors, bounded output, cancellation and monotonic deadlines. A blocking-provider control demonstrated late success before the correction. Final source f7db6d1a17c3e459193369c5eaca0e97af63d35f passes 20 owner cases, genuine script-free archive/Node/declaration consumers and hosted component verification. It remains draft because qualified real guest execution/authority and Kata egress are not yet delivered.

Draft UI #105 qualifies one exact SDK successor; all 46 owner cases (including real browser/mobile/Astro/public-package coverage), genuine Node/declaration archive consumers and both hosted runs passed. Upstream combined SDK review remains required. Platform #810 updates durable architecture/plan evidence and is ready after all 26 applicable current-head checks passed, including installed composition, retained UI/Keycloak and NPM/Git scenarios. The unchanged path-filtered Kata proof remains #792. No new PR was merged.

Verified local counts: SDK #494 123; SDK #495 129; Agent #530 16; Agent #531 17; Agent #532 20; combined SDK source 39d337c79528a3b815973a684844781211c4669a 144; preserved Agent component source 2d9afaba06ab6a827ea6eb8df8d7b456eec4be16 57. These are separate owner/candidate suites and must not be added as a unique total. All changed methods pass the canonical twenty-line gate without new baseline debt or exceptions.

New exact private archives:

• SDK .28 source eabe9b892ad1d2f73ef4ea75405965c3c9cc3cee; SHA-256 b06c943463c3aa87d8e4101088e355af487aefbac67aa99c4947b3040872a321.
• SDK .29 source a868b25fdbad76cb28efafc02c136f94acb7ef32; SHA-256 822f6cdb4d3ed6dfe7dd313777f71e334a195166159a8f33077e5ebe1b5b6dd3.
• SDK .30 combined integration source 39d337c79528a3b815973a684844781211c4669a; SHA-256 ce65aa96b9366a6c6aab3fad9d673d659f410f68eccb47325e1c5943b5ae0723. Pool/protocol source still needs bounded owner PR delivery after predecessor review; the integration branch is not a replacement.
• Agent .2 authority source 65db5ef89d9022e75a6119620d799de3eefdee19; SHA-256 69fc8e4a78e120e8468c437d7d44eed861020ee17f788b7ce00dfe33dd057e48.
• Agent .4 environment source f7db6d1a17c3e459193369c5eaca0e97af63d35f; SHA-256 1a94d5fd694ba759ef042e1e44bd994a2b753da883f2f42037e65fabad52a5c4.
• UI .21 source 45684e6b0b91374df87774513a0fbe4d6872d2fb; SHA-256 6ec80d79da213e6e04a791850d2f200da36ae74e124f7786f467513f7b7f3c56.

Earlier archives, including Agent .3 before the deadline refinement, retain their bytes. New empty-cache frozen installation proofs bind SDK .28/Agent and SDK .30/UI; the cache/lock prevention proposal is separate issue #809. Overlapping candidates must be reconciled into one exact SDK/owner closure with fresh resulting-head gates and every suite retained.

Full Task 3D is not complete. Remaining: actual separate manager/worker/guest programs and roots; scoped private sandbox transport/grants; real exclusive virgin pool/refill/generation cleanup; guest setup/egress; signed existing-team connection with isolated Keycloak enrollment/heartbeat/revocation; default API seed authority/artifact/custody/journal/recovery; CLI project/profile/seed/capacity and full assembled replacement. Work/models stay Task 10. API #645 remains draft. Original dirty Agent/Deployment files and indexes are unchanged; API #620 committer policy remains exact. All issues including #678 remain open, with no production/legacy mutation.

The earlier review/inventory below is retained as historical evidence.

Integration review checkpoint — 2026-10-28

All 21 original ready Task 3D PRs and two separately reviewed verification fixes have merged into cordis (23 PRs total). The exact squash commits were read back from GitHub and verified as ancestors of fetched origin/cordis. All 24 delivered branch references, including the matching Deployment handoff alias, were checked before local/remote deletion. Unlanded integration work and original dirty Agent/Deployment drafts remain preserved.

Final Platform cordis is f82ef1b (PR #792). All 28 checks passed at reviewed head 83f4b88, including both corrected genuine UI assemblies and hosted Ubuntu KVM/Kata. The real guest receipt records KVM API 12, host kernel 7.0.0-1017-azure, guest kernel 6.18.35, Kata 4.1.0, containerd 2.4.1, Ubuntu 26.04.1 runner image 20261023.163.3 and verified cleanup. No workstation runner registration or local VM/daemon execution occurred.

Review fixes #805 (affa3bf) and #806 (ab4911d) retain primary/cleanup errors and correctly observe eventual application readiness. The diagnosed frozen-cohort transient read failure is retried only for SERVICE_WORKER_EXCHANGE_FAILED within the unchanged 240-second budget/100ms interval; apply is never repeated, failed/cancelled/late outcomes cannot pass, and no file fallback or weaker ownership/readiness assertion was introduced. Both genuine UI runs and all 26 checks passed for #806. This qualifies bounded observation, not a guarantee that every worker request meets its latency deadline.

Task 3D resumed with SDK #493, ready for maintainer review and intentionally unmerged: source 7eb60a4a68ca770f896e07d0e3d8d2324154e6e9, SDK .27 archive SHA-256 ee30dbacf0e95d3fd9f88d097b15332c3dbf8020c3313c90e0a0578937a5d1df. All 121 owner cases, hosted gates, genuine public Node/schema and declaration consumers passed. It adds extensible activity-profile data contracts; Agent retains provider execution, semantic validation and live authority. API #645 remains draft pending real default adapters and complete owner verification.

Accepted exact artifacts:

• SDK .25 provider transport: source fe1d3237004ade38c44e94b64aac55c18be8f2a1; SHA-256 aca6df9d73f89c69ee0639a27a55ef9b84e118c04b015b5f5baf475281d944da.
• SDK .26 combined seed foundation: source bcf7919e1900e31cd3061b20d93c3909f45f7223; SHA-256 c964a28d6dd4e47b9424ec18496deb0a4e3b94ed0b7a2e795bf37096c0f6c835; 118 owner cases.
• Deployment .80 native backend: merged source d47c28987efd1beb5292f041daea3d1b902f3775; SHA-256 f093987d29685851bed3c2158b8cac44ae863da72e3b89f3fb393b8badf85624. Complete exact-head run 40688699878 passed all nine gates, including 64 foundation cases with a real warm guest and verified destruction. Script-free public archive and declarations passed independently.

All earlier archives remain immutable. API approved-committer blob remains b1a687db754ee2fac141919e6c63052d12bf2812. All 25 delivery issues, including #678, remain open. Full Task 3D is ongoing: separate manager/worker/guest programs, live team connection, environment preparation, seed runtime, CLI and full assembly remain outstanding. Real Work/model execution stays Task 10. Repository, Keycloak, legacy and production boundaries remain intact.

The sections below retain earlier requirements and historical candidate evidence; this integration checkpoint supersedes their earlier ready/unmerged status statements.

Goal

Implement the maintainer-approved revised Task 3D: separate Agent manager/worker/guest Cordis roots, real virgin warm Kata capacity and environment setup, extensible definition-owned activity profiles, seed-driven host composition and public existing-team connections.

Approved design and boundaries

Canonical references are docs/agent-architecture.md and docs/seed-architecture.md; revised delivery: docs/superpowers/plans/2026-10-27-agent-composition.md. The current architecture documentation candidate is PR #785 at ab07df126f333009db55e949b5e5cf8202c5be58; earlier approved design evidence remains preserved. The earlier embedded Agent root in Deployment's worker and sandbox-free Task 3D scope are superseded.

API owns headless seed coordination; SDK portable contracts; Agent manager/kernel/worker/pool/profile/runner/environment and container plugins; Deployment common artifacts/custody and bounded sandbox host control; CLI public owner clients and UI presentation. Real Work/models/productive handlers/accounting remain Task 10. Existing-team authority stays behind the existing control plane's public APIs, preserving Keycloak approval and signed provider credentials. No Team migration, production enrollment during tests, legacy service/source changes or cutover.

Acceptance criteria

• Preserve existing branches/dirty work and verify all nine fresh origin/cordis heads.
• Commit revised durable architecture and implementation plan before new runtime tests/code.
• Deliver critical readability rule/checker across all nine Cordis owners and shared future setup (separate Platform chore: require readable capability layers and contextual refactoring #781 and owner policy issues).
• Qualify separate manager/worker and actual Kata guest programs with default native construction.
• Prove external profile/handler/execution/environment providers without core edits, exact grants and generation-pinned cleanup.
• Prove virgin pool exclusive claims, background refill, generation discard, bounded setup/network permissions and verified teardown.
• Qualify API-owned seed plan/reconcile/read-back, policy-admitted missing plugins, durable partial progress and idempotent resume.
• Qualify real isolated Keycloak plus existing-control-plane contract fixtures for approved enrollment, heartbeat, revocation and team isolation.
• Consume exact public owner archives and record owner/assembled current-head CI evidence.
• Qualify hosted Ubuntu 26.04 x64 KVM/Kata first; require explicit self-hosted provisioning only if that venue fails. No workstation registration.
• Hand back bounded cordis PRs without merging; keep all issues including fix: align inherited skills with Cordis workflow #678 open.

Current checkpoint

The next bounded review wave is ready. No PR was merged and no issue was closed. Full Task 3D remains incomplete.

All nine critical policy candidates remain ready with latest effective checks green: Platform #784, CLI #328, SDK #486, Deployment #1014, API #643, Identity #56, Admin #149, UI #103, Agent #527. Earlier stale metadata failures are superseded by successful newer validation at those same heads.

Earlier compatible owner candidates remain ready: Identity #58, Admin #151, Deployment #1019 and API #646. SDK #483 remains the bounded probe-contract candidate. All new executable methods in this wave passed the pinned canonical twenty-line checker with unchanged origin baselines and no new grandfathered debt or exceptions.

Review/dependency order

1. Review the shared policy candidates first; preserve owner-specific rules and API Record SDK EF deadline failure and canonical-work repair frontier #620 approved committers.
2. Review SDK release: generation243 managed Identity service composition #492 before docs: suspend required human review during pre-launch integration #490 (same bounded compiler fix); SDK release: generation237 with rc288 managed backup coordination #483/Temporarily disable required human reviews during pre-launch integration; restore before launch #489 and Deployment #1022 are independently reviewable foundations.
3. Review docs: suspend required human review during pre-launch integration #490 and the compatibility candidates, including UI Select governed authoring runtime rc61 #104. Before any eventual merge, reconcile overlapping SDK projections/metadata rather than downgrading accepted contracts, then rebuild one exact combined SDK/owner closure and rerun the resulting exact-head gates.
4. Rebase API Retain Atlas coaching contract and closure lessons #645 after its compatible closure is accepted; keep it draft until real default adapters and the appropriate owner gates exist.
5. Continue bounded runtime/SDK/CLI/seed delivery waves. Existing integration branches and archived candidates are evidence and preserved work, not substitutes for reviewable owner PRs.

Exact private artifacts

The SDK .22 combined integration passed 135 owner cases; SDK .20 and the independent seed/provider/UI artifacts also passed installed-public-export and emitted-declaration consumers with scripts disabled. These overlapping suites are per-candidate evidence, not additive totals.

Explicit remaining Task 3D work

Manager/worker/guest production roots and built programs; named private sandbox grants/transport; real exclusive pool claims/refill/generation cleanup; immutable environment setup/verification and enforced egress; live existing-team enrollment/heartbeat/revocation; API seed default planning/preparation/authority/private persistence/recovery; CLI project/profile/seed/capacity commands; complete exact-artifact assembly and bounded owner delivery. Real Work/model execution stays Task 10.

Original dirty Agent and Deployment drafts remain unchanged and preserved. Every artifact above is local/private, with no production publication or legacy service mutation. Every issue, including #678, remains open.