**§11.4.182 — Track+branch work-stream identity label `(T/ - )` on every agent/subagent label + every operator-facing work-stream reference (User mandate, 2026-07-05).** Operator mandate (2026-07-05): "EVERY agent/subagent/work-stream label AND every operator-facing report reference to a work stream MUST carry a `(T/ - )` prefix identifying the track + git branch + the claude-toolkit alias in use — e.g. `(T1/main - claude1) ATM-312 MPV drm_prime investigation`, `(T2/feat/mistiq-vader - deepseek) SPK-XXX ...`." In a multi-track layout (parallel checkouts each on a distinct branch and potentially driven by a distinct claude-toolkit alias — e.g. `/mnt/track1..4`) a bare work-stream label does not say WHICH track/branch/alias produced it, so cross-track dispatches, status reports, and progress lines collide and mislead. ALL hold: (1) **universal label form** — every agent / subagent / work-stream label AND every operator-facing reference (agent-dispatch descriptions, status reports, resume/handoff docs, progress lines) MUST START with a `(T/ - )` prefix; (2) **deterministic derivation, never guessed** (§11.4.6) — `` from the checkout path (`/mnt/track/…`; honest `?` when not under a numbered track, never a guessed number), `` from `git rev-parse --abbrev-ref HEAD`, `` from the `CLAUDE_CONFIG_DIR` basename `.claude-` → `` (honest `?` when unset/non-matching, never a guessed name) (reference labeler `scripts/multitrack/track_branch_label.sh`); (3) **mechanical enforcement** (§11.4.75 / §11.4.109-class) — a PreToolUse guard hook (`constitution/scripts/hooks/guard-track-branch-label.sh`, inherited BY REFERENCE per §11.4.177, never copied) BLOCKS any Agent/Task/TaskCreate dispatch whose `description` (or `subagent` label) does not START with `^\(T[0-9]+/[^ )]+ - [^ )]+\) ` (branch AND alias both required, both non-empty), non-agent tools untouched; pre-build gate `CM-TRACK-BRANCH-LABEL` asserts labeler + hook exist/executable/parseable, hook wired in runtime settings, convention doc exists; (4) **honest boundary** (§11.4.6) — a `?` in the track field OR the alias field is a valid honest label (unknown track / no git repo / no matching `CLAUDE_CONFIG_DIR`), never a bluff; the enforced format surfaces (blocks) an off-track dispatch or a dispatch missing its alias segment rather than silently mislabeling it. Classification: universal (§11.4.17). Composes §11.4.178 (the label-prefix instantiation applied to EVERY agent/subagent label + operator-facing reference) / §11.4.29 / §11.4.75 / §11.4.109 / §11.4.177 / §11.4.6 / §11.4.58 / §11.4.103 / §11.4.119 / §11.4.116 / §11.4.147. Propagation gate `CM-COVENANT-114-182-PROPAGATION` (literal `11.4.182`) + recommended gate `CM-TRACK-BRANCH-LABEL` + paired §1.1 mutation. **Canonical authority:** constitution submodule [`Constitution.md`](constitution/Constitution.md) §11.4.182. Non-compliance is a release blocker. No escape hatch — no `--skip-track-label`, `--unlabeled-agent-OK`, `--bare-work-stream-reference`, `--no-track-branch-prefix`, `--label-from-memory` flag.

Uh oh!

FilesExpand file tree

AGENTS.md

Latest commit

History

AGENTS.md

File metadata and controls