From 2be8bfdbc2c7f51b22e3fce0a543f3a42219d62a Mon Sep 17 00:00:00 2001 From: Dongkeun Lee Date: Tue, 18 Aug 2026 11:15:55 -0400 Subject: [PATCH] docs(intake): ground initiatives in owning docs, not session anchors A two-day Azure initiative was worked from a session anchor plus one leaf design doc, so four of the five owning docs were never opened and a documented limitation of one compartment was reported as a system limit. Intake now requires finding the owning doc, treating anchors and evidence folders as state rather than intent, enumerating sibling docs when an initiative spans compartments, and naming the owning docs in the brief. --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 171ce89e735..2b97faf7dff 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -381,6 +381,13 @@ Keep dependency judgment coarse: same repo plus overlapping area means serialize Treat read-mostly scouts as almost never blocked. For `no-mistakes` projects, the pipeline rebase step absorbs mild overlaps; for other modes, have the crewmate rebase before review or merge if needed. +**Ground the ask in its owning docs before briefing it.** +Find the document that owns the subsystem and read it; docs in this repo say so outright ("This document owns ..."), and scripts own their command mechanics in their headers. +Session anchors, checkpoints, handoff notes, completion reports, and evidence folders are state, never intent: never take scope or requirements from one, and when resuming such work, reconcile it against the owning docs first and report what the anchor missed. +When an initiative spans compartments, list the sibling docs in that family before starting; a limitation documented for one compartment is that compartment's, not the system's, until a sibling doc is checked. +The Azure fleet family is `docs/azure-pilot.md`, `docs/azure-runner.md`, `docs/azure-validation.md`, `docs/azure-crosscheck.md`, and `docs/azure-workers.md`; `docs/azure-worker-runtime.md` is a design leaf whose built behavior `docs/azure-workers.md` owns. +Name the owning docs by path in the brief so the crewmate starts from intent rather than from your notes. + Write the brief per section 11. ### Spawn