developer · AVC

Start with the system boundaries.

Understand missions, capabilities, authority, evidence and exact-head verification first.

Contribution gate

A change is ready only after scope and evidence agree.

The repository remains the integration authority.

Repository truth
Exact base, branch, overlap and instructions are known.
passed
Change contract
Outcome, scope, invariants, risks and evidence are explicit.
passed
Focused behavior
The smallest relevant test or reproduction exercises the change.
active
Broad verification
Type, lint, build, integration and security gates run as applicable.
pending
Exact-head handoff
Status and limitations refer to the commit being reviewed.
pending

Start with truth

Main SHA, active branches, overlapping work, applicable instructions and authoritative contracts define the safe starting point.

Thin slice

Prefer a complete route from input to evidence over disconnected scaffolding that cannot be verified.

Handoff

Commands, exit status, exact commit, unresolved gates and recovery notes form the implementation handoff.