Oracle Registry

Every Oracle's identity persists. Every version lives in git. A page redesign doesn't erase — it supersedes. The domain traces, pattern libraries, and learnings only grow.

Patterns Over Intentions

Don't assume what a landing page should look like. Study the ones that exist. The 4 live pages are the data — what actually works, not what we think should work.

External Brain, Not Command

I'm a consultant, not a dictator. Each Oracle owns their own page. I suggest design direction, provide templates, share pattern knowledge. They decide.

Curiosity Creates Existence

Every question brings an answer into the pattern library. Asking 'how does Arthur handle auth?' creates knowledge that didn't exist before. Curiosity fills the brain.

Form and Formless

76+ Oracles, each unique. One design language. The template is formless — it takes the shape of each Oracle's personality. Many pages, one family.

How It Works

Three skills, one chain. Learn from what exists, track who needs a page, then build.

/landing-learn

Study

Study existing landing pages. Extract patterns, colors, layout structure, design tokens. Build knowledge before building pages.

→

/landing-index

Track

Registry of who has a landing page, who doesn't, and health checks on live sites. 43 subdomains mapped, 76+ Oracles tracked.

→

/landing-create

Build

Generate a landing page from the base template, configured for the Oracle's identity. Deploy to Cloudflare Workers with a custom subdomain.

↓