Consume role repository metadata and compile native residency #895

Closed
opened 2026-08-05 07:49:03 +00:00 by coilyco-ops · 0 comments
Member

Parent

coilyco-flight-deck/agent-compose#200

Outcome

Make AOS consume verified role repository metadata from Agent Compose and become the owner of one deterministic native host-residency plan.

AOS must not parse or reinterpret .agents/roles.kdl. Agent Compose owns that schema and resolution. AOS consumes the verified result.

Work

  • Read the active role's complete repository set from verified Agent Compose bundle metadata.
  • Use that same set across native and standalone-container launch planning.
  • Preserve the bundle metadata through the AOS-to-Ward handoff.
  • Remove AOS dependencies on the standalone per-harness mount-eligibility manifest.
  • Remove the legacy Python manifest generator after the Go and consumer migration completes.
  • Coordinate the generator retirement with #618, whose requirement to keep the old manifest flowing is superseded by the parent issue's final contract.
  • Compile one deterministic native residency plan from:
    • the union of every canonical role's repository dependencies
    • trusted provider and operating-context repositories required to construct those roles
    • explicit resident-only pins
  • Expose that plan through an installed surface and local machine-readable output that do not require every target checkout to exist first.
  • Keep only a minimal, explicitly named bootstrap input if fresh-host convergence needs one.
  • Make native workspace projection, startup cleanup, unexpected-clone handling, and repository status consume the same compiled residency plan.
  • Preserve residency and visibility as separate properties. Resident-only pins grant no role access.
  • Keep the substrate seed manifest separate.

Acceptance criteria

  • AOS consumes repository decisions from verified Agent Compose bundle metadata without parsing roles.kdl.
  • Native and standalone-container launches select the same repositories for a given role.
  • The Ward handoff preserves the verified repository set without re-derivation.
  • AOS no longer reads mount-eligibility.json.
  • The legacy Python mount-manifest producer and its dead contract are removed.
  • One deterministic residency plan covers role dependencies, trusted providers, operating context, and resident-only pins.
  • A fresh host can obtain that plan without a checkout dependency cycle.
  • Native projection, cleanup, status, and drift reporting use the same plan.
  • The embedded full expected-repository roster is removed or reduced to an explicitly named minimal bootstrap set.
  • Substrate remains a separate public-safe build input.
  • Documentation and docs/FEATURES.md describe the final contract.
  • Repository validation passes through declared Ward verbs.
## Parent https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/200 ## Outcome Make AOS consume verified role repository metadata from Agent Compose and become the owner of one deterministic native host-residency plan. AOS must not parse or reinterpret `.agents/roles.kdl`. Agent Compose owns that schema and resolution. AOS consumes the verified result. ## Work * Read the active role's complete repository set from verified Agent Compose bundle metadata. * Use that same set across native and standalone-container launch planning. * Preserve the bundle metadata through the AOS-to-Ward handoff. * Remove AOS dependencies on the standalone per-harness mount-eligibility manifest. * Remove the legacy Python manifest generator after the Go and consumer migration completes. * Coordinate the generator retirement with #618, whose requirement to keep the old manifest flowing is superseded by the parent issue's final contract. * Compile one deterministic native residency plan from: * the union of every canonical role's repository dependencies * trusted provider and operating-context repositories required to construct those roles * explicit resident-only pins * Expose that plan through an installed surface and local machine-readable output that do not require every target checkout to exist first. * Keep only a minimal, explicitly named bootstrap input if fresh-host convergence needs one. * Make native workspace projection, startup cleanup, unexpected-clone handling, and repository status consume the same compiled residency plan. * Preserve residency and visibility as separate properties. Resident-only pins grant no role access. * Keep the substrate seed manifest separate. ## Acceptance criteria * [ ] AOS consumes repository decisions from verified Agent Compose bundle metadata without parsing `roles.kdl`. * [ ] Native and standalone-container launches select the same repositories for a given role. * [ ] The Ward handoff preserves the verified repository set without re-derivation. * [ ] AOS no longer reads `mount-eligibility.json`. * [ ] The legacy Python mount-manifest producer and its dead contract are removed. * [ ] One deterministic residency plan covers role dependencies, trusted providers, operating context, and resident-only pins. * [ ] A fresh host can obtain that plan without a checkout dependency cycle. * [ ] Native projection, cleanup, status, and drift reporting use the same plan. * [ ] The embedded full expected-repository roster is removed or reduced to an explicitly named minimal bootstrap set. * [ ] Substrate remains a separate public-safe build input. * [ ] Documentation and `docs/FEATURES.md` describe the final contract. * [ ] Repository validation passes through declared Ward verbs. ## Related * #618
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agentic-os#895
No description provided.