Skip to content

UCCA Fence Ruling Record — 2026-07-01

Ruling 1 — Conformer and gate, both sides (matches RTOpacks' record; closes A-6)

The sender conforms; the receiver verifies. The conformer/adapter is client-side software holding all domain knowledge; the engine-side gate independently verifies conformance — structure, schema version, signature — before ingestion, and bounces malformed jobs whole. Two independent checks of two different kinds; trust boundary = corporate boundary (ADR-0003). Raw regulated corpus never crosses; only the translated, hashed, signed triumvirate does.

Engine-side consequence: the input-path build implements the gate side of this ruling. The gate's published spec (schema, versioning, signature requirements, error model) is what any client's conformer — reference or self-built — builds against.

Ruling 2 — The gate is the warranty boundary (engine terms of service; binds all clients)

Ruled by Tim at the relay, 2026-07-01. Recorded here as its binding home:

  • UCCA supplies a reference conformer/adapter best-effort, as-is — published code, like any vendor's SDK. UCCA does not and cannot warrant its application: deployment context, corpus quality, and translation fidelity live beyond the gate, invisible to the engine by design.
  • The client warrants its own translation — the semantic fidelity of every triumvirate it submits — whether it wired in the reference code or built its own to the published gate spec. Using UCCA's reference code transfers nothing.
  • UCCA warrants from the gate forwards: provenance completeness, envelope integrity, deterministic gate behaviour, and the never-sign property, over every job that passes structural verification.

One line: no warranty before the gate; full warranty after it. The warranty boundary, the trust boundary, and the corporate boundary are the same line.

Consequences: - This clause enters UCCA-INTAKE-01 (engine terms, to write) verbatim — it is client-agnostic by construction and survives the drift-check (nothing in it is VET). - The reference-adapter licence and the DPA liability wording are commercial-legal drafting tasks (flagged to STRATEGY-01's ledger, alongside the existing cross-border and residency items). Jimmy's eyes owed on the RTOpacks side; equivalent counsel owed on this side before any second client signs. - Client One's acknowledgment is on the record in FENCE-RULING-RECORD-01 (received copy).

Gap acknowledged — the parent assessment crosses now

RTOpacks' record correctly notes UCCA-ASSESSMENT-RTOPACKS-BRIEF-01 never crossed as a filed artefact. It exists engine-side as the original of record; the relay carried only the addendum. Corrective: the parent crosses with this relay, completing their received-copy set. No content changes — the fourteen verdicts stand as filed.

Two rulings recorded where they bind; the warranty line drawn where the trust line already was; one relay gap fixed by crossing the missing document. The input path remains unblocked and now has its warranty story.