# Brook 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

An email-first team triages requests using customer evidence, resolves them through reviewed replies and, when configured, explicit operator-approved refunds.

- Native email intake, shared triage, readable private/customer history, a reviewed reply and recorded resolution form a complete journey; failures and unknown sends remain visible (MAIL, TKT, OPS, QUEUE).
- Configured commerce shows real evidence, freezes the reviewed target and amount, authorizes one refund, performs current preflight, reconciles uncertainty without repeating the effect and records confirmed outcome. Customer reply approval remains separate (ACT). Evidence-backed guidance must be truthful; missing AI is named, never simulated (GUIDE, AI).

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 hosted pilot proves one Stripe TEST AUD1 refund, reconciliation/replay protection, native intake and one provider-accepted reply. It does not establish live-money effects, mailbox delivery, full mail handling or operational recovery. Operator management, accepted attachment handling, mail recovery, guidance and applicable baseline acceptance remain open; see IMPLEMENTATION.md.

## Preserved wider requirements

Full AI and guidance versions, calendars and queue breadth, participant/attachment handling, notification/feedback, search/merge/deletion and import/export remain preserved in GUIDE, AI, QUEUE, MAIL, NOTE, FB, TKT, CUST and DATA. Some are first-release blockers where the selected workflow needs them; none is satisfied by this profile.

[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/pilot-20260912/REPORT.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.