The loop, running

An object store with an AI-generated presentation layer. Pick a pool: the generator reads its shape — how much media, how many roles, how values are distributed — and proposes a layout spec. The runtime compiles it and derives a presentation from what it contains. No app name appears anywhere in that path.

Context Cardinality View Viewport Palette Scheme

New object

Open an object to add a property

You pick a role, never a widget. The property lands on one object; the others never learn about it. The layout is regenerated from the new shape, so adding something can change what you are looking at.

…

The layout spec the generator proposed

The pool genome — what would be shared, after the abstraction gate

Every package here is the real one the test suite exercises — nothing is mocked, because a demo that mocks the interesting part proves nothing about whether the interesting part works. Colour is derived in OKLCH from the palette name and proved against WCAG contrast floors in packages/runtime/test/palette.test.ts; the runtime refuses a layout it cannot render legibly rather than shipping it slightly worse.