Files
gstack/captain/templates/AGENTS.md
T
Garry Tanandcapy-ai[bot] 6417abf7a6 Move the tools only Capy crews use into a crew/ folder (GST-1833) (#4145)
* Load the Capy crew skills only on Capy machines (GST-1833)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Add changelog entry for Capy-only crew skills (GST-1833)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Move the Capy-only crew tooling into crew/ and run its tests only when needed (GST-1833)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Test that the Capy launch file puts crew/bin on PATH

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Count any ~/.capy as a Capy machine, so a Mac running Capy keeps /captain

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Fix the tests and fixtures that broke when crew tooling moved into crew/

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Plan every crew test when a pull request's merge-base can't be read

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Add a test that checks each crew-only module left the root tree for crew/

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Run crew tests on pull requests that change bin/ commands or workflows they drive

Review-Finding: p1/specialist-batched#1 reader=testing
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Keep running every crew test on every pull request; the skip comes in a later change

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Keep copied installs and older release bisects working after the crew/ move

Setup now copies crew/lib into every host's runtime root beside bin and lib, so Windows installs (which copy instead of linking) can still start gstack-ship-receipt, gstack-pregate and the other commands that import it. The release bisect runs the train-gate script from wherever the checked-out commit has it, so a bisect over commits from before the move still gets a verdict.

Review-Finding: p1/outside-voice#1 reader=outside-voice
Review-Finding: p1/outside-voice#2 reader=outside-voice
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Say in the changelog that Windows installs keep working after the crew/ move

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Point the harness guide's merge-queue rows at crew/lib/ where those modules moved

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Point the plain-title test at the wave module's new home in crew/ (GST-1833)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-11-08 14:26:14 +00:00

2.0 KiB

<CREW_NAME> standing rules

The controller's own file. Scope instructions: every thread in the crew reads it. Each rule that came from the owner keeps the date and the exact words, so lanes can cite it as a standing approval instead of asking again. Append; never rewrite an owner's words.

Mandate (, )

"<the owner's words for what this crew is for>"

  • Every -* thread in is in the crew. New threads the owner starts are added too.
  • Watch issues and PRs. Start lanes for severe user-reported bugs no live thread has claimed (the severity bar is below).
  • Severity first: S1 is a broken install or upgrade, data loss, a security result that is wrong, or BASE red. S2 is a broken workflow with no workaround. Everything else is batched.

Merging (, : "")

  • One controller merges, through a train (/captain, the merge-train section). Lanes send READY and never merge. Standing approval to merge when green: "".
  • A merge outside a train costs a backstop gate; none without the owner's words.

Spend (, : "")

  • Pre-approved: train gates, bisects, the backstop, screens, focused paid cases. Cap per rerun: . Over the cap is a fresh ask.

Asks to the owner (, : "")

  • The ask format (gstack crew/docs/captain.md), explained like I'm five: , then one lettered line per decision: "A: hit problem p, which happens when h. We could fix it in these ways: 1) x; 2) y; 3) z. Recommendation: x because why. A1 to take recommendation." "do it" takes every recommendation in the list at full scope, follow-ons included, no further ask; a named option ("A2") takes that option instead.

Parallelism (, : "")

  • Keep about lanes working on disjoint files whenever there is backlog. Serial steps stay serial only where the tooling requires it: one train's slots, version stamps, edits to a shared file.

Decisions log