From 5a0db31d80feda1d8871622aad6a8b7f95c8c0a0 Mon Sep 17 00:00:00 2001 From: garrytan Date: Tue, 3 Nov 2026 04:16:47 +0000 Subject: [PATCH] docs: leave docs/captain.md for a follow-up; /ship reads it as agent prose (GST-1160) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- docs/captain.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/captain.md b/docs/captain.md index 47a20b058..b09778c50 100644 --- a/docs/captain.md +++ b/docs/captain.md @@ -369,8 +369,7 @@ adopting this starts from **A. The record.** Every lane keeps an `## Approvals` table in its report and PR body, rendered by `gstack-approvals render`: date, what was asked, the owner's exact words, who -relayed them, what the answer covers, what is pending. On a public repository (or unknown -visibility) `render` prints only `Approved: yes|no (record )` for the PR body. Standing approvals are cited with +relayed them, what the answer covers, what is pending. Standing approvals are cited with their rule; a fresh ask is always needed for a product or behaviour decision, spend over a cap, anything published outside the repository, a threshold, budget, trial-count or case-kind change, closing a contribution without landing it, and anything destructive.