Generation became free.
coherence didn't.
When the cost of generating an artefact collapses to zero, the bottleneck moves rather than disappears. Nodes grow linearly; edges grow quadratically. Generative tools solved the cost of the node and left the cost of the edge untouched. These nine characteristics are all expressions of a single position: owning the edges.
Nine ways of owning the edges
Each one answers the same question: what happens to an experience after it has been generated.
Deterministic rendering
Generation is stochastic by construction: every regeneration is a fresh draw. Ekitai renders each surface from a referenced source, so a change is applied rather than re-drawn. The cost of change stays flat as surfaces multiply.
Three orthogonal axes
Identity, structure and content are decided once per axis, not once per artefact. Forty touchpoints don't produce forty identity decisions — they produce one, applied forty times.
The declared touchpoint
A touchpoint is a declared object: manifest, sections, atoms, capabilities. Because it's declared, it can be queried, diffed and governed — not just viewed.
Native instrumentation
Surfaces are born instrumented. Analytics, consent and events aren't wired by hand on surface thirty-one, so volume produces data instead of noise.
Experimentation
A variant is an alternative value on a declared property, not a fork of the project. Opening a test costs almost nothing — and so does closing one.
Compliance by construction
Accessibility, SEO and consent are emitted with the surface rather than audited afterwards. WCAG 2.1 AA and GDPR become outputs, not projects.
Measured coherence
Divergence from the source is declared as an override, so it shows up in the control room instead of accumulating as silent drift.
The attractor model
External surfaces gain capability at each level of ekitai.js integration — visibility, identity, control, continuity. The native platform becomes the obvious next step rather than a migration to be sold.
Exportable by design
The stack is Next.js, Strapi and PostgreSQL on Vercel: standard, readable, yours. No proprietary format means no hostage situation.
Evidence before announcement.
What isn't verified stays on the roadmap.
Points 1, 2, 3, 4, 7 and 9 are demonstrable today. Point 5 still needs us to specify what the platform genuinely supports in multivariate terms versus simple A/B, because the word carries a precise statistical meaning. On point 6, accessibility and SEO are solid; the GEO portion needs checking line by line against what the renderer emits right now.