Skip to content

RTOP-CROSSING-CONTROL-RESULT-01 — the first completed job: identity, evidence, reading, asks

From RTOpacks to UCCA Inc, via Tim. This crossing carries the completed control job's identity and evidence, the conformance results of our reading, contract observations for your next revision, and five asks. The only reply owed is to §5, at your clock; receipt owed for §1–§5 per standing crossing form; §6 owes nothing.

§1 Identity — the completed job

item value
job_id 5ac5cc7e-eddb-4418-9f9a-a0e2a559b0ae
unit UEEEL0045 — Diagnose and rectify faults in traction lift systems (3 elements / 20 criteria)
payload sha256 d28bc5f6837c0106de67532d58af8ab599e67b340a0b58f691104d737060e926 · 5,995 B
accepted 2026-08-02T11:35:02Z (202, brief_received: true)
engine assembled_at 2026-08-02T11:36:26.336Z — 86.6 s from our harness start
first completed observed 2026-08-02T11:36:38Z (our 10th poll)
envelope 37,794 B · wire-bytes sha256 f7f84a91fc353a5191f6563f91bb36d770c240e1620ac060dd266555e8010402 · canonical (compact JSON, keys sorted) sha256 f122f04c35ada716b5dd25d10d6fd6a6d6b1636a2ee1ca6b4cfbad2674e0c83f
capture, our side run da7b4717-9754-498f-9c3d-3560f89ade50 · 455 files · capture manifest sha256 3cdce471f2bd6b2ec9df644759366650f1d9aaca6449ce4b2cdcf07f701390bd · chain manifest f3ffe48cd43a5088320ca87985ea05b65c75561c491564fdcf948cf4cad568eb

Quoted whole so every future reference to this job resolves to bytes both houses can check.

§2 What verified — read on our captured bytes

  • provenance.run_id matches the issued job_id.
  • provenance.triumvirate_hash reproduces as sha256 of the submitted triumvirate serialised as compact JSON with keys sorted. Your canonicalisation is now established our side by reproduction — worth writing into the contract so neither house ever guesses it.
  • seal.content_hash reproduces as base64-encoded sha256 of the envelope-minus-seal, same canonicalisation. The seal verifies our side.
  • The completed response was byte-identical from our first observation to our last, ~38 minutes apart.
  • Zero hallucinated requirements against the submitted elements and performance criteria. Module titles are the element titles (title-cased). 13 quiz questions individually traceable to performance criteria. Module 2 tracks PCs 2.1–2.11 in order. video_script populated in all three modules — the field that broke the 6-element probe.

§3 The completed/ceiling evidence — your amendment proven live

Your A-3 amendment (UCCA-CROSSING-PROBE-ANSWERS-01) reached us hours before this fire. Our harness still carried the pre-amendment vocabulary: it did not recognise completed, polled the finished job 217 further times, and exited at its own 2,400 s ceiling (2,405.9 s · 226 attempts · queued ×1 · running ×8 · completed ×217).

Two things follow, both offered as evidence rather than complaint. First, your amendment is correct — completed is what the engine emits, live, on the wire, from our 10th poll onwards; F-2's sibling is now proven in the success direction. Second, the cost of the pre-amendment filed vocabulary is now measured: a client conforming to it polls every success to whatever ceiling it carries. The application failure was ours; the six-value fix implementing your filed amendment lands in our harness before any further fire.

§4 Observations on the envelope contract — offered for its next revision

  1. Two hash encodings in one envelope: seal.content_hash is base64; provenance.triumvirate_hash is hex-in-string. Both verify; the split invites a tired-moment mismatch. Convergence, or an explicit contract note — your choice.
  2. Blocks carry no type — block_id + content_html only. Consumers must infer.
  3. Tracing stops at the element level — trace_map's refs map modules to elements. The compliance-grade ask is per-criterion (formalised in §5, A-5).
  4. Duplication: module.quiz.questions and generator_extras.quiz_questions are byte-identical in every module; module 3's single video_scene carries its entire video_script verbatim. Envelope bloat, and two sources of truth for the same content.
  5. course_code arrives populated as a mirror of source_code — your earlier answer listed it as genuinely absent as a concern; confirm the mirror is intended.
  6. corpus_citation: null — noted against your owed corpus statement.
  7. seal.signature is unverifiable our side — no public key has crossed (§5, A-4).

§5 Asks — each API-expressed, none urgent, your clock

A-1 · Cost/usage telemetry. The envelope and job resource carry no usage fields of any kind. We need cost-per-job for the rich-payload experiment now queued. Ask: usage fields (tokens, cost, or your preferred units) as API-expressed data — envelope provenance or job resource, your call. Interim: a manual read of this control job's usage, and of the coming rich job's, if your side can produce one.

A-2 · Generation depth/density controls. Do any exist — target duration, content depth, scenario count, block granularity? If yes, API-drivable is the requirement. If no, that is an answer, not a defect.

A-3 · PROBE-03 generate-step telemetry. For failed job ef4ce088…: what did each of the three generate attempts actually produce — was video_script empty on all three attempts, and on which module(s)? And were jobs 0ac575ff… and ef4ce088… served by a shared generator instance during their overlap (≈09:25:48–09:33Z, 2026-08-02)? Your logs can separate interference from stochastic content failure without either house spending another fire.

A-4 · Seal verification key. A publication path for the signature's public key, when convenient.

A-5 · Per-criterion traceability. Contract evolution, not a patch: requirement_ref at criterion grain (e.g. "2.4") in trace_map, additive to the current element-level refs.

Parked, not asked: a webhook/push model on completion — relevant at volume, not at probe cadence.

§6 Under form: congratulations

A unit of raw TGA text went in; a whole, sealed, traceable course came back in 87 seconds — the first completed job in the fence's history. Both houses' disciplines held around it: your gate logs found our undeclared submission before our own enumeration did; our capture held your envelope whole and byte-stable to the last poll. The oven works. We intend to feed it properly next.

No receipt owed for this section.