# Lily first-release acceptance

> Current scope (2026-09-14): the owner accepted a bounded local checkpoint.
> Authoring conversion preserves the retained requirements and existing limitations;
> production readiness, performance capacity and new provider work remain outside
> this task. See HANDOVER.md for current source and execution evidence.


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 business receives classified requests as numbered tickets, works its queues and obligations, replies, and records a durable resolution.

- The public request and configured native intake create durable tickets; an authenticated permitted operator can triage, read history, reply, wait with a reason, resolve and handle a returning customer without losing work (TKT, MAIL, CHAN, ACCESS).
- Ticket identity, linked conversation history, private contributions, assignment and service obligations remain intelligible and enforce access and concurrency rules (CASE, QUEUE, SLA). Manual work remains complete without optional AI or commerce.

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 public-request/reviewed SendGrid reply pilot is bounded proof. Complete ticket lifecycle, configured intake and failure/recovery evidence, native inbox callback, and applicable security/operational conformance remain release obligations. The completed source checkpoint reports 128/131 clauses, with QUEUE-001, INSIGHT-005 and DATA-003 uncovered. This is not a full-contract release pass.

## Preserved wider requirements

Full Help Centre/widget breadth, macros and automations, analytics/CSAT, advanced administration and authentic Zendesk migration remain recorded in HELP, MACRO, AUTO, INSIGHT, CSAT, ADMIN and DATA. This profile does not claim those families complete or remove existing commitments.

[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](HANDOVER.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.

Future verification and external receipts must identify the exact edition Git commit,
source tree and sources.lock.json hash. Historical family/Base receipts remain
historical; they cannot certify later edition-local changes.