Files
gstack/capy/skill/gstack/factory.md
T
Garry Tanandcapy-ai[bot] a141e94388 Ask each question once and check every handed-over file, in every skill that loads the shared preamble (GST-2756) (#4383)
* Load the never-print-secrets rule in every skill on every host, with the commands it missed (GST-2753)

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

* Ask each question once and check every handed-over file, in every skill on every host (GST-2756)

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

* Point the shared CI-wait rule at gstack-pr-wait and name the missed secret-printing commands

The Ground Rules section told every skill to wait with gh pr checks --watch, which spends the shared GitHub GraphQL quota gstack moved off; it now names gstack-pr-wait. The banned list also covers ps aux and ps -ef, set -x, git config -l and an export $(...) that expands to a bare export. Size caps raised to the measured +70 bytes.

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

* Say which skills carry the new rule in its release note

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

* Say the new rules reach only skills that load the shared preamble

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

* List all four shared Ground Rules in the loadouts guide

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-17 12:05:52 +00:00

4.3 KiB

How we work: gstack's factory on Capy

Your crew's CREW.md and recorded approvals decide who may merge, update a base, spend or touch production; urgency changes priority, never permissions or gates. With no Captain, ask the person; never merge without their word. Story: capy/README.md; examples: org Drive software-factory/README.md.

  1. Plan, then a yes. New functionality starts with /autoplan sized to the work; the build waits for "do it". [SKILL.md: Plan, approve, ship]
  2. Someone else merges. Run /ship to a receipt on your final pushed head, send one READY quoting gstack's verify output verbatim, and stop. One open PR per lane; follow-ups ride it. The merge owner merges on green and assigns versions; docs-only PRs run only docs checks. [crew/docs/captain.md: The READY contract]
  3. Block only on the floor. A finding blocks if it would fail a test, break production, or lose data or secrets; deferred findings stay on the PR and never become issues. [docs/review-policy.md]
  4. Fix waves. When main goes red, hold /ship while one owner finds the root cause; bring main in once, as your rules allow. Follow-ups get one issue with an owner and one PR. [docs/triage.md]
  5. Severe first, same gates. A severe user-facing bug jumps the queue with a short plan; receipt, checks and merge owner stay.
  6. Trade findings, not small talk. Another crew's finding goes to its Captain, through yours, with evidence.
  7. Measure before you act. Run the real system on the merged tree you ship; a real run outranks a reviewed plan. Each number names its run, commit or uncapped query; say what you did not verify.
  8. Evals decide, and losses get reported. Preregister bars, cap and stop rule before paying [/eval-plan]. Cheap proof (a keyless fake, a smoke) first. Controls: no-skill and placebo arms, clean decoys. Report use and pass apart; quote spend from the meter. A new part needs proof it helps or a dated test plan [ETHOS.md: 9. Earn Its Place].
  9. Flakes: one rerun, a ledger, a daily fix. Only the policy's rerun, never for a harness or infra red; a second red is real; never loosen a test. [crew/docs/captain.md: The daily flaky pass]
  10. Quiet. Messages wake the Captain cold: send READY, a blocker, done or a Captain or owner call, else end_turn; no acks or progress notes. Reports and replies open with Failed or skipped:, Unverified: and Also changed: lines (each item, or none), under 250 words; top 10 of long lists. Findings write-ups follow [ETHOS.md: 8. Explain the Number]. Broadcasts go in its notes.
  11. Ask once, plainly (every skill's Ground Rules). One ask per decision, explained like the owner is five: your Captain's name, then a lettered line each: "A: hit problem p, which happens when h. We could do 1) x, 2) y or 3) z. Recommendation x because why. A1 to take recommendation." "do it" takes every recommendation; "A2" takes option 2. Owner tasks: the exact link (in Capy: path and field), numbered steps, the reply word. Never re-ask a standing rule. [crew/docs/captain.md: The ask format]
  12. Fresh threads, closed out. One thread per unit of work. A thread keeps its PR until it merges or closes and hands off only then, never mid-PR on a token count; past 1B own tokens it checks in with its Captain once and carries on. Standing threads that wake on every event (merge lanes, watchers) rotate at 500M tokens or 3 days [/runaway-stopper]. Crew threads never create threads: ask your Captain (Captain to Captain across projects), or report one you made by code for crew.add. Its Captain archives only its crew's threads, never one holding an open PR, successor or not (R91), or an open issue; a PR closes only as landed, superseded or dropped. Threads outside every crew are the owner's, even its automation's. Size reviews to the diff. [docs/ship-budget.md; crew/docs/captain.md: New threads join the crew]
  13. The owner's model preference. gstack-models resolve --role agent picks agent models, except cross-family voices and eval subjects. [docs/model-policy.md: Your model preference]
  14. Finish before starting. No new fix thread in a repo while more than 10 finished PRs (green, reviewed, waiting only to merge) sit in its queue: merge or close them first. Severe hotfixes are exempt: security, data loss, red main, a broken install. [crew/docs/captain.md: New threads join the crew]