Skip to content

UCCO Press Office Surface Brief

SURFACE: pr.ucco.foundation (NEW — needs Worker + DNS record)
OPS STUB: ops.ucco.foundation — new "Press Office" page under MEMBERSHIP section
CF ACCOUNT: aed3398a4e698767328cc3a9e698721d (FOUNDATION account)
DO NOT TOUCH: ucco-site, ucco-api, ucca-engine, ucca-ops, or any UCCA surface

→ TIM

This builds the foundation's public press office at pr.ucco.foundation and wires it into ops. Two parts:

  1. Public surface — the URL a journalist hits. Press releases, founder bio, logo pack, stock photos, fact sheet, pre-written interviews, media contact form. Static site with asset downloads. A journalist should be able to write a story about UCCO without ever emailing you.

  2. Ops integration — a Press Office page in the Membership section of ops.ucco.foundation. Inbound media request tracker, asset library management, media contact database. This is where you manage the press office from the inside.

The public surface is deployable quickly — it's a well-designed static site with file downloads from R2. The ops page is a stub that gets richer as we build out the Broadcast and Channels infrastructure.

This needs to exist before the seed letters drop. First impressions are permanent with press.


→ ALEX


Part 1 — Infrastructure Setup

New Worker

Create a new Cloudflare Worker: ucco-pr

  • Route: pr.ucco.foundation/*
  • Zone: ucco.foundation (already in foundation CF account)
  • DNS: CNAME or A record for pr subdomain, proxied through Cloudflare
  • SSL: Full (Strict) — inherited from zone settings

Stack

Static site served from a Cloudflare Worker. HTML/CSS/JS — no framework needed for this surface. Assets (logos, photos, documents) served from R2.

R2 Bucket

Create: ucco-press-assets

Directory structure:

/logos/
  ucco-logo-colour.svg
  ucco-logo-colour.png
  ucco-logo-colour.eps
  ucco-logo-white.svg
  ucco-logo-white.png
  ucco-logo-mono.svg
  ucco-logo-mono.png
  ucco-icon-colour.svg
  ucco-icon-colour.png
/photos/
  (founder headshots, product screenshots — added later)
/documents/
  ucco-fact-sheet.pdf
  ucco-foundation-overview.pdf
/releases/
  (press releases as markdown or HTML — added later)

Note: Tim will need to provide the actual logo files and headshots. For now, create the bucket and directory structure with placeholder README files in each directory explaining what goes there.

CF Access

This surface is PUBLIC — no CF Access. The whole point is journalists can access it without authentication.


Part 2 — Public Surface Design

Design language

This is a public-facing foundation surface. It must look professional, serious, and institutional — not startup, not tech demo.

  • Clean white background
  • Typography: system font stack, generous whitespace
  • Colour: Prussian blue #01497C for headings and navigation, #012A4A for body text, #10B981 green for CTAs and download buttons only
  • No dark mode on this surface — it's a press office, not a dev tool
  • Mobile responsive (journalists work from phones too)

Page structure

Single-page layout with anchor navigation. One URL, everything accessible by scrolling or jumping to sections.

pr.ucco.foundation
├── Header (UCCO Foundation logo + "Press Office" + nav anchors)
├── #latest — Latest News
├── #about — About UCCO Foundation  
├── #leadership — Leadership
├── #assets — Media Assets & Logo Pack
├── #factsheet — Fact Sheet
├── #articles — Available Articles & Interviews
├── #contact — Media Contact
└── Footer

Section content

Header - UCCO Foundation logo (left) - "Press Office" title - Anchor nav: Latest | About | Leadership | Assets | Articles | Contact - Clean horizontal rule under header

#latest — Latest News

Latest News

No press releases yet. Subscribe to be notified of future announcements.

[Email input] [Subscribe]

Email subscription stores to D1 (press contacts table — separate from pioneer or membership). When press releases exist, this section shows them reverse-chronological with date, headline, one-line summary, and "Read more" expanding to full text.

#about — About UCCO Foundation

About UCCO Foundation

The UCCO Foundation governs the Universal Capability Chain Object (UCCO) — 
an open standard for cryptographic capability verification.

The internet solved data transport (TCP/IP), identity (OAuth), and credentials 
(W3C Verifiable Credentials). UCCO completes the stack: a protocol layer that 
proves what someone can actually do, not just who they are or what certificates 
they hold.

The standard is open. The foundation is independent. The specification is 
currently in Draft for Public Comment (v1.1 Rev2) and has been submitted for 
adoption consideration to ISO TC 307, NIST NCCoE, and the W3C Verifiable 
Credentials Working Group.

Founded: 2026
Jurisdiction: Kentucky, United States (nonprofit corporation)
Governing document: UCCO Standard Specification v1.1 Rev2
Website: ucco.foundation
Standard repository: github.com/ucco-foundation/ucco-standard

#leadership — Leadership

Leadership

Tim Rignold — President & Chair
Background in datacenter/network infrastructure, VET sector compliance, 
and standards architecture. Based in Brisbane, Australia.
[High-res headshot download]

Jimmy Kuo — Treasurer & Director  
International business development (Alibaba, Temu, Informa/UBM). 
Trilingual (English/Mandarin/Taiwanese). Based in New York City.
[High-res headshot download]

Note: Add board members as they're confirmed. Each entry: name, title, one-line bio, headshot download link.

#assets — Media Assets & Logo Pack

Media Assets

All assets are provided royalty-free for editorial and informational use. 
No permission required for press coverage. For commercial licensing, 
contact press@ucco.foundation.

Logo Pack
├── Full logo — colour (SVG · PNG · EPS)
├── Full logo — white on transparent (SVG · PNG)  
├── Full logo — monochrome (SVG · PNG)
├── Icon only — colour (SVG · PNG)
├── Icon only — white on transparent (SVG · PNG)
└── [Download all as ZIP]

Usage guidelines:
• Minimum clear space: height of the "U" in UCCO on all sides
• Do not stretch, rotate, recolour, or add effects
• Do not place the colour logo on busy backgrounds — use white or mono variant
• The correct name is "UCCO Foundation" — not "UCCO", not "Universal Capability 
  Chain Object Foundation"

Screenshots & Photos
(Coming soon — product screenshots and event photography will be added here)

Brand Colours
• Prussian Blue: #01497C (primary)
• Deep Blue: #012A4A (secondary) 
• Green: #10B981 (accent)
• Cream: #F5F0E8 (light background)

Each asset row has individual download links (SVG, PNG, EPS where applicable). All served from the R2 bucket. The ZIP download packages everything.

#factsheet — Fact Sheet

Fact Sheet

Download the UCCO Foundation fact sheet (PDF) for a one-page overview 
suitable for print or digital distribution.

[Download PDF]

Quick facts:
• Name: UCCO Foundation, Inc.
• Type: Nonprofit corporation (Kentucky, USA)
• Purpose: Govern the UCCO open standard for capability verification
• Standard: UCCO Specification v1.1 Rev2 — Draft for Public Comment
• Submissions: ISO TC 307, NIST NCCoE, W3C VC Working Group
• Repository: github.com/ucco-foundation/ucco-standard
• License: W3C Software and Document License (specification)
• Pioneer Programme: 11 cryptographic keys issued
• Founded: 2026

#articles — Available Articles & Interviews

Available Articles & Interviews

The following content is available royalty-free for editorial use. 
No permission required — publish as-is or adapt for your audience. 
Attribution to UCCO Foundation appreciated but not required.

Pre-written interviews and contributed articles will be published here 
as they become available.

If you would like to arrange an original interview with Tim Rignold, 
please use the contact form below.

When articles exist, each entry shows: title, type (Q&A / op-ed / contributed article), target audience, word count, date, download link (markdown + formatted PDF).

#contact — Media Contact

Media Contact

For press inquiries, interview requests, or embargo access:

press@ucco.foundation

Or use the form below and we'll respond within 24 hours.

[Name]
[Email]  
[Outlet / Publication]
[Deadline (if applicable)]
[What are you working on?]

[Submit]

Form submits to D1 (media_requests table) and sends email notification to admin@ucco.foundation (via the existing email infrastructure). Include a confirmation message: "Thank you. We'll respond within 24 hours. For urgent requests, email press@ucco.foundation directly."

Footer

UCCO Foundation, Inc. · Kentucky, USA
ucco.foundation · github.com/ucco-foundation
press@ucco.foundation

© 2026 UCCO Foundation. Press materials provided royalty-free for editorial use.


Part 3 — Email Setup

For now: manual alias only if needed

Email infrastructure migration is planned but deferred (see UCCO-Email-Infrastructure-Roadmap-v1.md). The foundation email currently lives on Google Workspace via ucca.edu.au.

Do NOT set up Cloudflare Email Routing. MX records stay pointing to Google.

The contact form on the press page references press@ucco.foundation. Two options:

  1. If Tim has created the alias in Google Admin: form submissions email to press@ucco.foundation (which delivers to admin's Gmail inbox). Use this address in the form and confirmation text.
  2. If no alias exists yet: form submissions go to D1 only (media_requests table) with no email notification. The ops Press Office page surfaces inbound requests. Add a note on the contact page: "We'll respond within 24 hours" — Tim checks ops, not email.

Option 2 is the safer default. It means the contact form works without any email config. Tim monitors inbound requests through ops. Email notification can be wired later when aliases exist.

For the page text, still display press@ucco.foundation as the contact address — Tim will create the alias manually in Google Admin when the surface goes live. Until then, the form is the primary inbound channel.


Part 4 — D1 Tables

Add to the foundation's pioneer-db (or create a new press-db if cleaner — Tim to decide):

media_requests

CREATE TABLE media_requests (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  name TEXT NOT NULL,
  email TEXT NOT NULL,
  outlet TEXT,
  deadline TEXT,
  message TEXT,
  status TEXT DEFAULT 'new',  -- new / responded / archived
  responded_at TEXT,
  notes TEXT,
  created_at TEXT DEFAULT (datetime('now')),
  updated_at TEXT DEFAULT (datetime('now'))
);

press_subscribers

CREATE TABLE press_subscribers (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  email TEXT NOT NULL UNIQUE,
  subscribed_at TEXT DEFAULT (datetime('now')),
  unsubscribed_at TEXT
);

Part 5 — Ops Integration

New page in ops.ucco.foundation

Add "Press Office" as a new page under the MEMBERSHIP section in the sidebar.

Position it after "Channels":

◆ MEMBERSHIP
├── Overview
├── Outreach
├── Broadcast
├── Media Library
├── Channels
└── Press Office    ← NEW

Press Office ops page content (stub for now)

Press Office
pr.ucco.foundation — public press surface

Status: [live badge when deployed]

Surface: pr.ucco.foundation
Assets: R2 ucco-press-assets bucket  
Contact: press@ucco.foundation

Inbound Requests
┌────────┬──────────┬────────────┬──────────┬────────┐
│ Date   │ Name     │ Outlet     │ Deadline │ Status │
├────────┼──────────┼────────────┼──────────┼────────┤
│ (empty — no requests yet)                          │
└────────┴──────────┴────────────┴──────────┴────────┘

Press Subscribers: 0
Assets uploaded: 0 / logos, 0 / photos, 0 / documents

When fully built, this page will show:
• Inbound media request tracker with response status
• Press subscriber list management  
• Asset library with upload/tag/version control
• Media contact database (journalists, outlets, beats)
• Press release drafting and approval workflow
• Embargo tracker
• Download analytics (which assets, how often, by whom)

Wire the inbound requests table to the media_requests D1 table when the data exists. For now, the stub is enough.


Part 6 — Deployment Checklist

  1. Create R2 bucket ucco-press-assets with directory structure
  2. Create Worker ucco-pr with route pr.ucco.foundation/*
  3. Add DNS record for pr subdomain on ucco.foundation zone
  4. Deploy the public surface HTML
  5. Set up Cloudflare Email Routing for press@ucco.foundation
  6. Create D1 tables (media_requests, press_subscribers)
  7. Wire the contact form to D1 + email notification
  8. Wire the subscribe form to D1
  9. Add Press Office page to ops.ucco.foundation sidebar
  10. Verify: public access works (no CF Access), form submission works, email routing works
  11. Commit ucco-pr to a new repo on ucco-foundation GitHub org (or add to ucco-ops if preferred)

Assets Tim needs to provide

Before this surface is complete, Tim needs to supply: - [ ] UCCO Foundation logo files (SVG source, PNG exports, EPS) - [ ] Logo variants (colour, white, mono, icon-only) - [ ] Founder headshots (Tim, Jimmy — high-res, professional) - [ ] Foundation fact sheet content (for PDF generation) - [ ] Brand usage guidelines (if more detailed than what's in the brief)

The surface can deploy with placeholder text ("Logo files coming soon") and be updated as assets arrive. Don't block deployment on assets.


Brief: UCCO-Press-Office-Brief-v1 Author: Pace (Claude, Anthropic) Date: 15 March 2026, Session 7 For: Alex (Claude Code execution)