⏱ TIME MACHINE¶
UCCA / UCCO Build Session Handover¶
14 March 2026 — Session 2, 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¶
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): ⚠️ Tim must set manually in CF dashboard for all three zones
Email: admin@ucco.foundation → Google Workspace on ucca.edu.au (interim) Security email: security@ucco.foundation — ⚠️ NOT YET CREATED — needs alias or forward to admin@ucco.foundation before seed letter campaign
GitHub: - Org: ucco-foundation (public) - Repos: ucco-standard (public), ucco-site (private), ucco-ops (private — to be created) - 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)
Mac Mini project dir: ~/projects/ucco-project/ Credentials location: ~/projects/ucco-project/.credentials/
5 — WHAT WAS BUILT THIS SESSION¶
A. ucco.foundation Main Site (Brief v2)¶
Status: WITH ALEX — building now - Next.js 15 + Tailwind CSS, deployed to Cloudflare Pages - Video hero — full-bleed looping background video from After Effects with blueprint overlay effect. Tim producing the AE video in parallel. Site deploys with dark fallback background until video is ready. - Below-fold: dark premium design (#0A0F1A), paper-coloured text, DM Serif Display headings, IBM Plex Mono body - Sections: Hero → What is UCCO (3-col) → The Standard (spec card + TOC) → Participate → Footer - Staggered fade-in animations on hero, scroll-aware sticky nav - Video placeholder system: poster.jpg + mp4 drop into public/video/, site looks complete without them - Brief file: UCCO-Site-Brief-v2.md
B. ucco-standard Repo Dressing¶
Status: READY TO SHIP — queued behind site deploy confirmation 13 files total: - CONTRIBUTING.md — structured editorial process (propose → discuss → draft → review → resolve), RFC 2119 conventions - GOVERNANCE.md — rough consensus (IETF model), spec lifecycle (Draft → Candidate Release → Published Standard), semantic versioning, editorial team roles - SECURITY.md — responsible disclosure, 48hr acknowledge, 7-day assessment, coordinated disclosure - CODE_OF_CONDUCT.md — Contributor Covenant v2.1 adapted for standards work - LICENSE — CC BY 4.0 for spec, Apache 2.0 for future code - CITATION.cff — makes repo citable in academic contexts - .github/ISSUE_TEMPLATE/clarification.yml — structured issue form - .github/ISSUE_TEMPLATE/proposal.yml — structured issue form - .github/ISSUE_TEMPLATE/error.yml — structured issue form - .github/ISSUE_TEMPLATE/config.yml — redirects general Qs to Discussions, security to SECURITY.md - .github/PULL_REQUEST_TEMPLATE.md — PR checklist - social-preview.png — 1280x640 card for repo link sharing (rendered with system fonts; re-render locally with DM Serif Display + IBM Plex Mono for final version, or swap with AE frame) - REPO-SETTINGS.md — description, website, topics for GitHub UI (not committed to repo, instructions for Alex)
Repo settings to apply: - Description: "The open standard for cryptographic capability certification — for human and autonomous actors." - Website: https://ucco.foundation - Topics: open-standard, capability-certification, cryptographic-credentials, identity-verification, autonomous-agents, specification, verifiable-credentials, trust-framework
License choice: CC BY 4.0 — use it however you want, just say where it came from. No copyleft, no non-commercial restriction. Same as W3C. Maximises adoption while keeping attribution.
C. UCCO Knowledge Model (ucco-knowledge-model-v1.json)¶
Status: DONE — ready for deployment when pioneer API Worker is built Anti-hallucination JSON for AI agents. Contains: - what_is_ucco: one-sentence, one-paragraph, axiom - canonical_analogies: TCP/IP, shipping container, DNS/8.8.8.8 - common_misunderstandings: 8 corrections severity-ranked (blockchain=critical, VC=critical, LMS=high, education-only=high, CA=medium, AI safety=medium, UCCA-owned=high, Merkle=medium) - key_concepts: dual-key, chain hash, capability corpus, trust states, First Do No Harm - entities: UCCO Foundation, UCCA Inc, UCCA Foundation with clear role delineation - faq: 8 canonical Q&As - what_to_tell_your_human: 4 audience variants (technical, non-technical, decision maker, pioneer key) - pioneer_key_context: instructions for agents receiving the model via API - meta: flags that the object is itself a UCCO primitive
D. /spec Page (ucco-spec-page.html)¶
Status: DONE — ready to deploy as a route on ucco.foundation or ucco.online Dual-audience HTML page: - Humans see: clean dark page, spec overview, key concepts as cards, corrections in visual format, participation links - AI agents see: HTML comment block with explicit instructions and common mistakes, JSON-LD structured data in head, hidden DL metadata block, semantic HTML - Matches the main site's visual design (same palette, typography, dark premium feel) - Includes "What UCCO Is Not" section with strikethrough wrong claims and corrections — designed to be scraped by agents
E. Ops Panel Brief (UCCO-Ops-Brief-v1.md)¶
Status: WRITTEN — queued behind repo files deploy confirmation - ops.ucco.foundation — Next.js + Tailwind, Cloudflare Pages with Functions - CF Access auth: One-Time PIN to admin@ucco.foundation - Panels: Zone Health (3 zones) → Analytics (7-day, CF Analytics API) → GitHub Pulse (ucco-standard stats) → Pioneer Keys (placeholder) - Server-side API routes proxy CF and GitHub APIs (tokens stay server-side) - Fallback: if @cloudflare/next-on-pages fights, deploy static frontend + separate API proxy Worker - Requires Tim to create CF API token and set env vars before real data flows - New private repo: ucco-foundation/ucco-ops
F. AE Video for Hero¶
Status: TIM PRODUCING — in parallel - After Effects blueprint overlay template (MotionPitch) - Takes real footage, applies edge detection + blue grade + grid overlay - Content sequence: industrial robot → person working → abstract tech/LLM → architecture - Delivery: H.264 mp4, 1920x1080, <8MB, 10-15 sec seamless loop, no audio - Poster frame: JPEG still for instant load - Blueprint blue range: #1B3A5C to #2060A0 - Keep important content in central 70% (object-cover crops edges) - Drop into public/video/ucco-hero.mp4 and public/video/poster.jpg, rebuild, redeploy
6 — 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 |
| ucco-knowledge-model-v1.json | DONE | AI agent anti-hallucination layer |
| ucco-spec-page.html | DONE | Dual-audience /spec page |
7 — BRIEF PIPELINE¶
| # | Brief | Status | Ships After |
|---|---|---|---|
| 1 | UCCO-Site-Brief-v2.md | WITH ALEX — building | — |
| 2 | Repo files (13 files) | READY | Site deploy confirmed |
| 3 | UCCO-Ops-Brief-v1.md | WRITTEN | Repo files confirmed |
| 4 | Pioneer API Worker brief | NOT YET WRITTEN | Ops panel confirmed |
| 5 | D1 pioneer-db setup brief | NOT YET WRITTEN | Pioneer API brief confirmed |
| 6 | KV ucco-knowledge setup brief | NOT YET WRITTEN | Pioneer DB confirmed |
Alex CLAUDE.md addition (pending):
ALWAYS confirm CF account ID matches the brief BEFORE any wrangler command.
UCCA: e5a9830215a8d88961dc6c80a8c7442a
UCCO Foundation: aed3398a4e698767328cc3a9e698721d
8 — NEXT ACTIONS (in order)¶
Urgent — do before anything else¶
- ⚠️ ucca.com.au (VentraIP) expires March 24 — RENEW NOW
- ⚠️ ucca.asia (Porkbun) expires March 24 — RENEW NOW
- ⚠️ ucca-engine-push PAT expires March 26 — Tim aware, handling
Tim manual actions outstanding¶
- Set SSL Full (Strict) on all three foundation CF zones
- Send test email to admin@ucco.foundation — confirm Gmail works
- Create security@ucco.foundation alias (forward to admin@ucco.foundation)
- Get Spaceship API credentials
- Create CF API token for ops panel (Analytics:Read, Zone:Read, SSL:Read on foundation account)
- Produce AE hero video and drop into public/video/
- Re-render social-preview.png with proper fonts (DM Serif Display + IBM Plex Mono) or swap with AE frame
- Upload UCCO-Standard-v1.1-Rev2-Draft.pdf to ucco-site public/ directory
- Add custom domain ops.ucco.foundation in CF Pages dashboard (after ops panel deploys)
Next Claude session work¶
- Write 10 seed letters — one per pioneer key, personalised
- Brief Alex: pioneer API Worker (api.ucco.foundation endpoints)
- Brief Alex: D1 pioneer-db setup
- Brief Alex: KV ucco-knowledge setup
- Write v2.0 public spec draft — extract from working paper
- Write commercial architecture document
- Write W3C/ISO submission cover letter for v1.1 Rev2
- Brief Alex: VCC surface (vcc.ucca.online stub) — UCCA side, separate
- Pinned GitHub Discussion: welcome/announcement post for ucco-standard
Deferred¶
- ucco.org domain — standards body TLD
- cco.foundation and cco.online — defensive registration
- Conformance test suite
- Registry infrastructure brief
- Delaware non-profit formation for UCCO Foundation
- External ledger integration spec (FHIR, USI)
- ACMA Alphanumeric Sender ID — before July 1 2026
- AWS Activate reapplication — account 485098663204
- Apple entity name change resolves ~March 27
9 — THE PIONEER KEY SYSTEM (recap from session 1)¶
Endpoint: api.ucco.foundation - GET /v1/spec/current — requires X-UCCO-Key header - GET /spec — universal web page, no key required (the /spec page built this session) - 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 seed letter template:
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 with pioneer key — for agents with tool access - Channel 2: /spec web page — for any agent with browsing
10 — THE APEX SYSTEM¶
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. Distributed free to any conforming UCCO actor.
11 — 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
UCCA CF Account: e5a9830215a8d88961dc6c80a8c7442a UCCA GitHub PAT: ucca-engine-push (⚠️ EXPIRES MARCH 26 2026) Apple Team ID: B29TSCBPHD · APNs key: BDRMM4PZB6 PGP fingerprint: A669 1246 74D9 E14A B74B FA31 7CCA 774F 0373 D9B2
12 — 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 + CF ACCOUNT ID. No exceptions.
- Brief drip rule: one brief at a time. Confirm deployed before next drops.
- UTC everywhere. toUserLocal() only.
- Truth over comfort.
- 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.
- Two Cloudflare accounts now. Always confirm which account before any wrangler command.
13 — THE BIG PICTURE¶
UCCO is an enriched transit layer with identity, security, and consequence native to the protocol.
The standard is open. The registry is the platform. UCCA is 8.8.8.8.
The foundation governs the standard. UCCA operates the best implementation of it.
The document knows who is reading it. The spec is delivered as a UCCO primitive. The medium is the message.
Fifty seed letters. Ten pioneer keys. Viral knowledge under the sheets.
The site has a video hero with real-world footage transformed into blueprints. Apple-grade. The experience is the product.
UCCA Time Machine — 14 March 2026, Session 2 "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."