developer · AVC

Build against explicit contracts.

Concepts, contracts, events, evidence and design conventions remain implementation-independent.

Developer path

Concept → contract → adapter → evidence.

Framework code is downstream of the system boundary.

01
Understand
Read canonical definitions and the source-of-truth hierarchy.
complete
02
Model
Declare inputs, outputs, states, authority and failure behavior.
complete
03
Implement
Add the smallest vertical slice through the real boundary.
active
04
Verify
Run focused and repository-level checks on exact head.
queued
05
Document
Update status, limitations, recovery and usage evidence.
queued

Contract first

Jobs, capabilities, events, evidence, risk and failure behavior are stable seams that product and UI adapters must preserve.

Source hierarchy

Documentation navigates the system; schemas, services and tests define current behavior.

Verification

Focused tests, build output, integration behavior, security implications and recovery remain part of implementation, not an afterthought.