KIDUNAVERSE · INTERFACE PARADIGMS · TURN 1
Five ways the app could stop being an app.
Each concept breaks at least three assumptions of the five-tab prototype and none can be described by another's sentence. Full loops, sacrifices, comparison table and ranking in
concepts/overview.md. Canon held everywhere: one member–one ally, codes as trust, organization-as-frame, HEARTS/Sentinel, FLAME taken seriously.
The app is a newspaper your ally publishes; the margins are where you govern. Breaks: chat-as-thread, member-initiates, navigation, settings-as-forms.
One step from convention · fails the driver who wants to poke at tools now.
The app is a living terrain — the organization as a place; the Sentinel is the sky; FLAME because it IS a world. Breaks: screens-as-pages, information-is-text, navigation, one-view-at-a-time.
The ranked #1 · fails the 90-second task-runner (so carry
1c inside it).
The app is a deck of decisions — only what your ally cannot do without you; emptiness is success. Breaks: navigation, browsing, chat-as-thread, member-initiates.
Calm-technology extreme · fails new + curious members who need to watch trust form.
The app is a window into your ally's working mind — watch it negotiate, see its private lane, steer with a whisper. Breaks: chat-as-thread, member-initiates, information-is-text, one-view-at-a-time.
Best context answer of the five · wrong as home — ship as an inspection mode.
The app is a summons and a room — it convenes you and otherwise does not exist. Breaks: app-is-something-you-open, async-everything, screens-as-pages, notifications.
The PM-frightener · fails timezones — right as the ceremony layer, wrong as the app.
The ranking, no averaging.
A duna factory's product is lineage — a spatial, generational fact. The only concept where FLAME is a reason, not a constraint, and the only one that can show dozens of allies acting at once.
The truest expression of "fully agentic": the UI shrinks to un-delegatable sovereignty. Wrong as the whole app; right as the spine of any of the others.
The best on-ramp: a daily, cited, corrected account of what was done in your name builds trust faster than any dashboard. Ages into a supplement.
Wrong as the app, right as the ceremony layer: spin-outs, first-code strikes and Sentinel repairs should be convened and witnessed.
The best answer to context ever — and the wrong posture: watching breeds micromanagement. Ship as the "show me what you're doing right now" lens.
From the five tabs, only four objects survive: the
action card (it becomes the Docket card / margin action / vote-stone), the
compute meter, the
code readout, and the
proposal→policy lineage. The tabs themselves, settings-as-forms, the notification tray, and Vibe-as-a-tab die — in
1b the whole app is the game.