From ce638b98946f3eb9d6d48e07844e40832903709e Mon Sep 17 00:00:00 2001 From: garrytan Date: Tue, 3 Nov 2026 20:40:59 +0000 Subject: [PATCH] docs(captain): keep issues tidy (standing rule) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- changelog.d/garrytan-r68-crew-threads-attach.md | 1 + docs/captain.md | 13 +++++++++++++ 2 files changed, 14 insertions(+) diff --git a/changelog.d/garrytan-r68-crew-threads-attach.md b/changelog.d/garrytan-r68-crew-threads-attach.md index f694e410a..3c54277c6 100644 --- a/changelog.d/garrytan-r68-crew-threads-attach.md +++ b/changelog.d/garrytan-r68-crew-threads-attach.md @@ -2,5 +2,6 @@ ### Changed - **docs/captain.md** has a new section, "New threads join the crew". A crew thread asks its Captain for a new thread, and the Captain creates it in the crew. A thread the crew thread already made gets reported by code in that turn, so the Captain can add it with `crew.add`. A thread in another project goes Captain to Captain, and the receiving Captain creates it in its own crew as work, briefs it and returns the result. Only a project with no Captain lets the crew thread create the thread itself, with the code recorded on the work's issue. A cross-project thread the crew thread already made goes to that project's Captain to adopt, with its code on the issue. The cause: GBRA-240 created GBEV-33 directly in another project, and that thread ran outside every crew. +- **docs/captain.md** also has a new section, "Keep issues tidy" (Garry, 2026-11-03: "can we tell all the captains to audit their issues and clean them up. and have a standing rule that that is kept tiday"). Before archiving a thread, close or backlog its issues. On each wake, keep every touched issue accurate. Unassigned Todos nobody will start go to Backlog. A daily sweep closes, re-assigns or backlogs open issues untouched for 2 days whose assignee is archived, or idle with no open PR. The target is an In progress count close to working threads plus PRs waiting to merge. - **The Capy factory context (`factory.md` point 12)** now has the short version and cites that section. Its byte budget in `test/capy-skill-wrapper.test.ts` goes from 3,300 to 3,450: the page's new size rounded up to the next 25 bytes, and no other point was trimmed. - **docs/captain.md, Drive layout** says that `tools.capy.read` returns about the first 38,000 characters, with each line cut at 2,000. So a read, change and `tools.capy.write` program saves a truncated file, Drive files included. Edit long files with `tools.capy.edit`, or read and write the whole file in bash or Python and check the line count. `tools.drive.history` restores a recent version. This is how the org knowledge base's rules.md lost 37 rules. It lives in the docs page rather than the Capy skill because the skill sits at its fixed 5,315-token context budget. diff --git a/docs/captain.md b/docs/captain.md index 688e8f309..b85b68737 100644 --- a/docs/captain.md +++ b/docs/captain.md @@ -160,6 +160,19 @@ the work's issue. Why: a crew thread once created a thread in another project directly. That thread ran outside every crew, so no Captain briefed it, tracked it or could archive it. +## Keep issues tidy + +Issues show what the crew is really doing, so keep them true: + +- Before archiving a thread, close or move to Backlog every issue assigned to it. +- On each wake, leave every issue you touched accurate: its status, assignee and links. +- An unassigned Todo that nobody will start goes to Backlog. +- A daily sweep closes, re-assigns or backlogs any open issue outside Backlog that nobody + has touched for 2 days and whose assignee is archived, or idle with no open PR. + +The target: the Overview's In progress count is about the number of working threads plus +the PRs waiting to merge. + ## Plan before build A lane that builds something plans first. Its first act after the session-start install