Skip to content

UCCA — Time Machine — 2026-07-02

Companion: for byte-level repo/build state (SHAs, file paths, the input-path build entry points, infra traps), read UCCA-TM-2026-07-02-TECH alongside this.

Read me first. You are a fresh session. The previous session (2026-07-01→02) was the project's governance-and-contract day: canon went from chat to disk, a cross-company document protocol was ratified and exercised through a complete exchange cycle, three memory-born fictions died, and the input-path contract froze. You open onto a live build, not a blank page.

1. The one-line state

UCCA-CONTRACT-PACK-01 is v1.0 FROZEN (stamp record in the pack cites its four inputs). Canon, register, ADRs, and every crossing artefact are filed, pushed, and strict-build clean on the knowledge/docs sites. The next move is the input-path build — Alex implements against the frozen pack; its Definition of Done is ADR-0002's proof event (job exercised gate→engine→envelope to terminal effect + worlds/ severed from the engine repo). No engine code has been written yet; everything to date is think-file-and-contract.

2. What happened (the arc, compressed)

  • Canon went physical. FOUNDATION-01 and CAPTURE-01 filed (knowledge-site canon/); canon register live; ADR-0001/0002/0003 as files; FOUNDATION §4 corrected twice (CCO→UCCO per ADR-0001; proven run re-identified — see fictions below).
  • FENCE-PROTOCOL-01 ratified (canon, both sides) and exercised through a full cycle: brief → assessment (14 YES) + addendum → response → corrections in BOTH directions → contract pack → payload review → freeze. Read the protocol before touching anything cross-project; Tim is the only relay; verbatim bytes only.
  • UCCA-ADR-LIFECYCLE-01 adopted (Class F/B/G; rulings bind on ruling, mint on proof/verification/ratification). ADR-0002 is F+B: violation minted, remedy ruled (B, pre-proof) — flips when the input path ships.
  • Three fictions died, all memory-born: schema v2.4.1 (cull-spec corrected); the Power BI Excel ingest path (their correction — truth: world-side TGA REST-API sync + R2 dated snapshots); "proven on retail unit Dec 2025" (our correction — truth: CHCPRT025, care unit, 2026-03-09; the Dec-2025 run is attested history, not proof — founder testimony, artefact lost in the move, hunt run, deleted-presumed).
  • Yellow-tape rule + fossil-ledger.md now standing convention: tape history, delete false present-tense, log everything with how-we-know. Founder testimony on the engine's flat pre-boundary origin is in ADR-0002's context.
  • Three relay rulings recorded both sides (see UCCA-FENCE-RULING-RECORD-01 v1.0.1): conformer client-side / gate engine-side; no warranty before the gate, full warranty after it (engine terms — enters UCCA-INTAKE-01 verbatim); engine-published canonical document schema (their ack adopted it against their own earlier position).
  • ADR-0003: two companies, one link (a commercial data-processing arrangement). UCCA Inc (US) = the engine/Authority; the AU Pty Ltd operates RTOpacks. Trust boundary = warranty boundary = corporate boundary = the gate.

