28 OCTOBER 2026 · BROWSER-NATIVE EDITION
From readable intent
to executable evidence
How a specification-led harness grew into a component system for governed software creation.
THE BOTTLENECK MOVED
Code generation made code abundant. Confidence stayed scarce.
A candidate can be coherent, tested, and still be wrong about the authority it was meant to implement.
THREE THINGS MUST REMAIN DIFFERENT
Invert the product: intent is durable; implementation is renewable.
INTENT
Readable behavior
and constraints
IMPLEMENTATION
Replaceable source
and native artifacts
EVIDENCE
Independent checks
and current receipts
COMPOSITION WITHOUT COPY-AND-PASTE
A Component DAG keeps authority factored—and still makes art.
Each node owns a readable boundary. Edges express composition, not copy-and-paste.
EVERY TRANSITION CAN REFUSE
The lifecycle is a chain of custody, not a single generate button.
A changed specification, Flavor, skill, route, dependency, toolchain, or artifact changes what must be proved.
THE 0.X LINE
Evolution I · make readable authority executable.
THE 1.X LINE
Evolution II · make evidence compose at production scale.
THE RECIPE IS INSPECTABLE
Exact identities turn explanation into an executable contract.
- Component revision
- selected Flavors
- pinned skills
- workflow + routing
- repository sources
RECIPE
acceptance · receipt
SIDE EFFECTS CHANGE RETRY POLICY
Failure is evidence, too—if ownership stays explicit.
MODEL OUTPUT
Useful proposal
No acceptance authority
FAILED ATTEMPT
Retain diagnostics
Preserve ownership uncertainty
TRUSTED RESOLUTION
Owned terminal evidence
or admitted fenced lease
Retry policy must follow side effects—not optimism.
ONE PORTABLE HTML FILE
Observability became a product surface, not a debug afterthought.
A provenance-bound authority graph with filters, focus, and source excerpts.
A general IDE, symbol index, or go-to-definition engine.
NO KPI DASHBOARDS WERE HARMED
Six labs teach composition by making increasingly questionable life choices.
math → physics → audio/music → 3D → video → composed component art
YES, IT HAS A PIPE ORGAN · NO, FINANCE DID NOT ASK FOR IT
The cathedral is the argument: rigor can wear better clothes.
Select a node and inspect the authority it owns.
Change one capability without rewriting the whole artifact.
Capture bounded video; keep audio opt-in.
CLAIMS FOLLOW EVIDENCE
Release posture is part of the feature—not a footnote.
An unchecked roadmap item is not a release claim. A catalog entry is not universal native qualification.
SERIOUS EVIDENCE · LESS SERIOUS DEMOS
Readable systems can be
rigorous, renewable—and fun.
Keep intent human-readable.
Keep implementation replaceable.
Make evidence earn the release.