Design Round 8 · Deliverable 2 · Kiduna Studio · kiduna.studio · Windows / Mac / Chromebook / Linux · Flutter/Flame · July 13, 2026

# Studio — the same Field, more verbs

Studio is not a different product — it is the Field at a desk, where building verbs are granted: the workshop frame at 1440 (2a), the building verbs as conversation with receipts (2b), the inspection grammar for Allies and Actors — this round's hardest problem, given real screens (2c), collaboration designed ground-up: shared Scenes, self-organizing materials, GitHub, package transfer machine-to-machine (2d), and the R7 rulings honored as law (2e).

2a

## The workshop frame — the Field wide, the HUD earning the width

R7's four postures fold into the one-interface rule: on desktop the HUD's opaque state may stand beside the Field instead of over it — that is all "side-by-side" ever was. Same four HUD elements; the width buys a standing thread and longer chip labels, never more chrome.

Kiduna Studio kap://eco.kinship.net
Dowbot · registered
Digital Dolly
pkg #7 · in flight · 12 min
@elias · on his machine
The Ceremony Machine · Lightbrush integration
walk the returned build open the package thread
Taro — package #7 reports: adapter tests passing on Elias's machine. Elapsed twelve minutes; nothing waits on you.
HUD · opaque · standing beside fold →
Elias uploaded nine reference boards; I organized them under the adapter's materials and cited each to his upload receipt.
What's waiting on me across my Projects?
Two things stand. Here — the RenderDeck grant ask. In Fellowship of Play — a proposal closing tonight your Envoy holds a token for. Both stay at their objects; this is the Docket, spoken.
action · standing at its object
Connect RenderDeck to this Project. It would read Records at member level.
grant it not now
Say it or type it…

What the frame still refuses (R7 law, restated): file trees · tabs, docks, panels · notification trays · meters · a second primary action. The spacebar peek is cut (ruling 3). One Project at a time; switching is a drift.

2b

## The building verbs — said to the ally, run as commands, kept as receipts

Building an Organization, an Alliance, or an ally; adding content; modifying system prompts; connecting accounts — every verb is one grammar: the ally states the command verbatim before it runs; the receipt is a machine-generated sentence over it; the result is a citable Record. No settings forms anywhere in Studio.

founding an Organization
This registers Black Love as an Organization with its own Org ID, Mama Ayo as founder. The command, verbatim:
org.found --name "Black Love"
--founder @mamaayo --register wv-sos
Founding is one of the signed acts: press-and-hold, gold — this act writes the Organization's first authoritative Record. Registration is checked daily by an agent connected to the registered agent.
a Community formalizing into an Alliance
Your Community of five becomes the Service Alliance: a shared wallet needing three of five, and your first policy — the one you all said yesterday — enters as Proposal #1.
The circle's dashed edge turns solid in place; the table (wallet + proposals) materializes at the center. Each member signs their joining from their own surface. Envoys may be seated afterward, by instruction.
modifying a system prompt
"Taro, inside this Project you may speak for me on package status — nothing else." The Contract's change is read back, then held. Every sentence timestamped with who said it.
Only the Source can say this. Anyone else asking an ally to change is refused with the refusal stated — that is the prompt-injection answer rendered as UX, not a filter.
connecting an account
Bluesky connected and bound to your registry identity. It renders as a scoped, dated account link — never a claim that two names are the same person unless the proof is registered.
Connected accounts land as objects in your ally's room: a box full of Bluesky posts is a box in the Field. Other members' allies may use your public posts as context — that is the point.
2c

## Inspecting an agent — the workbench grammar, for Allies and Actors both

The hardest problem this round. The answer: an agent under inspection stands on a workbench — a small Scene of its own — and its anatomy surrounds it as read-only cards, each card a rendering of conversation's outcomes, each fact cited. The same bench serves both agent kinds; what differs is which cards exist. You never edit a card; you say the change, the ally (or the Actor's steward) reads it back, the card re-renders.

