From 022f16a7c1542ffc491cab01ff005dc3222c7522 Mon Sep 17 00:00:00 2001 From: Jammy2211 Date: Sat, 10 Oct 2026 17:35:17 +0100 Subject: [PATCH] docs: restore required generated policy blocks --- AGENTS.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index c378101..398a0c1 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -37,3 +37,29 @@ For board changes, follow the applicable sizing, navigation and orchestration standards and reuse Brain’s shared components. Keep domain data, prompt meaning and approval boundaries with the board’s owner. + + +## Sessions end at their deliverable + +A session ends when it reports its deliverable — never arm anything that +outlives the turn to wait for CI, a review or a merge: no `send_later`, no +`subscribe_pr_activity`, no `CronCreate`, no `ScheduleWakeup`, no `/loop`, no +`RemoteTrigger` create/update/run. Judge once, report, stop; the human re-runs +`/prm` (or the batch review) when it is green. Measured: five batch members +armed hourly check-ins on 2026-08-31, and a mobile `/prm` re-armed a 60-minute +`send_later` hourly all night on 2026-09-03 with no task active, draining usage. + + + +## Where to file + +Questions, help with code or an analysis, ideas, bug reports and results from a +user or collaborator — or an agent acting for one — go to + in the matching category +(Help & Questions, Ideas & Proposals, Bugs & Errors, Show and tell; +Announcements is maintainers-only), never to this repo's Issues. An agent never +runs `gh issue create` for such a report: it drafts the title, category and +body and hands them to the human (sessions cannot create Discussions). Only the +development flow — Mind prompt → `/start_dev` → `/create_issue` → one issue per +task → PR — opens issues here. Why: `PyAutoMind/policy/community_surface.md`. +