Roll out repo-local generated pointer skills across the managed fleet #608

Closed
opened 2026-07-23 17:56:12 +00:00 by coilyco-ops · 0 comments
Member

Dependency

Depends on coilyco-flight-deck/agentic-os#658 and participates in AOS #655.

Goal

Fan the AOS-owned repo-pointer generator and presence contract across the infrastructure-managed repo fleet. The rollout places one pointer in each eligible target repo and removes stale harness-global aggregation.

Acceptance

  • Use infrastructure's canonical managed-repo manifest and the exemptions defined by AOS #658.
  • Run the AOS generator in dry-run mode first and publish the expected, missing, stale, exempt, and leaked inventory.
  • Land generated repo-/SKILL.md sources in each target repo, with repo-owned commits and validations.
  • Remove stale global symlinks or aggregation entries after the repo-local source is present.
  • Do not expose all repo pointers through agentic-os-kai, the AOS substrate, or a harness-global catalog.
  • Preserve current-repo discovery for Claude, Codex, OpenCode, Aider, Goose, and any other selected harness adapter that supports skills.
  • Record explicit exceptions for repos without the trifecta or with intentionally different discovery.
  • Re-run the AOS presence validator across the complete managed set and attach the final inventory.
  • Re-run AOS #656 to show the pointer cost appears only in the active repo context.
  • Keep rollout logic in infrastructure. Ward setup and package installation do not mutate every checkout.

Done condition

Every eligible managed repo passes the AOS presence and drift validator from its own canonical main, global pointer aggregation is absent, and the fleet report has no unexplained missing or stale entries.

## Dependency Depends on coilyco-flight-deck/agentic-os#658 and participates in AOS #655. ## Goal Fan the AOS-owned repo-pointer generator and presence contract across the infrastructure-managed repo fleet. The rollout places one pointer in each eligible target repo and removes stale harness-global aggregation. ## Acceptance * Use infrastructure's canonical managed-repo manifest and the exemptions defined by AOS #658. * Run the AOS generator in dry-run mode first and publish the expected, missing, stale, exempt, and leaked inventory. * Land generated repo-<name>/SKILL.md sources in each target repo, with repo-owned commits and validations. * Remove stale global symlinks or aggregation entries after the repo-local source is present. * Do not expose all repo pointers through agentic-os-kai, the AOS substrate, or a harness-global catalog. * Preserve current-repo discovery for Claude, Codex, OpenCode, Aider, Goose, and any other selected harness adapter that supports skills. * Record explicit exceptions for repos without the trifecta or with intentionally different discovery. * Re-run the AOS presence validator across the complete managed set and attach the final inventory. * Re-run AOS #656 to show the pointer cost appears only in the active repo context. * Keep rollout logic in infrastructure. Ward setup and package installation do not mutate every checkout. ## Done condition Every eligible managed repo passes the AOS presence and drift validator from its own canonical main, global pointer aggregation is absent, and the fleet report has no unexplained missing or stale entries.
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/infrastructure#608
No description provided.