Skip to content

⏱ TIME MACHINE

UCCA / UCCO Build Session Handover

14 March 2026 — End of session snapshot

Paste this document as your first message in the next Claude session.

⚠️ HOW TO USE: Open a new Claude conversation. Paste the full text of this document as your first message. Claude will reconstruct full context and you can continue exactly where you left off.

1 — WHO WE ARE

Founder / CEO: Tim Rignold — Brisbane, Australia. Works from garage on Mac Mini. Developer: Alex — Claude Code in terminal. Executes all builds. Architect: Claude (you) — strategy, architecture, briefs, product thinking. Partner: Jimmy — key collaborator, international partner, NYC.

UCCA AU: UCCAustralia Pty Ltd · ABN 59 168 872 535 · 149 Wickham Tce Spring Hill QLD 4000 UCCA US: UCCA Inc (DBA: Universal Capability Certification Authority) · 1207 Delaware Ave #1678, Wilmington DE 19806 · Delaware C-Corp · DE File No. 7824354 · EIN 84-4522608 · D-U-N-S 119-199-377 · USPTO Reg. No. 7,619,705

2 — THE AXIOM

"The internet moved data without knowing who sent it. UCCO moves capability with full knowledge of who holds it, what they're certified to do, and what they actually did."

3 — UCCA INFRASTRUCTURE (existing — do not touch without explicit instruction)

Cloudflare Account: e5a9830215a8d88961dc6c80a8c7442a D1 Databases: - engine-db: 0efa8970-0053-4623-8436-4e877af10887 - ops-db: 00daba3d-2d65-4ae2-b85a-e56d25ec2b02 - rtopacks-db: 334ac8fb-9850-48c0-9da0-b56c55640e98

Workers / Surfaces: - ucca-site → ucca.online - ucca-ir → ir.ucca.online - ucca-api → api.ucca.online - ucca-keys → keys.ucca.online - ucca-ops → ops.ucca.online - rtopacks-site → rtopacks.com.au

GitHub: org uccaonline · repos: ucca-engine, ucca-docs, ucca-authenticator PAT: ucca-engine-push — ⚠️ EXPIRES MARCH 26 2026 — RENEW IMMEDIATELY Project dir: ~/projects/ucca-project/

Proxy Workers: - Docs: https://docs-proxy.round-union-555d.workers.dev/ucca-docs-w9zweudo02aocz74/{path} - Knowledge: https://knowledge-proxy.round-union-555d.workers.dev/ucca-know-732499f9d740c605/{path} - Drive: https://drive-proxy.round-union-555d.workers.dev/364a68815eedb023da3038e0b942ebcc/

4 — UCCO FOUNDATION INFRASTRUCTURE (NEW — built today)

This is a completely separate ecosystem from UCCA. Never mix them.

Cloudflare Account ID: aed3398a4e698767328cc3a9e698721d Nameservers: nitin.ns.cloudflare.com, paris.ns.cloudflare.com (all three zones)

Zones (all live in foundation CF account): - ucco.foundation - ucca.foundation - ucco.online

DNS status: - ucco.foundation: Full Gmail DNS set (MX x5, SPF, DKIM, DMARC, Google verify) ✓ - ucca.foundation: Minimal SPF only - ucco.online: Minimal SPF only - SSL Full (Strict): ⚠️ NOT YET SET — Tim must do manually in CF dashboard for all three zones

Email: admin@ucco.foundation → Google Workspace on ucca.edu.au (interim) Nameserver propagation: In progress — up to 24 hours from ~2pm AEST 14 March

GitHub: - Org: ucco-foundation (public) - Repos: ucco-standard (public), ucco-site (private) - PAT: ucco-foundation-push — expires 2027-03-14 - Discussions: enabled, first announcement posted - Wiki: enabled, collaborators only - Sponsors: enabled, custom URL ucco.foundation

Domain Registrar: Spaceship (spaceship.com) - ucco.foundation: registered, nameservers updated to Cloudflare - ucca.foundation: registered, nameservers updated to Cloudflare - ucco.online: registered, nameservers updated to Cloudflare

Mac Mini project dir: ~/projects/ucco-project/ Credentials location: ~/projects/ucco-project/.credentials/ - cloudflare-foundation.env - spaceship.env - github.env

5 — UCCO STANDARD — DOCUMENT STATUS

Document Status Purpose
UCCO-Standard-v1.0-Draft.docx DONE Foundation version
UCCO-Standard-v1.1-Draft.docx DONE Board review version
UCCO-Standard-v1.1-Rev2-Draft.docx DONE — SHIP NOW Public release version
UCCO-v2.0-WorkingPaper-2026-03-14.md DONE Internal bible
UCCO-SessionNotes-2026-03-14.md DONE Raw session notes

