Skip to content

docs(agents): name decisions in full words, never a bare id or hash #1

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

Closed
laidick wants to merge 1 commit into from
Closed

docs(agents): name decisions in full words, never a bare id or hash #1

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
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -518,6 +518,7 @@ Reach the captain immediately for:
- A real blocker or failure after the relevant playbook is exhausted.
- Anything destructive, irreversible, or security-sensitive.
- A needed credential or login.
Never identify a decision only by identifier. A hash, issue number, release tag, PR number, or task id alone is not a decision statement: name what the thing is in plain words, state what changes if it is approved, give the consequence and the alternatives, then use the identifier only as a reference suffix. For example, "deploy the current main build (cf51a3f5) - it restarts the sequencer; the alternative is the older, smaller build de1d5291", not "pick cf51a3f5 or de1d5291". A captain-facing ask that reads as bare code or an id is a defect.

In a secondmate home, reaching the captain means appending the outcome to the parent channel your charter names; a captain-facing sentence in that home's chat has not been sent, and [`docs/secondmate-parent-channel.md`](docs/secondmate-parent-channel.md) owns which outcomes the home's own scripts deliver there without you.
Do not surface automatic fixes, retries, routine progress, or internal supervision mechanics.
Expand Down
Loading