Skip to content

docs: sync fleet-managed AGENTS.md sections from hub #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
d-sorg-jules merged 1 commit into from
Sep 23, 2026
Merged

docs: sync fleet-managed AGENTS.md sections from hub #62

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 24 additions & 12 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -454,23 +454,35 @@ never as a silent close, never as a fabricated result.
acceptance criteria copied verbatim, why it is external, the resources it
needs, and what would reopen it. Validate with
`python -m shared_scripts.deferred_validation --repo-root .`.
3. **Split mixed issues.** If part of the issue is implementable software or CI
work, that part stays open as `retained_issue_url` and you may do it.
4. **Publish, verify, then close — in that order.** The original issue is only
closed as not planned after the record is merged, its `record_url` resolves
on the default branch, and a named human or the Board signed it off
(`reviewed_by` / `reviewed_on`).

Existing deployed plans retain their original source snapshots, pending Board
resource decisions and reactivation requirements. A schema change supplies no
review approval or measurement. Do not reopen already deferred `roadmap` work
because its experiment remains undone; inspect the plan and publication receipt.
3. **Split mixed issues.** Independently executable software or CI stays active.
In v1, retain its source issue and owner-plan software section; in the
new-adopter format, use `retained_issue_url`. Never add fields from one
schema to the other.
4. **Publish, verify, then close - in that order.** Preserve the original scope
and acceptance, verify the merged owner-plan link, and record the authorized
disposition before closing external-only work as not planned. New-adopter
records additionally require their `record_url` and recorded review fields;
v1 owners retain source snapshots and central publication/closure receipts.
User authorization to defer work is not Board approval to fund or execute it.

For v1, external-only is `disposition: defer`, mixed is `split`, and unavailable
work remains `status: deferred` with `board.decision: pending`. Reactivation
requires Board approval/evidence, evidence for every `prerequisites` entry and
an accountable execution owner; then link the bounded `activation_issue`.
`ready` or `activated` never means a measurement or validation was completed.
GitHub Projects draft cards are optional views, not prerequisites to activation.

Existing deployed plans retain original source snapshots and resource decisions.
A schema change supplies no review approval or measurement. Do not reopen already
deferred `roadmap` work because its experiment remains undone; inspect the plan
and publication receipt.

### Discovery Is Not Authority

Matching keywords like `measure`, `rig`, `chamber`, `specimen`, `calibrat` or
`trial` is how you **find** candidates. It never authorises closing an issue.
The catalog validator refuses a closed origin with no recorded review.
The applicable catalog and publication receipts must support the disposition;
new-adopter records require their recorded review fields.

The standard, the schema and the per-role instructions are in
[`docs/fleet-deferred-validation.md`](https://github.com/D-sorganization/Repository_Management/blob/main/docs/fleet-deferred-validation.md).
Expand Down
36 changes: 24 additions & 12 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -454,23 +454,35 @@ never as a silent close, never as a fabricated result.
acceptance criteria copied verbatim, why it is external, the resources it
needs, and what would reopen it. Validate with
`python -m shared_scripts.deferred_validation --repo-root .`.
3. **Split mixed issues.** If part of the issue is implementable software or CI
work, that part stays open as `retained_issue_url` and you may do it.
4. **Publish, verify, then close — in that order.** The original issue is only
closed as not planned after the record is merged, its `record_url` resolves
on the default branch, and a named human or the Board signed it off
(`reviewed_by` / `reviewed_on`).

Existing deployed plans retain their original source snapshots, pending Board
resource decisions and reactivation requirements. A schema change supplies no
review approval or measurement. Do not reopen already deferred `roadmap` work
because its experiment remains undone; inspect the plan and publication receipt.
3. **Split mixed issues.** Independently executable software or CI stays active.
In v1, retain its source issue and owner-plan software section; in the
new-adopter format, use `retained_issue_url`. Never add fields from one
schema to the other.
4. **Publish, verify, then close - in that order.** Preserve the original scope
and acceptance, verify the merged owner-plan link, and record the authorized
disposition before closing external-only work as not planned. New-adopter
records additionally require their `record_url` and recorded review fields;
v1 owners retain source snapshots and central publication/closure receipts.
User authorization to defer work is not Board approval to fund or execute it.

For v1, external-only is `disposition: defer`, mixed is `split`, and unavailable
work remains `status: deferred` with `board.decision: pending`. Reactivation
requires Board approval/evidence, evidence for every `prerequisites` entry and
an accountable execution owner; then link the bounded `activation_issue`.
`ready` or `activated` never means a measurement or validation was completed.
GitHub Projects draft cards are optional views, not prerequisites to activation.

Existing deployed plans retain original source snapshots and resource decisions.
A schema change supplies no review approval or measurement. Do not reopen already
deferred `roadmap` work because its experiment remains undone; inspect the plan
and publication receipt.

### Discovery Is Not Authority

Matching keywords like `measure`, `rig`, `chamber`, `specimen`, `calibrat` or
`trial` is how you **find** candidates. It never authorises closing an issue.
The catalog validator refuses a closed origin with no recorded review.
The applicable catalog and publication receipts must support the disposition;
new-adopter records require their recorded review fields.

The standard, the schema and the per-role instructions are in
[`docs/fleet-deferred-validation.md`](https://github.com/D-sorganization/Repository_Management/blob/main/docs/fleet-deferred-validation.md).
Expand Down
Loading