V2-01: Run design-partner discovery and publish the scope decision #8

Outcome

Validate whether OffboardProof's verification-first offboarding workflow is recurring, material, and pilotable before implementation begins.

Deliverables

• Interview 5–8 operators, approvers, or auditors across at least 3 organizations.
• Capture a sanitized baseline: trigger source, provider, controls, handoffs, active time, elapsed time, containment time, exceptions, approvals, evidence, and retention requirements.
• Identify a named pilot trigger, provider path, operator, approval roles, and evidence consumer.
• Confirm signing-key ownership, webhook-secret ownership, and data-handling boundaries.
• Score requested capabilities using the V2 discovery rubric.
• Publish a PII-free decision record: keep, revise, or stop the V2 thesis.
• Decide whether Microsoft Entra ID is committed or deferred.

Acceptance criteria

• At least 3 participants confirm the evidence/verification problem is recurring and material.
• At least 2 organizations identify a viable signed trigger source and will evaluate the evidence bundle.
• At least 1 pilot can run Google Workspace or the mock provider end to end.
• Baseline claims are labeled as measured, participant-estimated, or still unknown.
• If the criteria fail, the record explicitly stops connector expansion and revisits the target problem.

Planning source

.dev/v2/DISCOVERY_GUIDE.md and .dev/V2_PLAN.md in the local planning package.

Dependencies

None. This is the M0 release gate. Implementation must not start before it passes.