coilyco-flight-deck/agent-compose
coilyco-flight-deck/agent-compose
Watch
2
0
Code Issues 41 Pull requests Projects Releases 187 Packages Wiki Activity Actions

Make repository availability role-scoped and derive native residency #200

New issue
Closed
opened 2026-08-05 07:42:44 +00:00 by coilyco-ops · 2 comments
coilyco-ops commented 2026-08-05 07:42:44 +00:00
Member
Copy link

Outcome

Make repository availability a first-class part of the Agent Compose role graph. Remove harness-specific mount variance, collapse the standalone mount-eligibility artifact into verified role bundles, and derive the native host residency plan from the complete role repository graph.

The completed model has three concepts:

  • Substrate - build-time repositories available through the development image or cache.
  • Role bundle - doctrine, skills, providers, and repositories visible to one role.
  • Host residency - long-lived native checkouts derived from every role dependency plus explicit resident-only pins.

Substrate remains separate because image availability, host persistence, and role visibility have different security and lifecycle boundaries.

Role graph contract

Extend the trusted .agents/roles.kdl schema with explicit repository dependencies.

  • Support global repository dependencies inherited by every role.
  • Support repository dependencies selected for one role.
  • Resolve each role to one complete, sorted, deduplicated repository set.
  • Keep repository selection invariant across Claude, Codex, Goose, OpenCode, and any later harness.
  • Validate logical owner/repo identity, duplicate declarations, unknown references, and invalid placement.
  • Preserve strict parsing. Do not ignore unknown top-level or role nodes.
  • Stop inferring repository mounts from the location of composed doctrine sources.

Initial AOSK policy:

  • coilysiren/lore is a global repository dependency for every role.
  • coilysiren/voice-corpus is a Content Manager repository dependency.
  • Provider repositories continue to enter the appropriate role closure through the trusted provider graph.

Collapse mount eligibility into the bundle

Repository dependencies belong in Agent Compose's typed decision output and verified bundle metadata.

  • Agent Compose owns parsing, validation, resolution, provenance, and deterministic serialization.
  • Bundle inspection and description surfaces show why each repository entered the role.
  • AOS and Ward consume the complete resolved repository set from the verified bundle.
  • Consumers do not merge defaults or re-parse roles.kdl.
  • Harness frontmatter may still affect doctrine composition where supported, but never repository visibility.
  • Remove the standalone ~/.config/agent-compose/mount-eligibility.json contract.
  • Remove the legacy per-harness manifest producer, source-location inference, drift checks, consumers, tests, and documentation.
  • Any compatibility bridge needed for rollout is temporary and is removed before this issue closes.

Derive native host residency

Replace handwritten expected-repository rosters with one compiled residency plan.

The default resident set is:

  1. The union of every canonical role's resolved repository dependencies.
  2. Trusted provider and operating-context repositories required to build those roles.
  3. Explicit resident-only pins for repositories that belong on a native host but must not become visible to a role.

The derivation must preserve the distinction between residency and visibility. A resident-only pin does not grant a role access, and a role dependency does not become substrate merely because it is resident.

AOS owns the deterministic host plan and its local machine-readable output. Infrastructure realizes that plan across hosts.

  • Expose the compiled residency plan through an installed AOS or Agent Compose surface that does not require the target checkouts to exist first.
  • Keep only a minimal, explicitly named bootstrap input if fresh-host convergence needs one. Do not retain a second full expected-repository roster.
  • Make AOS native workspace projection, startup cleanup, and the repository status line consume the same compiled plan.
  • Make Infrastructure's checkout sync consume the compiled plan instead of a source-tree list.
  • Retire the duplicated public and private flat roster maintenance.
  • Retire AOSK's scripts/repos-on-disk.txt once its registry, digest, pointer-skill, and catalog-graph consumers read the canonical compiled plan.
  • Remove the Infrastructure repo-list symlink rollout when no consumer needs ~/.config/agentic-os/repos-on-disk.txt. Keep unrelated fleet-organization configuration separate.
  • Preserve an explicit report or doctor surface for resident checkout drift.

Current drift demonstrates the need: AOS's native roster includes voice-corpus, while AOSK's repeated flat personal roster omits it.

Ownership

  • Agent Compose - roles.kdl schema, strict validation, repository resolution, bundle metadata, provenance, and inspection.
  • AOSK - personal global, per-role, and resident-only repository declarations.
  • AOS - launch integration, deterministic host-plan output, native workspace and status-line consumption, and removal of the legacy manifest generator.
  • Ward - consume verified bundle repository metadata for warded workspace mounts without role re-derivation.
  • Infrastructure - converge checkouts and host configuration from AOS's compiled plan without owning a repository list.
  • Substrate build - retain its separate public-safe seed manifest and image lifecycle.