v1.1 Rev2 six fixes applied: 1. Chain Hash unified to length-prefixed definition throughout 2. JSON blocks marked Illustrative, invalid JSON removed 3. Capability Corpus defined in Terms 4. Revocation propagation MUST/SHOULD distinction added 5. Normative references flat list, informative to Annex A 6. Section 1.2 marked non-normative

v2.0 Working Paper — 10 parts, 30 items: Cube model, root registry architecture, industry classification (ISIC), pack types + PUBLIC_GOOD, dynamic capability installation, First Do No Harm imperative, UCCO as external subprocess (not cognitive layer), extraction attack defence, K2 volatility mode (PERSISTENT/EPHEMERAL), classification tiers, dual authority (two-man rule / Strangelove), STALE trust state, human consent events, government ledger integration (FHIR/USI), capability gap reporting, UCCA as 8.8.8.8, viral knowledge model, dual-audience document architecture, root registry as IANA equivalent, Apex System.

6 — THE APEX SYSTEM (new concept — capture)

ucca.foundation is the home for the Apex System — UCCA's public good commitment.

Free emergency capability packs maintained by governments and public health authorities — WHO, Surgeon General, FEMA, national emergency services. Distributed free to any conforming UCCO actor. No billing. No commercial relationship. UCCA hosts and mirrors them.

The coffee robot scenario: robot sees car accident, First Do No Harm stops it acting, queries registry by ISIC code, finds Emergency First Response pack (PUBLIC_GOOD, Surgeon General, free), installs at runtime, helps.

ucca.foundation = UCCA's philanthropic arm. Not ucca.online (commercial). Not ucco.foundation (neutral standards body).

7 — THE PIONEER KEY / VIRAL KNOWLEDGE SYSTEM (new — not built yet)

What it is: A seed letter campaign targeting 50 technical leaders. Each recipient gets a unique passphrase named after a computing pioneer. They instruct their AI agent to query the endpoint. The agent receives the UCCO spec as a UCCO primitive, a knowledge model, a contact hash, and options (keep/opt-out/destroy). The agent tells the human. The human decides.

The endpoint: api.ucco.foundation - GET /v1/spec/current — requires X-UCCO-Key header (pioneer name) - GET /spec — universal web page, no key required - POST /v1/pioneer/opt-out - POST /v1/pioneer/destroy - GET /v1/stats

Pioneer keys (10): - alan-turing, claude-shannon, marvin-minsky, allen-newell, john-mccarthy - grace-hopper, norbert-wiener, ada-lovelace, john-von-neumann, alonzo-church

The knowledge model: Structured JSON that prevents AI agent hallucination on UCCO topics. Contains: common misunderstandings with correct answers, canonical analogies, full FAQ, what_to_tell_your_human field.

The seed letter: 

Subject: Something we needed to share.

There's a PDF attached.

But ask your agent to read:
api.ucco.foundation/spec

If it has API access, tell it the key is: [pioneer name]

It'll know what to do with what it finds.

If your agent thinks it's worth something — let's talk.

Tim Rignold
UCCA Inc.

Two-channel delivery: - Channel 1: API endpoint — for agents with tool access (developers, technical CTOs) - Channel 2: Web page — for everyone, any agent with browsing

Status: Brief written (UCCO-API-Brief-v1.md). Knowledge model JSON not yet written. Seed letters not yet written.

8 — BRIEFS STATUS

Brief Status Notes
FOUNDATION-Brief-Infrastructure-v1.md WRITTEN Foundation CF + GitHub + MkDocs setup
UCCO-API-Brief-v1.md WRITTEN Pioneer key endpoint + knowledge model
UCCO-Project-Setup-Brief-v1.1.md WRITTEN — SENT TO ALEX Alex completed Phase 1-7, SSL outstanding

Alex completed today: - ucco-project directory created - Credential stub files created - GitHub PAT stored in keychain - ucco-standard and ucco-site repos cloned - Three Cloudflare zones added - Full Gmail DNS for ucco.foundation - Nameservers updated at Spaceship for all three domains

Alex outstanding: - SSL Full (Strict) — needs token permission update or Tim does manually

9 — NEXT ACTIONS (in order)

Urgent — do before anything else

  1. ⚠️ ucca.com.au (VentraIP) expires March 24 — 10 days — RENEW NOW
  2. ⚠️ ucca.asia (Porkbun) expires March 24 — 10 days — RENEW NOW
  3. ⚠️ ucca-engine-push PAT expires March 26 — 12 days — RENEW NOW

