Context budget

majordomus://rule/majordomus.context-budget@1active contextbudget

it references

depends_on majordomus.minimum-sufficient-context@1
depends_on majordomus.projection-integrity@1

referenced by

exercises hand-work-between-sessions
exercises keep-the-bootstrap-thin-and-within-budget
exercises read-only-the-context-that-fits
exercises resume-from-a-prompt-asset

Rationale

The always-loaded projection stays within its line budget, every reference in it resolves, it states no count that will go stale, and the assembled context fits the builder's own budget.

Required behaviour

The always-loaded projection stays within its budget, every reference in it resolves, it states no count that will go stale, and the assembled context fits its own budget.

Failure behaviour

A violation is a FAIL finding under the category budget, and the command that found it exits 10. Under watch the same violation is reported as drift and the command exits 11.

Verification

mj_validate_budget decides it, dispatched from doctor, watch. The behavioural case test/cases/02_doctor_basic.sh proves it, and CI runs that case.

Where this comes from

canonical file: .ai/repo/rules/vendor/majordomus/rules/context-budget.v1.md
identity: majordomus.context-budget@1
also served as: MCP resource majordomus://rule/majordomus.context-budget@1 · majordomus entity show rule/majordomus-context-budget-1 · GET /api/v1/entity?uri=majordomus://rule/majordomus.context-budget@1
in the Cockpit: /cockpit/objects/rule/majordomus-context-budget-1

This page is generated from the file above by scripts/generate-site-data; editing the page changes nothing, editing the file changes every surface. The relations above are edges of docs/generated/graph.json, which the executable writes from the same index.