Config remains at the lowest layer that fully determines it. Infrastructure performs fleet rollout but does not redefine role policy.

Rollout sequence

  1. Add strict repository declarations, resolution, provenance, and bundle metadata to Agent Compose.
  2. Teach AOS and Ward to consume the verified bundle repository set.
  3. Add the AOSK global Lore and Content-only Voice Corpus declarations.
  4. Add deterministic host-residency derivation and resident-only pins.
  5. Move Infrastructure and AOS native consumers to the compiled host plan.
  6. Move AOSK registry and catalog jobs to that plan.
  7. Delete the standalone mount manifest, handwritten full rosters, repo-list symlink, compatibility code, and stale documentation.
  8. Regenerate affected documentation and feature inventories through each repository's declared workflow.

Acceptance criteria

  • roles.kdl has a strict, documented repository dependency schema.
  • Unknown nodes, invalid repository identities, duplicate declarations, and unknown references fail closed.
  • Each verified role bundle contains one complete repository set with decision provenance.
  • The same role receives the same repository set across every supported harness.
  • Every role receives coilysiren/lore.
  • Content Manager receives coilysiren/voice-corpus.
  • Roles other than Content Manager do not receive coilysiren/voice-corpus unless separately declared by an accepted policy change.
  • Native, standalone-container, and warded launches consume the same role repository decision.
  • No consumer re-parses roles.kdl or rebuilds the repository set.
  • mount-eligibility.json and its per-harness contract are removed.
  • The native resident set is derived from the complete role graph plus explicit resident-only pins.
  • Fresh-host convergence can obtain the residency plan without a checkout dependency cycle.
  • Infrastructure clones and refreshes the derived resident set without maintaining a second list.
  • Native workspace projection, cleanup, status, and drift reporting use the same residency plan.
  • AOSK registry, digest, pointer-skill, and catalog-graph jobs no longer depend on a handwritten flat roster.
  • Repeated public and private repos-on-disk manifests and the Infrastructure repo-list symlink are removed.
  • Substrate membership remains an independent, public-safe build input.
  • Agent Compose, AOS, AOSK, Ward, and Infrastructure documentation describe the final ownership boundary consistently.
  • Material feature changes update each affected docs/FEATURES.md.
  • Repository validation passes through each repository's declared Ward verbs.