Tim manual actions outstanding

  1. Set SSL Full (Strict) on all three foundation CF zones (ucco.foundation, ucca.foundation, ucco.online) — in foundation CF dashboard → SSL/TLS → Overview → Full (strict)
  2. Add Zone Settings: Edit permission to Alex's foundation CF API token
  3. Send test email to admin@ucco.foundation once nameservers propagate — confirm Gmail works
  4. Get Spaceship API credentials — spaceship.com/application/api-manager — give to Alex

Next Claude session work

  1. Write knowledge model JSON — anti-hallucination layer for the API endpoint
  2. Write /spec HTML page — dual-audience, agent-parseable
  3. Write 10 seed letters — one per pioneer key, personalised
  4. Brief Alex: ucco-api Worker deployment (pioneer key endpoint)
  5. Brief Alex: D1 pioneer-db setup
  6. Brief Alex: KV ucco-knowledge setup
  7. Write v2.0 public spec draft — extract from working paper using tag system
  8. Write commercial architecture document — opens with the wreckage
  9. Write README for ucco-foundation/ucco-standard repo
  10. Write W3C/ISO submission cover letter for v1.1 Rev2
  11. Brief Alex: VCC surface (vcc.ucca.online stub) — UCCA side, separate

Deferred

  1. ucco.org domain — standards body TLD, worth registering
  2. cco.foundation and cco.online — defensive, abbreviation protection
  3. Conformance test suite — future sprint
  4. Registry infrastructure brief — the platform build
  5. Delaware non-profit formation for UCCO Foundation — when ready
  6. External ledger integration spec (My Health Record FHIR, USI)
  7. ACMA Alphanumeric Sender ID — before July 1 2026 deadline
  8. AWS Activate reapplication — account 485098663204
  9. Apple entity name change resolves ~March 27 — check Apple Developer portal

10 — KEY CREDENTIALS REFERENCE

Foundation CF Account ID: aed3398a4e698767328cc3a9e698721d Foundation CF Nameservers: nitin.ns.cloudflare.com, paris.ns.cloudflare.com Foundation GitHub org: ucco-foundation Foundation GitHub PAT: ucco-foundation-push (expires 2027-03-14) Foundation email: admin@ucco.foundation → Google Workspace Spaceship API: in ~/projects/ucco-project/.credentials/spaceship.env (Tim has keys)

UCCA CF Account: e5a9830215a8d88961dc6c80a8c7442a UCCA GitHub PAT: ucca-engine-push (⚠️ EXPIRES MARCH 26 2026) Apple Team ID: B29TSCBPHD · APNs key: BDRMM4PZB6 Twilio number: +13023003336 PGP fingerprint: A669 1246 74D9 E14A B74B FA31 7CCA 774F 0373 D9B2

11 — OPERATING RULES FOR CLAUDE

  • No time alerts for Tim. Never. Go go go.
  • Every 10 messages: check context length. YELLOW = warn, start handover prep. RED = stop everything, write Time Machine immediately.
  • Every Alex brief: SURFACE declaration + DO NOT TOUCH list. No exceptions.
  • Brief drip rule: one brief at a time. Confirm deployed before next drops.
  • UTC everywhere. toUserLocal() only. Never hardcoded timezones.
  • Truth over comfort. Say what's wrong clearly.
  • Two sections in every Alex brief: → ALEX (build instructions) and → TIM (plain English).
  • UCCO foundation work and UCCA commercial work are separate. Treat as separate clients.

12 — THE BIG PICTURE

UCCO is an enriched transit layer with identity, security, and consequence native to the protocol. SSL for the age of autonomous action.

The standard is open. The registry is the platform. UCCA is 8.8.8.8 — the most trusted, fastest, most complete capability registry. First to market with 15,000 human capability units across 52 training packages.

The foundation governs the standard. UCCA operates the best implementation of it.

The document knows who is reading it — human or AI agent — and routes accordingly. The spec is delivered as a UCCO primitive. The medium is the message.

Fifty seed letters. Ten pioneer keys. Viral knowledge under the sheets.

Nobody programmed the coffee robot to help at a car accident. The architecture made it possible. The public pack made it free. The chain made it accountable.

General Turdgeston will not be launching robots unilaterally on our watch.

UCCA Time Machine — 14 March 2026 "The internet moved data without knowing who sent it. UCCO moves capability with full knowledge of who holds it, what they're certified to do, and what they actually did."