Inspector

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.

This pool

Reading two things at once

Ctrl-click (Cmd-click on a Mac) a reference and what it points at opens beside what you are reading rather than replacing it — or Ctrl-Enter on a card you have tabbed to. The side pane is a second lens, generated from the object's own shape by the same path as the first; it is not a preview. It is read-only for now, and it closes when you switch pools, because a pane belongs to the pool it came from.

What was derived

…

Ask for something else

Put something in

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. This form is instrumentation, not the answer — task 0044 says how an object should come into existence, and it is not through four fields.

What Morph believes

Underneath

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.