## Outcome Make repository availability a first-class part of the Agent Compose role graph. Remove harness-specific mount variance, collapse the standalone mount-eligibility artifact into verified role bundles, and derive the native host residency plan from the complete role repository graph. The completed model has three concepts: * **Substrate** - build-time repositories available through the development image or cache. * **Role bundle** - doctrine, skills, providers, and repositories visible to one role. * **Host residency** - long-lived native checkouts derived from every role dependency plus explicit resident-only pins. Substrate remains separate because image availability, host persistence, and role visibility have different security and lifecycle boundaries. ## Role graph contract Extend the trusted `.agents/roles.kdl` schema with explicit repository dependencies. * Support global repository dependencies inherited by every role. * Support repository dependencies selected for one role. * Resolve each role to one complete, sorted, deduplicated repository set. * Keep repository selection invariant across Claude, Codex, Goose, OpenCode, and any later harness. * Validate logical `owner/repo` identity, duplicate declarations, unknown references, and invalid placement. * Preserve strict parsing. Do not ignore unknown top-level or role nodes. * Stop inferring repository mounts from the location of composed doctrine sources. Initial AOSK policy: * `coilysiren/lore` is a global repository dependency for every role. * `coilysiren/voice-corpus` is a Content Manager repository dependency. * Provider repositories continue to enter the appropriate role closure through the trusted provider graph. ## Collapse mount eligibility into the bundle Repository dependencies belong in Agent Compose's typed decision output and verified bundle metadata. * Agent Compose owns parsing, validation, resolution, provenance, and deterministic serialization. * Bundle inspection and description surfaces show why each repository entered the role. * AOS and Ward consume the complete resolved repository set from the verified bundle. * Consumers do not merge defaults or re-parse `roles.kdl`. * Harness frontmatter may still affect doctrine composition where supported, but never repository visibility. * Remove the standalone `~/.config/agent-compose/mount-eligibility.json` contract. * Remove the legacy per-harness manifest producer, source-location inference, drift checks, consumers, tests, and documentation. * Any compatibility bridge needed for rollout is temporary and is removed before this issue closes. ## Derive native host residency Replace handwritten expected-repository rosters with one compiled residency plan. The default resident set is: 1. The union of every canonical role's resolved repository dependencies. 2. Trusted provider and operating-context repositories required to build those roles. 3. Explicit resident-only pins for repositories that belong on a native host but must not become visible to a role. The derivation must preserve the distinction between residency and visibility. A resident-only pin does not grant a role access, and a role dependency does not become substrate merely because it is resident. AOS owns the deterministic host plan and its local machine-readable output. Infrastructure realizes that plan across hosts. * Expose the compiled residency plan through an installed AOS or Agent Compose surface that does not require the target checkouts to exist first. * Keep only a minimal, explicitly named bootstrap input if fresh-host convergence needs one. Do not retain a second full expected-repository roster. * Make AOS native workspace projection, startup cleanup, and the repository status line consume the same compiled plan. * Make Infrastructure's checkout sync consume the compiled plan instead of a source-tree list. * Retire the duplicated public and private flat roster maintenance. * Retire AOSK's `scripts/repos-on-disk.txt` once its registry, digest, pointer-skill, and catalog-graph consumers read the canonical compiled plan. * Remove the Infrastructure repo-list symlink rollout when no consumer needs `~/.config/agentic-os/repos-on-disk.txt`. Keep unrelated fleet-organization configuration separate. * Preserve an explicit report or doctor surface for resident checkout drift. Current drift demonstrates the need: AOS's native roster includes `voice-corpus`, while AOSK's repeated flat personal roster omits it. ## Ownership * **Agent Compose** - `roles.kdl` schema, strict validation, repository resolution, bundle metadata, provenance, and inspection. * **AOSK** - personal global, per-role, and resident-only repository declarations. * **AOS** - launch integration, deterministic host-plan output, native workspace and status-line consumption, and removal of the legacy manifest generator. * **Ward** - consume verified bundle repository metadata for warded workspace mounts without role re-derivation. * **Infrastructure** - converge checkouts and host configuration from AOS's compiled plan without owning a repository list. * **Substrate build** - retain its separate public-safe seed manifest and image lifecycle. Config remains at the lowest layer that fully determines it. Infrastructure performs fleet rollout but does not redefine role policy. ## Rollout sequence 1. Add strict repository declarations, resolution, provenance, and bundle metadata to Agent Compose. 2. Teach AOS and Ward to consume the verified bundle repository set. 3. Add the AOSK global Lore and Content-only Voice Corpus declarations. 4. Add deterministic host-residency derivation and resident-only pins. 5. Move Infrastructure and AOS native consumers to the compiled host plan. 6. Move AOSK registry and catalog jobs to that plan. 7. Delete the standalone mount manifest, handwritten full rosters, repo-list symlink, compatibility code, and stale documentation. 8. Regenerate affected documentation and feature inventories through each repository's declared workflow. ## Acceptance criteria * [ ] `roles.kdl` has a strict, documented repository dependency schema. * [ ] Unknown nodes, invalid repository identities, duplicate declarations, and unknown references fail closed. * [ ] Each verified role bundle contains one complete repository set with decision provenance. * [ ] The same role receives the same repository set across every supported harness. * [ ] Every role receives `coilysiren/lore`. * [ ] Content Manager receives `coilysiren/voice-corpus`. * [ ] Roles other than Content Manager do not receive `coilysiren/voice-corpus` unless separately declared by an accepted policy change. * [ ] Native, standalone-container, and warded launches consume the same role repository decision. * [ ] No consumer re-parses `roles.kdl` or rebuilds the repository set. * [ ] `mount-eligibility.json` and its per-harness contract are removed. * [ ] The native resident set is derived from the complete role graph plus explicit resident-only pins. * [ ] Fresh-host convergence can obtain the residency plan without a checkout dependency cycle. * [ ] Infrastructure clones and refreshes the derived resident set without maintaining a second list. * [ ] Native workspace projection, cleanup, status, and drift reporting use the same residency plan. * [ ] AOSK registry, digest, pointer-skill, and catalog-graph jobs no longer depend on a handwritten flat roster. * [ ] Repeated public and private `repos-on-disk` manifests and the Infrastructure repo-list symlink are removed. * [ ] Substrate membership remains an independent, public-safe build input. * [ ] Agent Compose, AOS, AOSK, Ward, and Infrastructure documentation describe the final ownership boundary consistently. * [ ] Material feature changes update each affected `docs/FEATURES.md`. * [ ] Repository validation passes through each repository's declared Ward verbs.
coilyco-ops commented 2026-08-05 07:49:14 +00:00
Author
Member
Copy link

