Skip to content

title: UCCA — Ruling — INTAKE-01 warranty scope + offboarding terms doc_id: UCCA-RULING-INTAKE-TERMS-01 type: ruling record — Tim's rulings on the two open ⟨TIM⟩ markers in UCCA-INTAKE-01. Carries drafted clause language for integration; final wording placement is Alex's layout call, substance is fixed here. layer: decisions (append-only) canonical: false ruled_by: Tim, 2026-07-03, verbatim: "on 1 its a yes on 2 agreeded" — (1) warranty bounded to the envelope; (2) offboarding as the documented clearance process proven with the first client. authored: 2026-07-03 NYC (Claude-web, formalising for filing) relates_to: UCCA-INTAKE-01 (closes both its ⟨TIM⟩ markers) · UCCA-FOUNDATION-01 §2 (raises hands, never signs) · ADR-0005 (provenance- only seal) · RTOPACKS-RESPONSE-MIGRATE-02-PHASE-6-01 + UCCA-RETIREMENT- UNIT-BRIEF-01 (the lived offboarding process the termination clause promises) · proof job 0dda7509 (the exhibit for the warranty boundary)

Ruling — the two INTAKE-01 terms

1. Warranty scope — RULED

The engine warrants the envelope, never the content's fitness.

Covered by the warranty (after the gate — per the standing rule "no warranty before the gate; full warranty after it"): - Structural conformance — the payload validates against the frozen, versioned contract schema in force for the client. - Provenance — the envelope's account of how the artefact was produced (inputs, trace, model calls, cost) is complete and true. - Signature integrity — the seal is cryptographically valid over the exact signed bytes, verifiable by the client independently. - Atomicity — an envelope is whole or it does not exist; no partial artefact is ever delivered (partial-failure-is-failure).

Explicitly OUTSIDE the warranty: - The content's fitness for the client's regulatory purpose. That judgement is human, on the client's side, always — the engine raises hands and never signs (FOUNDATION-01 §2). The seal attests provenance only (ADR-0005); it is not, and never becomes, a verdict on the work.

Drafted clause (substance fixed; Alex fits the words to INTAKE-01's voice):

UCCA warrants each delivered envelope: that its content conforms structurally to the contracted schema version, that its provenance record is complete and accurate, that its signature is valid and independently verifiable, and that envelopes are delivered whole or not at all. UCCA does not warrant, and the certification object does not assert, that the enveloped content is fit for any regulatory, professional, or accountable purpose. That determination remains at all times the client's, made by a qualified human. The engine's seal attests provenance, never judgement.

2. Termination / offboarding — RULED

On termination, client data is retired under a documented, client-confirmed clearance process — the process proven with the first client, 2026-07-03, now promised as a term:

  1. UCCA identifies and discloses all client data resident in the engine's infrastructure.
  2. The client confirms in writing: function takeover, data currency, and any final-export requirement (with format and destination if so).
  3. Clearance is granted by the client, with any exclusions stated.
  4. Retirement executes as one reviewed unit — logged per resource, safety mechanisms (backups) retired last, and any data found without a confirmed successor stops the process and returns to the client for adjudication before deletion.
  5. The client receives written confirmation when the unit is closed.

Drafted clause (same terms):

On termination, UCCA will disclose all Client data resident in its infrastructure and will not delete any of it except under a clearance the Client has confirmed in writing — including the Client's statement of data currency and any final-export requirement, which UCCA will fulfil before retirement. Retirement is executed as a single reviewed and logged unit, with backup mechanisms retired last; any Client data found without a confirmed successor halts retirement and is returned to the Client for decision. UCCA confirms completion in writing.

Consequences

  • Both ⟨TIM⟩ markers in UCCA-INTAKE-01 are CLOSED by this ruling. Alex integrates the clauses (voice/placement his), flips INTAKE-01's open markers, updates the register row.
  • INTAKE-01's status may advance out of DRAFT once integrated — whether it is then ratifiable in one pass is Alex's report to make and Tim's word to give.
  • Nothing here crosses the fence. These are engine-side terms for future clients; RTOpacks' own arrangement is already governed by the filed contract pack.

Ruling record. The warranty ends where human judgement begins, and the exit is the process we proved before we promised it. The last two open decisions of the sprint, closed on the day the engine went live.