context-budget

name	context-budget
description	Bound repository context reads and semantic-search output without weakening source, test, or evidence verification.
metadata	{"origin":"adapted from ZMB-UZH/omero-docker-extended at 246110b1045cfd4ca318b4e870b5a38d213399b6; ECC v2.0.0 reviewed"}

Context Budget

Goal

Limit reads to the minimum high-signal surface required to implement the task correctly, then widen only when evidence is missing.

Workflow

1. Read AGENTS.md.
2. Identify exactly which module and command path is affected.
3. Open one source file, one test file, and one skill that governs the area.
4. Implement with tight scope.
5. If uncertainty remains, open one more implementation file and one more test file only.

Hard limits

• Avoid bulk reading unrelated directories and generated artifacts.
• Avoid opening entire modules for tangential concerns.
• Prefer rg for symbol search over opening large files.
• Keep semantic routing at the five-result default; ten results is the hard maximum. Refine the query or use path/language filters before widening.
• Treat measured UTF-8 output bytes as a context-volume proxy only. Do not infer or publish token savings without a tokenizer-specific measurement.
• Keep a verification ledger with the exact command, relevant tree state, result, and artifact under test.
• Do not rerun a passing gate until its code, configuration, fixtures, dependencies, runtime artifact, or platform input changes.
• Run independent read-only checks in parallel when host resources permit. Serialize builds, model training, and live database or exchange mutations.
• Run the complete required matrix once against the final tree before release.

Exit condition

Before coding the next step, verify that remaining assumptions are either covered by existing tests or addressed by newly added tests.