Implementation issues

The parent remains the complete architecture and done-condition. Each child owns its repository-local implementation and validation.

## Implementation issues * AOS: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/895 * AOSK: https://forgejo.coilysiren.me/coilyco-bridge/agentic-os-kai/issues/837 * Infrastructure: https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/issues/758 * Ward: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1644 The parent remains the complete architecture and done-condition. Each child owns its repository-local implementation and validation.
coilyco-ops commented 2026-08-05 10:06:34 +00:00
Author
Member
Copy link

Completed

The repository-availability migration is landed across every owning layer.

  • Agent Compose: 72cd03c plus validator follow-up dca225f. Strict role repository policy, bundle provenance, materialize-only handoff, and deterministic residency plan. Release run 159 passed.
  • Ward: efbb7ab1. Verified bundle repositories mount read-only under /refs. Promote and release workflows passed.
  • AOSK: 848073d. Lore is global, Voice Corpus is Content-only, resident-only policy is explicit, and the flat roster is deleted.
  • Infrastructure: 6d71f7d. Fresh-host policy bootstrap and compiled residency convergence are landed. Lint and secret-scan workflows passed.
  • AOS: PR coilyco-flight-deck/agentic-os#896 merged as c2817ed6. Verified repository metadata now drives native and Ward launch handoffs. The Python composer, standalone mount manifest, and embedded flat roster are retired.
  • AOS main validation, CLI release, pre-commit release, mirror, promotion, and full dev-base publication all passed.

All child issues are closed: agentic-os#895, agentic-os#618, agentic-os-kai#837, infrastructure#758, and ward#1644.

