# Ferry first-release acceptance

Recorded 13 September 2026. **Status: incomplete.** This defines the useful
first-release outcome; it is not a new test registry or a certificate of release.

## Purpose and minimum outcome

A small sales team turns slipping deals into an explainable intervention, credible next activity and buyer commitment, then records the deal outcome.

- Create and maintain linked contacts/deals, stage and close/reopen deals, plan/complete activities and maintain customer commitments with attributable history and conflict handling (PIPE, REL, ACT, COMMIT, EVID, STORY).
- The decision board and Intervention Brief explain the real evidence and business-time deadlines. A human reviews the exact follow-up before a durable send; acceptance, failure and uncertainty remain separate and do not fabricate buyer progress (TEAM-003, INT, MAIL).

A complete first release also requires an honest empty installation, owner-controlled
setup and repeat deployment preserving data, authenticated and authorized access,
input/privacy boundaries, recoverable failures and data export/restore appropriate
to its stored data. Verify these in the real runtime with the selected providers,
including desktop/mobile use. Applicable guarantees in [BASELINE.md](BASELINE.md)
remain obligations. A missing proof is open, not passing or automatically waived.

## Unmet release obligations

The deployed pilot proves record creation, activity completion, business-zone display and activity-driven health. Follow-up Send remains disabled and deal/commitment lifecycle is incomplete: both block the useful first release. Full failure/concurrency recovery, operational acceptance and current release-candidate evidence remain open.

## Preserved wider requirements

Advanced pipeline configuration, record/import/export/custom-field breadth, operator administration, Insights and reminders remain preserved in PIPE, TEAM, IMPORT, EXPORT, FIELD, INSIGHT and ACT. Required workflow integrity cannot be deferred merely by labelling a feature advanced.

[CONTRACT.md](CONTRACT.md) remains unchanged and authoritative for its declared
guarantees, including any full-1.0 release conditions. This narrower first-release
profile prioritizes a useful outcome; it does not reclassify clauses, waive an
owner requirement, or authorize a full-1.0 label. A conflict with an existing release
condition remains explicit and unresolved until its scope is deliberately settled.
All unmapped clauses remain in the original contract with their existing status.

## Evidence and decision rule

Read [the handover](HANDOVER.md) and [dated pilot evidence](verification/2026-09-12-justevery-pilot/README.md) for exact
source versions, executed checks and limitations. These are historical receipts,
not a fresh verification of this document's candidate. Publication is independent
of deployment and product acceptance; a published tree is not a release verdict.

Report four separate results: executed gates (including failures and skips), unmet
first-release obligations, preserved wider backlog, and external unknowns. A green
`verify` proves only its executed gates. Mark this first release complete only when
its minimum outcome and applicable guarantees have evidence on the exact candidate,
remaining scope conflicts are resolved, and every external claim names what was
actually observed. Provider acceptance alone never proves mailbox delivery or a
confirmed business effect. Retain test-session and test-mode limitations.