Skip to content

UCCO Ops — Membership & Outreach Stub Pages Brief

SURFACE: ops.ucco.foundation (ucco-ops repo)
CF ACCOUNT: aed3398a4e698767328cc3a9e698721d (FOUNDATION account)
DO NOT TOUCH: ucco-site, ucco-api, ucca-engine, ucca-ops, or any UCCA surface

→ TIM

This is a quick one. Alex updates the five Membership section stub pages with the descriptions we designed in Session 5. No infrastructure, no APIs, no Broadcast system — just the stub page content so the ops panel accurately describes what each surface will become. The architecture spec (UCCO-Membership-Outreach-Architecture-v1.md) is the reference doc — this brief just says "put these words on those pages."

→ ALEX

What this is

Update the five existing stub pages under the MEMBERSHIP section with proper descriptions. These pages already exist from the Ops Cosmetics Brief — they just have the generic "This surface is planned" template. Replace that with the specific descriptions below.

What this is NOT

Do NOT build any backend infrastructure, API integrations, D1 tables, or signing systems. Stub content only.

Page updates

1. Membership Overview (/membership/overview or wherever the current stub lives)

Replace the generic stub with:

Membership Overview

Founding member registry, membership tiers, donation pipeline, contributor activity.

When live, this page will show:
• Total founding members and membership tier breakdown
• Pending invitations and seed letters in flight
• Donation summary (wired to Mercury API when bank account is live)
• Recent membership activity and contributor registry

Status: planned — blocked on foundation incorporation and Mercury bank account

2. Outreach (/membership/outreach)

Outreach

Seed letter pipeline — draft, send, track, follow up.

When live, this page will show:
• Seed letter templates with per-recipient customisation
• Send status tracking (drafted → sent → delivered → opened → responded)
• Follow-up scheduling and reminders
• Response tracking (interested / declined / no response / meeting scheduled)
• Pipeline view: letters out, responses received, conversion rate

This is the recruitment funnel: Pioneer → Board → Membership.

Status: planned — activates when seed letters are ready to send

3. Broadcast (/membership/broadcast)

Broadcast

Compose once, authorize, sign, hash, distribute everywhere.

The broadcast model: you write a post. A board member or president authorizes it — 
that's a signature event. The system hashes the content, records the authorization, 
then publishes to every configured channel simultaneously. Each distribution is logged.

Workflow: COMPOSE → AUTHORIZE → SIGN → HASH → DISTRIBUTE → VERIFY

The result is an immutable communications ledger. Every public statement is a signed 
envelope with a chain position and public verification URL.

"Never 'do you remember when you said...' 
 Always 'here is exactly what we said, signed by whom, on this date.'"

Channels: YouTube, TikTok, Reddit, GitHub Discussions, X, LinkedIn

Status: planned — dedicated build brief required, multi-session engineering

4. Media Library (/membership/media-library)

Media Library

Every public statement, video, press release, blog post — indexed, hashed, searchable.

When live, this page will show:
• Searchable archive of all foundation public communications
• Each item content-hashed (SHA-256), timestamped, and attributed
• Linked to Broadcast records where applicable
• Filterable by type (video, text, press release, blog, social post)
• Filterable by date, author, channel

The foundation's complete public record from day one.

Status: planned — follows Broadcast system build

5. Channels (/membership/channels)

Channels

Distribution infrastructure — connection status and configuration per platform.

┌─────────────┬──────────────┬─────────────────┐
│ Channel     │ Status       │ Last Post       │
├─────────────┼──────────────┼─────────────────┤
│ YouTube     │ not connected│ —               │
│ TikTok      │ not connected│ —               │
│ Reddit      │ not connected│ —               │
│ GitHub      │ not connected│ —               │
│ LinkedIn    │ not connected│ —               │
│ X           │ not connected│ —               │
└─────────────┴──────────────┴─────────────────┘

When live, this page will manage:
• OAuth connection status per platform
• API key and token expiry tracking
• Rate limit monitoring
• Quick test button to verify connections
• Posting history per channel

Status: planned — follows Broadcast system build

Styling notes

  • Use the same stub page template/component from the cosmetics brief
  • The descriptions should render as body text, not code blocks (the code blocks above are just for this brief — render them as proper paragraphs and lists)
  • The Channels table on the Channels page can render as an actual HTML table with the "not connected" status in grey
  • Keep the planned badge on each page
  • If GUIDED mode is implemented from the cosmetics brief, these descriptions double as the GUIDED mode help content for these pages

Deployment checklist

  1. Update all five stub pages
  2. Verify each page loads correctly in both light and blueprint modes
  3. Confirm CF Access still gates the surface
  4. Commit and push to ucco-ops repo

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