start a build 
███████╗██╗   ██╗██████╗ ███████╗██████╗ ███╗   ██╗ ██████╗ ██╗   ██╗ █████╗ 
██╔════╝██║   ██║██╔══██╗██╔════╝██╔══██╗████╗  ██║██╔═══██╗██║   ██║██╔══██╗
███████╗██║   ██║██████╔╝█████╗  ██████╔╝██╔██╗ ██║██║   ██║██║   ██║███████║
╚════██║██║   ██║██╔═══╝ ██╔══╝  ██╔══██╗██║╚██╗██║██║   ██║╚██╗ ██╔╝██╔══██║
███████║╚██████╔╝██║     ███████╗██║  ██║██║ ╚████║╚██████╔╝ ╚████╔╝ ██║  ██║
╚══════╝ ╚═════╝ ╚═╝     ╚══════╝╚═╝  ╚═╝╚═╝  ╚═══╝ ╚═════╝   ╚═══╝  ╚═╝  ╚═╝
supernova@observatory ~/supernova.claudioandroyde.uk
$ ./render-about.sh --dial story
the story — the observatory who · how · why

One operator, a documented pipeline, and a printed honesty contract.

# this page answers who is behind Supernova and how the builds actually run — no fake team bios, no stock claims, no invented history

One person runs this — and that's the point. A small business's website shouldn't be a brochure that sits there; it should be what their customers' AI answers quote. So every build ships with Generative Engine Optimization (GEO) as standard, not as an upsell — and everything on this site, down to the receipts on the case-studies page, is built the same way yours would be.

who runs it — one humanthe operator

Supernova is run by one person, operating a pipeline that was built and refined across this project’s own register — chapters 06, 07 and 08 were dogfood builds of this same service, and this site is chapter 09.

There is no fabricated “team of experts” page and no stock-photo faces. You will speak to the same person who reads your brief, checks your mockup, and ships your build — and who replies to hello@supernova.dev within one business day.

public social profiles are intentionally not published yet — the reachable signal today is the email above. Honest slots, not empty promises.
what the name meanswhy “observatory”

An observatory watches the sky and reports what it sees with instruments, not opinions. Supernova watches the conversation — the questions customers ask Google, ChatGPT, Perplexity and Gemini — and points its instruments at the businesses that deserve to be in those answers.

The terminal look of this site is that metaphor made literal: a well-lit observatory that happens to be a terminal. Warm, calm, and precise — not a hacker den, and not a sales funnel wearing a costume.

the register — real prior buildsverified, not vibes
ch. 06  Terminal/CLI register — 8 pages · 37 schema blocks · QA log
ch. 07  byte-identical twin of 06 — the output is reproducible
ch. 08  css baseline · dsh/CC-executor run · dual-theme renders
ch. 09  this site — the flagship demonstration, you are reading it
caribbean-vibes  external client build · 7 pages · 15 schema · QA 87/100
receipts for every line above are on /case-studies, read from each workspace’s own files at build time.

01 how a build actually runs $ cat ./how.md

No black box, no “trust the process” hand-wave. Five stages, each with a human gate, documented in the same files the operator reads.

the five stageswhat you see at each gate
01 · observe

$ ./scan --ai-visibility

Listen to what engines ask, and what your site answers today. You see the diagnosis.

02 · design

$ design --unique

Type, color, layout drawn for you — never off-the-shelf. You approve the concept.

03 · build

$ build --geo-first

Static HTML + structured data + stack wiring. You review the mockup.

04 · verify

$ verify --cite

Every figure cited, QA logged, honesty printed. You read the QA report.

05 · launch

$ deploy --dual-theme

Days, not weeks. You keep everything — code, design system, strategy doc.

why there are human gatesthe anti-slop guarantee

Every build is reviewed by a human at concept, plan and mockup — before anything ships. The gates exist because the output of an automated pipeline is only as good as the taste applied to it, and taste is not a checkbox.

That is also why the QA records are public. The seven-bans quality gate, the visual checks at three viewports, the WCAG scan — when they fail, the failure goes on the record and gets fixed, as the case-studies page shows with real logs.

02 what the observatory believes $ cat ./ethos/

honestyprinted

No invented testimonials, no fabricated metrics, no fake urgency. Every figure on this site is either verified from a shipped build or a named source, or marked * until it is.

scaleowned

This is a lifestyle business with a deliberate ceiling — one operator, a handful of builds a month, each one treated like a flagship. The ceiling is the quality control.

prooffirst

This site is the flagship demonstration. If the claim is “marketing sites that humans AND AI engines can find,” the claim has to survive on its own surface first.

ownershipyours

You own the code, the design system, the strategy document, the domain and the analytics. No lock-in, no hostage file formats, no “contact us to leave”.

Every build ships dual-theme, schema.org and llms.txt. Pricing is printed, not quoted. Sources are cited, never borrowed. the honesty contract — how Supernova runs, stated once, kept on every page
the printed promiseswhat you can hold us to
  • Static HTML on the Cloudflare free tier — fast, secure, no server to babysit, no CMS lock-in.
  • Human-reviewed at concept, plan and mockup — nothing ships past you by surprise.
  • You own everything — code, design system, strategy document, domain, analytics.
  • Honest pricing, printed — $2,500 Launch · from $4,500 Build + GEO · optional retainer $250–750/mo, on /pricing.
  • No lock-in and no fake claims — no “guaranteed #1”, no invented testimonials, no stock-photo credibility.
  • Sources cited — every market figure carries a named, fetchable source or the * mark until it does.
start — open channela human replies
$./start-a-build.sh--planlaunch|build-geo
# mailto: hello@supernova.dev — a reply lands with the operator within one business day, not a drip campaign
launch $2,500 · build + GEO from $4,500
open pricing · dual-theme included · sources cited *