Mount verified role repository dependencies in warded workspaces #1644

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

Parent

coilyco-flight-deck/agent-compose#200

Outcome

Make Ward mount the complete repository set carried by a verified Agent Compose role bundle. Remove the old standalone mount-eligibility manifest and all harness-specific repository judgment.

Work

  • Read repository dependencies from verified bundle metadata supplied through the AOS handoff.
  • Mount exactly the complete set resolved for the assigned role.
  • Apply the same repository set for that role regardless of harness.
  • Preserve existing workspace authority, read-only reference behavior, writable target selection, and foreign-work protections.
  • Fail closed when required repository metadata is absent, malformed, outside allowed roots, or inconsistent with the verified bundle.
  • Do not parse roles.kdl, merge defaults, infer repositories from doctrine paths, or apply a second role policy.
  • Remove the mount-eligibility.json reader and its per-harness schema.
  • Remove compatibility code before the parent issue closes.

Acceptance criteria

  • Ward consumes repository dependencies only from verified bundle metadata.
  • One role produces the same mounted repository set across supported harnesses.
  • Missing or invalid repository metadata fails before workspace materialization.
  • Ward performs no role, default, provider, or source-location re-derivation.
  • mount-eligibility.json and its harness keys are unsupported in the final state.
  • Existing writable workspace and read-only reference boundaries remain intact.
  • The Content role can receive Voice Corpus while unrelated roles do not.
  • Every role can receive Lore through the bundle's global dependency.
  • Documentation and docs/FEATURES.md describe the bundle-owned repository contract.
  • Repository validation passes through declared Ward verbs.
## Parent https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/200 ## Outcome Make Ward mount the complete repository set carried by a verified Agent Compose role bundle. Remove the old standalone mount-eligibility manifest and all harness-specific repository judgment. ## Work * Read repository dependencies from verified bundle metadata supplied through the AOS handoff. * Mount exactly the complete set resolved for the assigned role. * Apply the same repository set for that role regardless of harness. * Preserve existing workspace authority, read-only reference behavior, writable target selection, and foreign-work protections. * Fail closed when required repository metadata is absent, malformed, outside allowed roots, or inconsistent with the verified bundle. * Do not parse `roles.kdl`, merge defaults, infer repositories from doctrine paths, or apply a second role policy. * Remove the `mount-eligibility.json` reader and its per-harness schema. * Remove compatibility code before the parent issue closes. ## Acceptance criteria * [ ] Ward consumes repository dependencies only from verified bundle metadata. * [ ] One role produces the same mounted repository set across supported harnesses. * [ ] Missing or invalid repository metadata fails before workspace materialization. * [ ] Ward performs no role, default, provider, or source-location re-derivation. * [ ] `mount-eligibility.json` and its harness keys are unsupported in the final state. * [ ] Existing writable workspace and read-only reference boundaries remain intact. * [ ] The Content role can receive Voice Corpus while unrelated roles do not. * [ ] Every role can receive Lore through the bundle's global dependency. * [ ] Documentation and `docs/FEATURES.md` describe the bundle-owned repository contract. * [ ] Repository validation passes through declared Ward verbs.
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/ward#1644
No description provided.