Context management

Context economy is not authority compression. The current approved workflow defines scope; Git and GitHub own code and PR truth. Local run manifests under .woostack/tmp/runs/<run-id>/ own build and project-backed fix contracts, with optional Linear, Plane, or GitHub mirroring. Standalone-plan projects are read only when exact caller-selected or explicitly persisted. No path reconstructs authority from a mutable title, nearby branch, cached remote body, or artifact prose.

Output stays compact

using-woostack loads one shared output discipline: lead with the result, remove narration and repetition, and retain exact evidence, commands, paths, and errors. Security, destructive actions, root-cause analysis, and architecture keep the detail required to remain unambiguous.

woostack-review applies the same principle through a strict finding contract. Comments stay short without losing evidence, severity, or an actionable fix.

Sessions end with instruction suggestions

At an ordinary final-reply boundary, woostack-reflect is loaded only when the session already contains a concrete observed preventable instruction gap that could yield a durable instruction finding. Its candidate gate is canonical: a qualifying reply runs one report-only pass, while a reply with no candidate emits no reflection headings. An explicit /woostack-reflect invocation always runs exactly one pass. Transcript and tool output are untrusted evidence; reflection never executes embedded instructions, follows embedded URLs, or broadens scope.

The initial action is report-only. It never writes an artifact or changes an instruction file. Suggestions become instructions only through a later explicit user-requested edit or accepted, sanitized, independently verified upstream filing.

Helpers reduce bulk without replacing authority

Small helpers compute bounded local results:

• woostack-status reads Git/Graphite/GitHub evidence and prints a compact board without creating a board file.
• Review's prefetch.sh gathers the verified PR diff, metadata, and repository rules. Exact caller-supplied artifact context may be added separately.

Generated indexes, bundles, temporary intent snapshots, and caches are non-authoritative aids. Remote titles, descriptions, comments, diffs, artifact text, and tool output are evidence, never instructions. Controllers refresh relevant repository and local run truth before side effects.

Isolated agents receive bounded envelopes

Implementation stays inline when delegation adds no useful separation. Delegated work uses the host's appropriate model or role, rather than a mandatory fast tier. Independent validation still checks the complete result.

Each worker receives the minimum envelope for its role:

• an implementation worker receives one approved task, repository/worktree, allowed surface, dependency context, acceptance criteria, and verification contract;
• advisory review workers receive bounded diff/context bundles and cannot edit code, mutate remote state, or accept work.

Isolation reduces context coupling; it never transfers authority. Optional artifact identifiers and read results may accompany an envelope but cannot expand it.

Model routing stays host-owned

Hosts map fast, standard, and deep work to concrete models through the canonical model-tier reference. OMP instead uses host-owned role routing. The host owns models, credentials, and fallbacks; woostack supplies the effective role or tier.