From a2e53c772f7f0f85a22f880ae11f342298d1e99a Mon Sep 17 00:00:00 2001 From: garrytan Date: Mon, 26 Oct 2026 23:31:57 +0000 Subject: [PATCH] fix: pre-landing review fixes Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- capy/skill/gstack/captain.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/capy/skill/gstack/captain.md b/capy/skill/gstack/captain.md index ca946103e..4c9e7245b 100644 --- a/capy/skill/gstack/captain.md +++ b/capy/skill/gstack/captain.md @@ -27,8 +27,9 @@ and the Captain's drive) is the `/captain` skill and `docs/captain.md` in the gs - closing someone's contribution without landing it; - anything destructive or irreversible. - **Observable questions are not the person's to answer.** A question a command, a render or a measurement - can settle ("is the new path faster", "does the endpoint take this payload", "does the test still fail") - is settled by the thread: it runs the thing and reports the result. Only a product or preference call + can settle locally, read-only and for free ("is the new path faster", "does the test endpoint take this + payload", "does the test still fail") is settled by the thread: it runs the thing and reports the result. + A call that changes state, reaches a live system or spends money is still an ask. Only a product or preference call goes up, with the observation already made. A Captain that receives an observable question sends it back with the check that answers it instead of relaying it. - **What a gstack workflow does in Capy.** Launched with `GSTACK_SESSION_KIND=unattended`, a workflow takes