Inventory effective AGENTS.md cascades across substrate and product repos #657

New issue

Closed

opened 2026-07-23 17:55:18 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

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

Member

Parent

AOS #655

Goal

Build one deterministic inventory of AGENTS.md sources across the substrate and managed product fleet, then report the effective cascade for each selected role and harness. The inventory must distinguish aggregate duplication analysis from files that are actually eager in a session.

Repository sets

Derive the AOS substrate set from the committed substrate-image manifest. Do not scan an operator's projects directory.
Derive the full managed repo set from the infrastructure-owned fleet manifest.
Compute product repos as managed repos minus the AOS substrate set.
Track AOSH separately. It is not an AOS substrate repo and its AGENTS.md or hardware catalog must not become an automatic global load.
Record public/private provenance without copying private doctrine into public artifacts.

Measurements

Inventory root and nested AGENTS.md files, generated load-point bridges, and harness-specific overlays.
Record exact bytes, tokens, line count, source owner, audience, load condition, and paragraph hashes.
Produce an aggregate substrate report for duplication analysis.
Produce an active cascade report for each harness, role, CWD, and repo. Do not report the sum of every substrate AGENTS.md as eager startup cost when those files are only peripheral.
Detect repeated universal doctrine already supplied by the composed global base.
Classify every block as universal, role-specific, repo-specific unconditional doctrine, task-specific guidance, generated pointer, duplicate, or documentation-only.

Acceptance

A machine-readable artifact and readable report use canonical repo manifests and stable ordering.
The report covers root and nested AGENTS.md files across every managed repo, including repos that currently lack a root file.
The report shows both the aggregate substrate corpus and each real active cascade, with the distinction explicit.
AOSH is visible in the inventory but is never silently promoted into the global cascade.
Paragraph-level duplication points to the owning source rather than recommending copy edits blindly.
The output identifies product-repo clipping candidates and their correct destination: global person context, role COMPOSED.md, ordinary skill, repo docs, validator/code, or deletion.
Fixture-backed tests cover repo-set difference, nested cascade order, generated bridges, duplicate hashing, missing roots, public/private provenance, and AOSH non-substrate handling.
AOS #656 can consume the inventory without reimplementing repository discovery.

Starting evidence

The current substrate manifest names seven repos, five of which currently carry a root AGENTS.md. Their aggregate source size is about 41.5 KB. That number is a duplication-audit signal, not an eager-context total or a test constant.

Rollout child

coilyco-flight-deck/infrastructure#607 consumes this audit to clip managed product-repo AGENTS.md files. This inventory ticket remains read-only and does not fan out repo mutations.

## Parent AOS #655 ## Goal Build one deterministic inventory of AGENTS.md sources across the substrate and managed product fleet, then report the effective cascade for each selected role and harness. The inventory must distinguish aggregate duplication analysis from files that are actually eager in a session. ## Repository sets * Derive the AOS substrate set from the committed substrate-image manifest. Do not scan an operator's projects directory. * Derive the full managed repo set from the infrastructure-owned fleet manifest. * Compute product repos as managed repos minus the AOS substrate set. * Track AOSH separately. It is not an AOS substrate repo and its AGENTS.md or hardware catalog must not become an automatic global load. * Record public/private provenance without copying private doctrine into public artifacts. ## Measurements * Inventory root and nested AGENTS.md files, generated load-point bridges, and harness-specific overlays. * Record exact bytes, tokens, line count, source owner, audience, load condition, and paragraph hashes. * Produce an aggregate substrate report for duplication analysis. * Produce an active cascade report for each harness, role, CWD, and repo. Do not report the sum of every substrate AGENTS.md as eager startup cost when those files are only peripheral. * Detect repeated universal doctrine already supplied by the composed global base. * Classify every block as universal, role-specific, repo-specific unconditional doctrine, task-specific guidance, generated pointer, duplicate, or documentation-only. ## Acceptance * A machine-readable artifact and readable report use canonical repo manifests and stable ordering. * The report covers root and nested AGENTS.md files across every managed repo, including repos that currently lack a root file. * The report shows both the aggregate substrate corpus and each real active cascade, with the distinction explicit. * AOSH is visible in the inventory but is never silently promoted into the global cascade. * Paragraph-level duplication points to the owning source rather than recommending copy edits blindly. * The output identifies product-repo clipping candidates and their correct destination: global person context, role COMPOSED.md, ordinary skill, repo docs, validator/code, or deletion. * Fixture-backed tests cover repo-set difference, nested cascade order, generated bridges, duplicate hashing, missing roots, public/private provenance, and AOSH non-substrate handling. * AOS #656 can consume the inventory without reimplementing repository discovery. ## Starting evidence The current substrate manifest names seven repos, five of which currently carry a root AGENTS.md. Their aggregate source size is about 41.5 KB. That number is a duplication-audit signal, not an eager-context total or a test constant. ## Rollout child coilyco-flight-deck/infrastructure#607 consumes this audit to clip managed product-repo AGENTS.md files. This inventory ticket remains read-only and does not fan out repo mutations.

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

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

Clip managed product-repo AGENTS.md after the fleet context audit #607

coilyco-ops referenced this issue

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

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

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 commented

2026-07-24 00:41:21 +00:00

Author

Member

The agent is implementing this inventory on branch issue-657-agents-inventory as the parallel structural track under #655. The work will avoid the #656 lane-budget and adapter implementation, publish canonical repository/cascade discovery through a separate contract, and leave #656 able to consume that discovery without reimplementing it.

The agent is implementing this inventory on branch `issue-657-agents-inventory` as the parallel structural track under #655. The work will avoid the #656 lane-budget and adapter implementation, publish canonical repository/cascade discovery through a separate contract, and leave #656 able to consume that discovery without reimplementing it.

coilyco-ops referenced this issue from a commit

2026-07-24 00:54:30 +00:00

feat(context): inventory AGENTS cascades (closes #657)

coilyco-ops closed this issue

2026-07-24 00:54:30 +00:00

coilyco-ops referenced this issue

2026-07-24 00:54:54 +00:00

Measure Goose startup context before the ordinary-skill refactor #656

coilyco-ops referenced this issue

2026-07-24 01:08:12 +00:00

Reject unknown current repositories in AGENTS inventory #681

coilyco-ops referenced this issue