## Completed The repository-availability migration is landed across every owning layer. * Agent Compose: 72cd03c plus validator follow-up dca225f. Strict role repository policy, bundle provenance, materialize-only handoff, and deterministic residency plan. Release run 159 passed. * Ward: efbb7ab1. Verified bundle repositories mount read-only under /refs. Promote and release workflows passed. * AOSK: 848073d. Lore is global, Voice Corpus is Content-only, resident-only policy is explicit, and the flat roster is deleted. * Infrastructure: 6d71f7d. Fresh-host policy bootstrap and compiled residency convergence are landed. Lint and secret-scan workflows passed. * AOS: PR https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/896 merged as c2817ed6. Verified repository metadata now drives native and Ward launch handoffs. The Python composer, standalone mount manifest, and embedded flat roster are retired. * AOS main validation, CLI release, pre-commit release, mirror, promotion, and full dev-base publication all passed. All child issues are closed: agentic-os#895, agentic-os#618, agentic-os-kai#837, infrastructure#758, and ward#1644.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
aos/claude/sb46-tpm-execution-handoff
aos/claude/sb46-tpm-gate-exits
feat/gamedev-role
feat/boundary-omit
aos/claude/eval-context
aos/claude/eval-current-state
aos/claude/eval-refs-restore
aos/claude/eval-docs-one-page
aos/claude/personality-anchors
aos/claude/favorite-color-spread
aos/claude/personality-catalog-gaps
aos/claude/gh297-binding-skill-selector
aos/claude/personality-prose-distinctiveness
aos/claude/gh56-adopt-aos-eval
aos/claude/aw85-bands
aos/claude/xu59-just
aos/claude/xu59-eval-export
aos/claude/xu59-comment-caps
aos/claude/xu59-pr-ci
aos/claude/xu59-role-attribution
aos/claude/ck78-banner
aos/claude/mg96-fm
rescue/precommit-v0.18-uncommitted
evals/262-board-run
claude/agents-temp-clone-note
assets/compose-mark
adjacency/262-role-adjacents
chore/precommit-bump
prose/257-258-233-second-person
boundary/254-primitive-rename
fix/acompose-undefined-role-bindings
comms/rescope-counterpart
native-home/968-user-scope-projection
meld/248-evidence-acquisition
meld/231-shared-role-melds
evals/240-baseline
evals/240-model-arms
spike/claude-native-ui-surfaces
issue-225-compact-director-eval
issue-210
issue-218
issue-215-remove-context-levels
codex/luna-medium-ai-evaluation
issue-206-align-role-tiers
codex/luna-medium-roster-prose
issue-196-remove-legacy-role-providers
issue-197-role-provider-graph
feat/model-tiers
feat/remove-context-levels
issue-187
issue-178-content-communication-ownership
issue-163-designer-evals
codex/issue-794-preserve-canonical-projections
issue-163-ornith-direct-eval
issue-163-design-current-eval
issue-150-v2-baseline
issue-156-content-code
issue-150-v2-evidence
issue-150-v2-evaluation
issue-154-v2-main-integration
issue-148-remove-v1-integrations
issue-146-core-roster
issue-144-aos-catalogue-manifest
issue-152-release-classifier
issue-139-role-metadata-last
issue-138-designer-visual-web
issue-785-first-person
ward-salvage/agent-compose-078db83c
ward-salvage/agent-compose-74e37165
issue-130
recovery/2026-07-27-local-work
v2.66.0
v2.65.0
v2.64.0
v2.63.0
v2.62.0
v2.61.0
v2.60.0
v2.59.0
v2.58.0
v2.57.0
v2.56.0
v2.55.0
v2.54.0
v2.53.0
v2.52.0
v2.51.0
v2.50.0
v2.49.0
v2.48.0
v2.47.0
v2.46.0
v2.45.0
v2.44.0
v2.43.0
v2.42.0
v2.41.0
v2.40.0
v2.39.0
v2.38.0
v2.37.0
v2.36.0
v2.35.0
v2.34.0
v2.33.0
v2.32.0
v2.31.0
v2.30.0
v2.29.0
v2.28.0
v2.27.0
v2.26.0
v2.25.0
v2.24.0
v2.23.0
v2.22.0
v2.21.0
v2.20.0
v2.19.0
v2.18.0
v2.17.0
v2.16.0
v2.15.0
v2.14.0
v2.13.0
v2.12.0
v2.11.0
v2.10.0
v2.9.0
v2.8.0
v2.7.0
v2.6.0
v2.5.0
v2.4.0
v2.3.0
v2.2.0
v2.1.0
v2.0.0
v1.49.0
v1.48.0
v1.47.0
v1.46.0
v1.45.0
v1.44.0
v1.43.0
v1.42.0
v1.41.0
v1.40.0
v1.39.0
v1.38.0
v1.37.0
v1.36.0
v1.35.0
v1.34.0
v1.33.0
v1.32.0
v1.31.0
v1.30.0
v1.29.0
v1.28.0
v1.27.0
v1.26.0
v1.25.0
v1.24.0
v1.23.0
v1.22.0
v1.21.0
v1.20.0
v1.19.0
v1.18.0
v1.17.0
v1.16.0
v1.15.0
v1.14.0
v1.13.0
v1.12.0
v1.11.0
v1.10.0
v1.9.0
v1.8.0
v1.7.0
v1.6.0
v1.5.0
v1.4.0
v1.3.0
v1.2.0
v1.1.0
v1.0.0
v0.70.0
v0.69.0
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.0
v0.61.0
v0.60.0
v0.59.0
v0.58.0
v0.57.0
v0.56.0
v0.55.0
v0.54.0
v0.53.0
v0.52.0
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.0
v0.38.0
v0.37.0
v0.36.0
v0.35.0
v0.34.0
v0.33.0
v0.32.0
v0.31.0
v0.30.0
v0.29.0
v0.28.0
v0.27.0
v0.26.0
v0.25.0
v0.24.0
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.0
v0.18.0
v0.17.0
v0.16.0
v0.15.0
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.0
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.4.1
v0.4.0
v0.3.0
v0.2.1
v0.2.0
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
burndown-2026-08
Closed in the 2026-08-26 backlog burn-down. Reopen freely: state:closed label:burndown-2026-08 recovers the whole set.

  
autonomy
async-consult
 A human needs to consult on the issue to upgrade it to headless

  
autonomy
epic
 This issue has many units of sub work - its size makes it meaningfully exclusive with other autonomy types

  
autonomy
headless
 The agent can perform the work on its own

  
autonomy
live-collab
 The agent and the human need to work together in realtime

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
priority
P0
 priority tier

  
priority
P1
 priority tier

  
priority
P2
 priority tier

  
priority
P3
 priority tier

  
priority
P4
 priority tier

  
qa-fixture
Disposable issue admitted to the bounded Ward QA verification lane.

  
role/devrel
requires work from the Developer Advocate seat

  
role/eval
requires work from the Agent Evaluation Engineer seat

  
role/exec
requires work from the exec role

  
role/frontend
requires work from the Frontend Design Engineer seat

  
role/gamedev
requires work from the Game Developer seat

  
role/human
requires a person, and specifically not an agent seat

  
role/platform
requires work from the Developer Platform Engineer seat

  
role/qa
requires work from the QA role

  
role/sysadmin
requires work from the Systems Administrator seat

  
role/tpm
requires work from the Technical Program Manager seat

No labels
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/devrel
role/eval
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/sysadmin
role/tpm
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/agent-compose#200
No description provided.