chore(docs): AGENTS.md public linkage — retire, relocate, or clearly mark as maintainer-scope #316
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit#316
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
Lookout Codeberg cold-read (bus 45db) flagged: AGENTS.md is explicitly internal-facing (maintainer discipline, chamber-context, substrate-of-record for internal review). But it is linked from README Architecture section, which brings new adopters into the wrong register — same as
docs/cold-read/on the public surface.Decision required
Three options:
docs/internal/AGENTS.md: moves it out of root, clearly signals scope. Update README link accordingly.docs/architecture.mdthat IS linked from README; keep AGENTS.md as maintainer-scope, unlinked from adopter path.Herald prose-craft judgment on which option best serves the adopter register. QM has substrate-context on what MUST stay in AGENTS.md vs what can move.
Set J context
Must land before v1.0.0. Herald + QM collaboration surface.
Resolved as option 3 (split), merged in PR #321.
docs/architecture.md— adopter-register architecture overview, link-first to the ADRs (points, doesn't restate — no double-canonical drift).Converged with QM (substrate-safety review) + Surveyor (prose merge-gate). Residual
operations.md:198AGENTS.md leak folded into #315. Ships in v0.26.0.