3. True and verified (don't re-derive, don't spook)

  • The frozen contract (docs-site strategy/, pack + ucca-content-payload- schema-v1.json): async-first job model (submit→job-id→poll/webhook, no sync call, no SLA); diagnosis endpoint = honest 501 stub with full gate checks; four parsed envelope surfaces; provenance block satisfies the client's Q-A3 completeness test; citation kinds split (dated raw snapshot = pointer; normalised hash = attestation); two ingest surfaces never merged; payload IDs at module/block/question level, stable within artefact version only — regeneration = new version + new IDs; requirement side (the triumvirate) is the cross-version anchor.
  • One interpretation flag riding: blocks encoded as modules[].blocks[] (Alex's call, ratified). If RTOpacks' conformer expected different block encoding, it's a v1.1 clarification, not a re-freeze.
  • The engine repo still contains worlds/ + TGA residue — the ADR-0002 violation is live until the build severs it. The engine no longer ingests anything and never connects to TGA (standing ruling: false present-tense claims of engine↔TGA connectivity are deleted on sight, not taped).
  • Docs-site/knowledge-site March-era material is deprecated in voice — mechanics may bind where ADR-ratified; canon wins every conflict. Cull spec exists; banner sweep may still be in progress — check with Alex.

4. Live forward

  1. The input-path build (Alex, against the frozen pack §10). Support it; apply the drift-check to every implementation decision.
  2. The stamped-pack crossing (~/Downloads/ucca-stamp-crossing-2026-07-02/) has crossed to RTOpacks (2026-07-02) — their conformer builds against it. The one open return is their block-encoding confirmation (modules[].blocks[] — v1.1 clarification if it diverges, not a re-freeze). [CLOSED 2026-07-03 — RTOPACKS-CONFIRM-PAIR-RECEIPT-01: "our conformer will validate against it"; encoding accepted as-is, no divergence. Ledger zero both directions.]
  3. To write, engine-side: ~~UCCA-NORTHSTAR-01~~ filed & ratified 2026-07-02 (canon/UCCA-NORTHSTAR-01.md). Remaining: UCCA-INTAKE-01 (engine terms; carries the warranty clause verbatim; generalises the old §5 questions into the client-agnostic brief template) — now the oldest canon debt.
  4. Residuals, none blocking: three ⟨TIM/JIMMY⟩ items (hand-raise tolerance; lived sign-off practice; performance-assessment colour); legal ledger items for STRATEGY-01 (DPA wording, cross-border/residency, reference-adapter licence).

5. Parked (deliberate, not loose)

Diagnosis build (after input path; contract stub already holds its place) · STRATEGY-01 · pitch deck · further canon stones · RTOpacks' normalised-layer dated versioning (their backlog; the contract deliberately does NOT depend on it).

6. Principles the next head must not undo

  • The fence is real: verbatim bytes only; never file from summaries or chat scroll; never self-serve from the other repo; the relay checks the package (three relay gaps were caught this session by exactly that habit).
  • "Prepared from project memory" is a warning label, not a source. Testimony counts when labelled and filed. Attested ≠ proven: an event without an artefact is a memory; the ledger deals in artefacts.
  • Observation-typed ≠ intent-typed: schemas derived from runs describe what happened; contracts state what's promised. (Their review taught us this; it's engine practice now, with attribution.)
  • Nothing executes against a draft — the stamp is the execution gate. Rulings bind when ruled; builds start when documents freeze.
  • The engine raises hands, never signs; outputs speak about material, never persons (two-lens rule, contract §4.4 — testable, and it will be tested).

7. First questions next session

  1. The stamped-pack crossing has landed at RTOpacks (2026-07-02) — has their conformer confirmed the block encoding yet? (The only open return on the freeze.) [ANSWERED 2026-07-03: yes — RTOPACKS-CONFIRM-PAIR-RECEIPT-01. Ledger zero both directions.]
  2. Has Alex broken ground on the input path — and does he need the build brief expanded from pack §10, or is the pack sufficient spec? Then get out of the way of the build, and write NORTHSTAR-01 while it runs.

8. Pointers (the index — go here, not to this TM)

Knowledge-site: canon/ (FOUNDATION-01 as corrected · CAPTURE-01 · register · fossil-ledger · UCCA-ADR-LIFECYCLE-01 · UCCA-FENCE-ADOPTION-01) · decisions/canon/ (ADR-0001/0002/0003) · canon/sent/ + canon/received/ (every crossing artefact, including FENCE-PROTOCOL-01 and both correction docs). Docs-site: strategy/ — UCCA-CONTRACT-PACK-01 v1.0 FROZEN · ucca-content-payload-schema-v1.json · the March adapter design (historical mechanics). RTOpacks side (via relay only): their originals of everything under crossings/. Access/infra state: unchanged from UCCA-SEED-01 — note: the SEED itself is still not filed in this repo (register row is honest about it); re-verify tokens before any cloud action; the three traps (CF_ACCOUNT_ID pin, export-don't-source, wire-by-UUID) still apply.

Time Machine, 2026-07-02. Proper close at the freeze. One day took the project from "canon exists in a chat window" to "a frozen, citation-verified, cross-company contract and a build with a definition of done." Three fictions died; every claim that survived has been tested against bytes, testimony, or a crossing. Next head: confirm the crossing landed, support the build, cut the North Star. Pointer points; the staves hold the rest.