# Local code and test work

For an explicit task with resolved scope and applicable delegation, proceed with
local code edits and stronger tests without redundant human approval. The v0.8
HOT/build/L0 non-tenant envelope illustrates that delegation; it does not infer
the current estate grant. Check repository instructions and actual task scope.

Keep policy changes fixture-first and explain the accepted constraint a check
encodes. Do not weaken checks to pass, approve your own widening, or transfer
HOT precedent into a COLD/tenant envelope. Negative memory about the same
decision shape requires escalation until cleared. Missing evidence can be
produced through authorized tests; missing authority cannot be produced by tests.

For this repo: Python 3.11+, `pip install -e '.[test]'`, then
`python3 -m pytest -q`. The knowledge CLI is read-only orientation and cannot
approve an effect. State the consulted source/package version and test evidence
in the work record. A source conflict or unknown target goes to the task owner.

Source owner IDs (cite the relevant owner, not an invented umbrella): `emergent-security`, `the-custodian`.