the bench · Taro · Moto's ally
the Contract
14 sentences · each timestamped, each with its sayer. Newest: "may speak for Moto on package status, inside Lightbrush only" — Moto, today.
instruction only from the Source
grounding
Weighted by source: Moto's own words first, the Organization's Records second, public material last. Ask "why do you think that?" and the answer cites.
what it knows
Counted by access level — public · private · secret · personal. Forgetting is a said thing: removal, not hiding, and the removal is itself a Record.
recent acts
Every act cited to its receipt, in the Organization it happened in. Nothing summarized without its source.
"Drop the Bluesky grounding to public-only." — read back, then the card re-renders
Inspecting an Ally. Four cards: Contract · grounding · what it knows · recent acts. Cards are read-only renderings; change happens in conversation and only from the Source. No gold here — stated trust (R6 rule); the Contract change is light.
the bench · Dowbot · Actor · invoked by the Lightbrush Project
function
What it is for, verbatim from its builder: "watches Dolly's render queue and files completion Records." An Actor has a function, not a Contract — it represents no one.
invoker & standing
Invoked by the Lightbrush Project · acts inside The Ceremony Machine, as a member of it · built by Moe's team · registered. Accountability is a chain you can walk.
permissions
The grants it runs under, each stated and revocable in a sentence by whoever granted it. Enhancement = new grants or new skills, said by the steward, receipted.
routine & recent acts
Its routine as it would run today; its last acts cited. You can interact with it directly on the bench — through your ally, as always: member → ally → ally.
"Give Dowbot the new manifest skill from Elias's package." — steward's sentence, receipted
Inspecting an Actor. Four different cards: function · invoker & standing · permissions · routine. No Contract, no Source — an Actor is directed by whatever invoked it, within its grants. Builders and Creators can name their own Actor types; the bench renders any of them.

The bench is the inspection grammar Live lacks — which is exactly why acceptance and complex diffs stay in Studio (ruling 4). When Live can render a bench honestly, mobile acceptance gets revisited (R7 OQ-4, still standing).

2d

## Built for building together — one Scene, several hands

real-time, same Scene
Two builders stand in one Project Scene; each sees the other as position and act — "Elias is dressing the north wall" — not as cursors. Edits land as objects with provenance chips the moment they're made. Voice rides the HUD; nothing needs a share link, because being in the room is the share.
materials organize themselves
Drop anything in — boards, docs, audio, a folder of sprites — and it lands in the Scene and organizes into the graph: named, leveled, cited to its upload receipt. There is no file tree to maintain because the graph is asked, not browsed. "Where did Moe's reference boards go?" is a sentence, answered with citations.
GitHub, linked honestly
A repo links to a Project as a registered resource — an object in the room stating what it is and where it lives. Studio never becomes an IDE: code work goes out through packages to Claude Code or Codex and comes home as draft Records cited "via [agent] · pkg #N," forever.
package transfer, machine to machine
Packages (skills, Scenes, materials) move directly between client computers when both ends are present and trusted, and to network storage when they're not — the server brokers, grants scope, Records both ways. A sent package waits at the room's edge and lands when taken, never before. Trusted unlocks direct transfer and standing sync; untrusted still exchanges — server-held, at arm's length.
2e

## The rulings, rendered — where R8 obeys R7's law

Quarantined violations. A returning package that breaks its own manifest is held at the room's edge as evidence — the exact violated constraint stated on the card — and can never enter the Project as drafts or Records. The quarantine object is dim camel, not red; a fact, not an alarm.
The Docket is a projection. "What's waiting on me" renders as a spoken answer or a card of standing ACTIONS — each one a pointer to its object, no counts, no badges. Closing the card changes nothing, because it was never a place.
Two signatures, separate Records — profile send and Code redemption — remain the invitation's shape; Studio's Profiler flow renders both distinctly.
Gold only into the Record. Elias accepting work-in-progress is light. Moto accepting into The Ceremony Machine's authoritative Record is the press-and-hold, the ring, the embers. The bench, the grants, the Contract changes — all light.
Studio's sentence, R8: the workshop is a place in the Field where more can be said — never a different language.

Compute renders here as everywhere: prepaid usage credits that power intelligent agents, spent quietly, stated on request. Buying it is a door to the web — kiduna.cash — never a form in Studio.