PROOF: FIRST ENGAGEMENT WORKSHEET

Choose a route: software factory / audit alongside our development / discuss
Component and business consequence:
One change or bounded backlog:
Owner of intended behavior:
Old and candidate revisions:
Build path and required access:

AGREE THE WORK
Intended behavior and authoritative source:
Existing promises to preserve:
Conflicting or unapproved intent:
Affected requirements, code and dependencies:
Risks and operating conditions:
Required observations and why they are sufficient for this scope:
Exclusions and open questions:

AGREE AUTHORITY
Who implements:
Who may approve intent and exceptions:
Repository, network, execution and spending permissions:
Who may accept, merge and deploy (separate permissions):

HANDOFF
Requirements and approval state:
Impact and hazard record:
Checks with expected and observed results:
Exact revisions, commands, environment and raw artifacts:
Finding dispositions and unresolved decisions:
Reusable regression checks and freshness conditions:
Factory scope: proposed implementation and fixing Change record:
Customer ownership, export and exit arrangements:

COMMERCIAL SCOPE
Build/setup work:
Price, compute costs and exclusions:
Handoff date and acceptance criteria:
Ongoing verification responsibilities:
Baseline human effort, rework and time to a decision:
Follow-up measurement on the next related change:

EXAMPLE
Tenant document API migration. Another tenant must receive a rejection and
leave durable state unchanged. Compare responses AND stored rows on the old
and candidate implementations. Include an authorized update as a control.
Concurrency, load and live cutover need additional agreed checks.
This illustrates scope, not a completed customer engagement.
https://reqproof.com/topics/software-correctness-audit#sample-scope