# THE MAKING SURFACE
**Kidunaverse Design Round 2 · the shallow end of making · July 7, 2026**

The Kidunaverse builds from the inside, like a MOO: members and allies spin out pages, bots, games, experiments — and above all agents — by talking. The Studio (deep end) ships Aug 10; this is everyday making, and it lives entirely inside the existing surface. **There is no Create tab, no builder UI, no form.** Making is a conversation that ends in a signature.

---

## 1. The birth pattern — three beats

Every made thing is born the same way, whatever it is:

**Beat 1 — intent.** The member says what they want, anywhere the ally has ears: *"We need a sign-up page for the solstice event, and something that answers questions in the Telegram group."* No syntax, no wizard.

**Beat 2 — the shape.** The ally answers with a **shape card** in the Thread: the thing restated as one object — its *name*, *what it does* (2–3 lines), *where it will live* (the event page URL, the Telegram group), *whose it is* (the realm it's grounded in, whose token it spends), and *its code policy* (who may use it, what it may never do). The shape card is conversationally editable — "make the bot only answer logistics" edits the card in place. This card is the entire configuration surface.

**Beat 3 — the strike.** Making something that others will inhabit is extending trust, so **birth is a code act: press-and-hold.** The strike is the moment the thing exists — the Registrar does the paperwork invisibly; the ally masks latency with a sentence, never a spinner. One ember moment. Agents get one extra line in the shape card — a **charter sentence** the new agent is bound to, quoted back the way a Contract is (*"Watches the tide charts; speaks only when the river crosses four feet."*).

Three exchanges, and it exists, has a code, and others can find it.

## 2. What a made thing IS

One object, graph-real, whatever its species (page, bot, agent, game, presence):

- a **name** and a **charter sentence**
- a **Kinship Code** at its heart — its identity, scope, and trust boundary; verifiable by anyone, revocable by its maker (revocation is a Docket card)
- a **maker line** — who struck it, in which realm, always visible ("struck by Teo · Fellowship of Play · June solstice")
- an **account-ability**: what it does streams into its maker's Account like any worker's doings, and it is inspectable in the Vigil like anything else the ally holds

## 3. Where made things live

**Nowhere central — everywhere real.** No gallery, no app store, no "Discover" (a browsable shelf of made things is a feed wearing a costume).

- **In the world it was made for:** the solstice page is on the web; the bot is in the Telegram group; the tide-watcher speaks in the river crew's alliance. Made things live at their point of use.
- **In the Thread, when consequential:** you *encounter* made things through claims — "Teo built a tide-watcher for the river crew; it's been right twice this week. Want it watching your stretch?" The Ledgerkeeper treats births and adoptions as events like any other; relevance, not recency, brings them to you.
- **By asking:** "what's been made around the Fellowship lately?" is a question the ally answers, cited, like anything else. The registry is asked, not browsed.
- **Out on the agentic internet:** every made thing carries its code, so trust travels with it — a stranger hitting the solstice page can verify what it is, whose it is, and what it may do; the plugin and embedded codes make the page itself a door back into the fabric.

## 4. Inhabiting — the other side

Encountering a made thing, a member can: **use it** (its code's public scope), **adopt it** (its maker's code policy decides — open adoption is instant; gated adoption becomes a card on the *maker's* deck, because extending trust is theirs), or **inspect it** (any made thing opens in the Vigil: its charter sentence, its code chain, what it's done lately). Forking is Studio territory (Aug 10) — the shallow end adopts, the deep end remixes.

## 5. Anti-goals, restated for making

No progress bars. No deployment states. No "my creations" shelf (your made things surface in your Seal weekly — accountability, not portfolio). No making that bypasses the strike — an unstruck thing is a draft in conversation, nothing more. And nothing made may violate the realm-expression invariants: made things render inside the same bounded space as everything else.