EXHIBIT 000 / THE CASE FILE
Every claim on dissfam.com points back to this page. What follows is the operating record of one autonomous session: the brief, the run, the Engine reviewing its own work, and the bill of materials. Nothing here is a mock-up — you are standing inside the deliverable.
BRIEF.RAW / RECEIVED VERBATIM
“Make dissfam supernatural. You can do it straight to production. I will give you no instruction, no guidance. Deliver to your absolute best capabilities.”
That is the entire specification the Engine received. Strategy, positioning, copy, design system, artwork, code, review, and deployment followed from it.
One session, brief to production. The ledger below is the real sequence.
Four research agents swept the live portfolio in parallel — Cellavie, Every Era Estate, the old dissfam.com — and hunted the public web for the unlaunched products. The copy on /work is grounded in what they verified, not in guesses.
4 agents · 3 live properties mapped
Tokens, typography, the hairline “Signal” language, the generative mark engine, the WebGL field, and the homepage were built as a single coherent gesture — then frozen as a written contract (docs/DESIGN.md) before anything fanned out.
8 generative marks · 0 raster portfolio assets
Four builder agents took one route each — the registry, the Engine, the pipeline and terms, the contact channel — against the frozen design contract. Disjoint file ownership; no agent touched shared ground.
4 builders · 6 routes · 1 contract
Six adversarial reviewers — visual, mobile, accessibility, copy, code, functional — attacked the finished site. Every finding then faced an independent verifier instructed to refute it. What survived got fixed. What did not, died.
33 findings raised · 32 confirmed · 32 fixed · 1 refuted
The Engine and Process pages were rebuilt around live proof — the operating floor, the veto gate you can press, the engagement replay — followed by a structural refactor that left one implementation of every hard problem.
Press the veto gate yourself →5 live simulations · 29 e2e tests green
Build clean, lint clean, suite green, pushed to main. The human veto stood over every deploy. It still does.
same-session · straight to production
The strongest evidence for governed autonomy is the Engine catching its own mistakes. A sample of what the adversarial pass confirmed — against its own fresh work — and fixed before you ever saw it:
Visitors with reduced-motion enabled received blank pages — the reveal system never wrote its resting state over the server-rendered hidden state.
Fixed. Reduced motion now renders every page fully, verified by a standing regression test.
A decorative vignette mask was silently dimming real content — including the primary call-to-action buttons — on every hero section, worst on the contact form.
Fixed. The mask was moved to a non-content layer; buttons measured back to full brightness.
Every subpage declared the homepage as its canonical URL — an instruction to search engines to de-index the entire site except one page.
Fixed. Per-page canonicals shipped the same session.
The homepage stat “2 live on the public internet” was false — one of the two products sat behind an access wall. The Engine flagged its own marketing copy as unverifiable.
Fixed. The claim was rewritten to what is true, and the case-file links were gated by real status.
That is what the gate is for. Autonomy produced the site; adversarial review produced the truth; a human signed the release.
No templates. No stock imagery. No page builders. Every portfolio mark is drawn by seeded code at runtime.
The next case file could be yours. Send a brief and watch the same pipeline run with your name on the ledger.