Enforce generated repo-pointer presence for every eligible managed repo #658

New issue

Open

opened 2026-07-23 17:55:59 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-23 17:55:59 +00:00

Member

Parent and prior work

Parent: AOS #655
Related audit: AOS #657
AOS #93 shipped the generator and drift validator.
agentic-os-kai #584 shipped the earlier org-wide rollout.
This is the missing presence and scoping follow-up, not a replacement for those completed tickets.

Problem

The repo-pointer validator can verify an existing generated pointer, but absence is still a valid no-op. Several repos have a generated repo- source while many eligible managed repos do not. Aggregation can also make pointers for unrelated repos visible globally, defeating the repo-local context boundary.

Goal

Every eligible managed repo gets one deterministic, generated, repo-local pointer skill. The validator enforces both presence and content drift without placing the fleet's pointer catalog into every session.

Acceptance

Define eligibility from a canonical manifest, with explicit exemptions for archived, unmanaged, or intentionally pointerless repos.
AOS owns the generator and presence validator. Infrastructure owns fleet rollout. Each generated source lands in its target repo.
Fail validation when an eligible repo lacks its expected repo-/SKILL.md, not only when existing content drifts.
Keep generated content minimal: repository purpose plus pointers to README.md, AGENTS.md, and docs/FEATURES.md when those targets exist.
Preserve generator ownership markers and deterministic stable ordering.
Keep discovery repo-local. Do not aggregate every repo-pointer into agentic-os-kai, AOS, or a harness-global skill union.
Let the active current repo contribute its pointer to the effective catalog measured by AOS #656.
Provide a dry-run inventory showing expected, present, missing, stale, exempt, and globally leaked pointers.
Add fixture-backed tests for missing pointers, renamed/transferred repos, absent optional docs, exemptions, offline validation, and removal of stale global symlinks.
Update the skill-authoring placement guidance if the repo-local pointer boundary needs a sharper statement.
Cross-reference pointer moves or deletions in the ordinary sweep at AOS #629.

Rollout child

coilyco-flight-deck/infrastructure#608 fans the generated repo-local pointer contract across the managed fleet after this AOS authoring work lands.

## Parent and prior work * Parent: AOS #655 * Related audit: AOS #657 * AOS #93 shipped the generator and drift validator. * agentic-os-kai #584 shipped the earlier org-wide rollout. * This is the missing presence and scoping follow-up, not a replacement for those completed tickets. ## Problem The repo-pointer validator can verify an existing generated pointer, but absence is still a valid no-op. Several repos have a generated repo-<name> source while many eligible managed repos do not. Aggregation can also make pointers for unrelated repos visible globally, defeating the repo-local context boundary. ## Goal Every eligible managed repo gets one deterministic, generated, repo-local pointer skill. The validator enforces both presence and content drift without placing the fleet's pointer catalog into every session. ## Acceptance * Define eligibility from a canonical manifest, with explicit exemptions for archived, unmanaged, or intentionally pointerless repos. * AOS owns the generator and presence validator. Infrastructure owns fleet rollout. Each generated source lands in its target repo. * Fail validation when an eligible repo lacks its expected repo-<name>/SKILL.md, not only when existing content drifts. * Keep generated content minimal: repository purpose plus pointers to README.md, AGENTS.md, and docs/FEATURES.md when those targets exist. * Preserve generator ownership markers and deterministic stable ordering. * Keep discovery repo-local. Do not aggregate every repo-pointer into agentic-os-kai, AOS, or a harness-global skill union. * Let the active current repo contribute its pointer to the effective catalog measured by AOS #656. * Provide a dry-run inventory showing expected, present, missing, stale, exempt, and globally leaked pointers. * Add fixture-backed tests for missing pointers, renamed/transferred repos, absent optional docs, exemptions, offline validation, and removal of stale global symlinks. * Update the skill-authoring placement guidance if the repo-local pointer boundary needs a sharper statement. * Cross-reference pointer moves or deletions in the ordinary sweep at AOS #629. ## Rollout child coilyco-flight-deck/infrastructure#608 fans the generated repo-local pointer contract across the managed fleet after this AOS authoring work lands.

coilyco-ops referenced this issue from coilyco-flight-deck/infrastructure

2026-07-23 17:56:12 +00:00

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

coilyco-ops referenced this issue

2026-07-23 17:57:23 +00:00

[epic] Bound composed-agent context across selected roles and harnesses #655

coilyco-ops added the

autonomy

live-collab

priority

labels

2026-07-29 03:44:50 +00:00