Orchestrata Ultimate / Briefs

Briefs

A brief is the whole prompt a coordinator hands to a worker agent. The worker is a fresh session that sees nothing else, so the brief carries the goal, the files it may touch, the guards, the proof it must produce and the stop rules. In this project briefs are checked by a hook before they leave, enriched on the way, and gated again when the worker stops.

Read Writing a brief for the rules and the measured lessons, and Brief templates for every template, quoted in full.

Dispatch flow

• Validation. task_context_hook.py runs before every Agent call. It requires the five labels GOAL:, FILES:, CONSTRAINTS:, DONE WHEN: and VERIFY: and, for development and testing tasks, a .py path inside FILES:. A separate design hook (RUL-022) asks builder, wirer and refactorer briefs for a DESIGN_WAIVER: line.
• Enrichment. The hook appends the categorised methodology blocks and, for the modules named in FILES:, their AST and Prolog-inferred dependency contracts, once per session (blocks are hashed into a ledger so nothing is injected twice).
• Stop gate and ledger. Per the maintainer's notes, a SubagentStop hook holds a worker until ~/bin/precommit-check reports PRECHECK-OK, and every finished worker appends a line to ~/.local/state/codetools/dispatch-ledger.ndjson. Those two facts come from notes, not from a read of the hooks in this run. See the dispatch ledger.

Every brief in plans/briefs/ (69 markdown briefs)

Date is the filename date when present, else the date the file was first committed. Target is what the brief itself names near its top (executor, model, worktree); "not stated" means it names none of them. Page links follow plans/briefs/<name>.

Data files in the same directory, with no page: c3_run1.json, c3_run2.json, c3_run3.json, full_suite_run2.json.

Related

• Writing a brief
• Brief templates
• Plans
• Dispatch ledger
• Workflow
• Gates
• task_context_hook
• Orchestrata Ultimate