Open questions stay listed here, and at the end of every working session, until they are decided or explicitly paused.

Legal matters live on their own list — Legal Items for Review — maintained with Legal (Track 9) and never mixed into this page.

## The standing queue

The queue is empty — cleared in full on 2026-08-01. Every OQ-C item (from the Final Canon Taxonomy) and every OQ-B item (from the Studio + Live Working Design Brief) was ruled, absorbed into Taxonomy v1.3.8, or retired to design work. The resolutions are below; what remains unspecified anywhere is design detail, not canon — Field-return defaults, action-state vocabulary, money-movement confirmations, focus-protection defaults, and per-Scene journeys are settled in the app design as it happens, per the owner’s standing instruction that these cannot be answered generically.

(The prior B-queue’s parent rulings remain in force on the brief §9, read through Taxonomy v1.3.8; the sixteen R6/R7 rulings of 2026-07-12 stand unchanged.)

## Recently resolved (full history in versions)

- The close-out of 2026-08-01 (OQ-C6, OQ-C7, OQ-B1..B10). The owner cleared the remainder of the queue in one pass:

  - OQ-C6 · Theme icons → the design repository. All icons, symbols, and graphics across the eight Scenes are built as one consistent, growing repository that populates the universe. Production work, not a canon question. → Taxonomy v1.3.8 §13
  - OQ-C7 · Sub-theme promotion → the adoption rule. Any Realm can adopt anything public or offered to it — the Realm decides. When the Ecosystem (the Genesis Realm, Kinship Duna) adopts something through regular governance, it becomes available everywhere. The rule is general: Abilities, Scenes, sub-themes, vocabulary. → Taxonomy v1.3.8 §12
  - OQ-B1 · First-release journeys → OBE. The brief’s two-working-distances framing is superseded: Studio is a Scene, not a Surface — and so is the rest of that framing. Journeys and starting points are design work. → Taxonomy v1.3.8 §2
  - OQ-B2 · Field return → design. Being designed; too much detail for major canon.
  - OQ-B3 · Focus protection → answered as posed. Ki and the Source figure it out; system prompts and Wisdom establish the baseline; there is no generic solution.
  - OQ-B4 · Action-state vocabulary → design. Cannot be answered generically; settled in app-design detail.
  - OQ-B5 · Privacy classifications → the privacy hierarchy (ruled). An item may carry more privacy than its context, never less; public is only really public in a public Realm. → Taxonomy v1.3.8 §10
  - OQ-B6 · Offline behavior → none (ruled). Not connected means not present; downloads are just downloads. The brief’s offline-preparation language is superseded. → Taxonomy v1.3.8 §11
  - OQ-B7 · Money movement → design. Needs specific UX design, not generic answers.
  - OQ-B8 · Platform floors → recommendation adopted. Desktop 1280 designed / 1024 functional; iOS 16+ / Android 10+; CTV on Android TV at 1080p; WCAG 2.2 AA the formal baseline, nothing formally exceeding it at launch. Owner-adjustable. → Taxonomy v1.3.8 §13
  - OQ-B9 · Validation → none external. No external validation or expert panels at this stage; that’s for particular Realms to decide.
  - OQ-B10 · Realm types → final at ten. Ecosystem · Organization · Alliance · Program · Project · Relationship · Community · Institution · Concept · Cell. Offering retired as a type (Offers is an Element); Member Realm retired as a type. → Taxonomy v1.3.8 §9

- OQ-C5 · The economic rails (2026-08-01). Ruled by the owner, superseding the same-day “internal ledger” reading of Taxonomy v1.3.8 §5. The economy is on the blockchain from day one: every Source has a FROST wallet; every Organization (DUNA), Alliance, and Institution has a Squads wallet; Communities and Relationships hold no wallets. Everything runs wallet to wallet, orchestrated by agentic AI behind the command boundary. What is dropped is the external token platform, whole — launchpads, futarchy (pay-for-voice governance markets, rejected as contradicting equal voting), automatic percent-to-DEX liquidity, founder treasury-draw rights, per-project tokens, and the smart contracts that enforce them: every function they performed is performed by the orchestration and database layers over the real wallets. No new blockchain code is needed to launch; enforcement decentralizes over time. Liquidity is never fragmented: at launch everything runs on $KIDUNA; duna tokens arrive when ready (release mechanics to be specified with the full economy). The utility model is the engine — $KIDUNA pays for intelligence; the Agency Premium (duna-set LLM pricing, premium share to treasury, the waterfall) carries the value. The full economy will be detailed in its own document and nightpaper (commissioned). → Taxonomy v1.3.8 §5, Functional Spec §4.2, Real Work, Real Money

- OQ-C4 · Scene has one sense — and Portals return (2026-08-01). Ruled by the owner. A Scene is a unique area — a room, a scenario, a place — rendered in Flutter/Flame with its sprites, tiles, and interface elements: a cohesive set of Media connected to the full Kiduna stack. The v1.3.4 reading (“a Media system attached to a Realm”) is superseded — the Scene is the composed place itself. The eight canonical Scenes are the launch set; Builders create their own Scenes in Studio and the Workbench and deploy them as unique ways to Enjoy or otherwise use Realms, under the Workbench trust model. A Garden app is exactly a deployed Scene, rendering through the composition grammar. Scenes connect through Portals — that is how you navigate Scene to Scene — reinstating Portals and superseding their v1.3.4 elimination; the design record’s portal grammar (tap to enter, abortable crossing, press-and-hold only for signatures) stands. → Taxonomy v1.3.8 §1

- OQ-C3 · CTV ships in the first release (2026-08-01). Ruled by the owner: a basic version of all four Surfaces — Desktop web, Mobile, Chrome Sidebar, and CTV — is in the initial release. No surface waits for a later wave; depth varies, presence does not. CTV remains Flutter/Flame on Android TV, driven by the mobile devices in the room, Garden first. → Taxonomy v1.3.8 §2, Surfaces v5.9, Functional Spec §5

- OQ-C2 · The Workbench trust model (2026-08-01). Ruled by the owner. What members build in the Workbench are Abilities — the platform’s own Impart Abilities Capacity, member-implemented — plus the Automations composed from them. Safety is Realm containment + role + inspection: a custom Ability operates only in the Realms where it is explicitly deployed (no global deployment, no ambient capability); deployment requires the Builder role in that Realm and is a named deterministic Action; Builder and Ability are inspectable (author, history, provenance, reach — trust the Realm you’re in, trust the Ability deployed there); the plugin checks credentials at hand-off and return so packages only deploy properly within their Realm; a Builder may make an Ability public, and inspection carries its full history into any Realm that adopts it; Sentinels run the acceptance protocol (prompt injection, malicious code, bugs), handshaking with the Claude Code/Codex plugin to double-check flagged items — a returning package lands as a draft, nothing deploys until acceptance passes, and violating packages quarantine as evidence per the standing package-manifest rule. Remaining work is engineering specification (wire-level package format, sandbox runtime), commissioned with the architecture document — not an owner decision. → Taxonomy v1.3.8 §1, Functional Spec §3.4, Create from Within

- OQ-C1 · The Garden interface model: the composition grammar (2026-08-01). Ruled by the owner, same day it was opened. The Garden renders every app through a composition grammar — a small vocabulary of interface primitives (cards, panels, lists, maps, schedules, tiles, chips, action cards; on the order of fifteen, ruthlessly held) with combination rules, authored in Studio (and by Ki) and drawn by a deterministic renderer. Rationale in force: it is the v1.3.4 law (stable Media, dynamic composition, no preset screens) applied to the Garden; it preserves the command boundary by construction (a grammar cannot invent an action — money and votes stay behind named commands); and it makes the next app free, which is what a duna factory needs. Archetypes are starter content, generative is the ceiling: launch apps ship as authored compositions in the grammar (archetype speed without archetype lock-in); post-launch, Ki composes arrangements generatively within the grammar — arranging primitives, never inventing them, Actions always deterministic chips and action cards. Fallback discipline: if launch pressure forces hard-coding an app, it is hard-coded as a composition-in-waiting (same data shapes), never bespoke screens. This gives engineering a countable estimate: primitives + renderer + N apps. → Taxonomy v1.3.8 §1, Functional Spec §3.7

- The Final Canon Taxonomy (2026-08-01). Taxonomy v1.3.8 settled: the eight Scenes (Atlas · Studio · Commons · Workbench · Forum · Exchange · Garden · Vault); Surfaces are form factors (Desktop web · Mobile · Chrome Sidebar · CTV; Vault web-only); the Seven Elements (Offers admitted as first-class, superseding “Offerings are Realms”); the Six Capacities, final (Inform with Wisdom · Instruct for Presence · Empower with Connections · Enable with Automations · Impart Abilities · Align for Coherence — the long-open capacity-verb question is closed: Enable and Impart both exist, and Coherence is the sixth); the economic rails (as refined the same day by the OQ-C5 ruling above: real wallets, orchestration-run economy, $KIDUNA-only liquidity at launch, no external token platform); equal-weight voting (never money-weighted, extending holdings-recognition-none); Commons scoped to Realms; Atlas read-only with Gravity (orbits of relevance, pan/zoom override); and Themes — the intention layer (26-theme spine in 6 clusters, ≤3 per Realm, folksonomy sub-themes, aggregation up the nesting, theme-affinity matching in the Graph).

- Sixteen design decisions (2026-07-12). Projects: stable Scene identity and Field address always; a materialized room is earned by scale. Gold only when work enters or changes the Organization’s authoritative Record; work-in-progress acceptance is light. Spacebar peek cut. No phone Studio in v0 (Live handles participation and simple approvals). Package manifests enforced — violating returns quarantined as evidence, never entering as drafts or Records. The Docket admitted as a projection of standing ACTIONS, never an inbox; no badges. Disclosure sentence + source list both kept. Two signatures, separate Records (profile; Code redemption). Ki’s public door kept, on a capped guest Compute allowance funded as Kinship Duna acquisition-and-education expense. Live voice cut from launch. One store listing — Kiduna, with Live as the mobile experience; kiduna.one/.live stay web entry points. The graph Relationship Record is the single source of truth; surfaces are projections. Room presence counts yes; behavior counts and person scores never. The practice currency is Practice Credits (never “scrip,” never implied transferable). Identity sameness is never claimed without registered proof — proven links render as scoped, dated account links. R5 Studio confirmed as horizon under Surfaces §8. → R7 rulings · R6 rulings

- The counsel brief: sent, answered, adopted. All seven questions came back resolved (2026-07-09); the resolutions live as rules in force on Legal (Track 9), in priority order, held for final review; the standing legal queue moved to Legal Items for Review.

- HEARTS: members see effects, never the instrument. No acronym, no meters, no scores, ever; the Sentinel’s behavior plus plain sentences on request or Contract-set disclosure; the member-facing word is vibe; Symmetry carries the seventh signal, inward and outward. The Sentinel now has its own track — the meters (−100 to +100, zero is health), the two-fields regulation model, and hard human-in-the-loop boundaries. → The Sentinel (Track 8)

- Organizer economics: configuration with a canonical default. Commissions attach only to Compute purchases by an Organizer’s Clan (four generations deep), including initial purchases — never to enrollment itself, work, splits, or votes. Default schedule, all dunas unless changed and Kinship Duna at launch: Gen 1 20% · Gen 2 5% · Gen 3 3% · Gen 4 2%; Catalyst-set at founding, Forum-changeable. USDC purchases pay immediately; fiat purchases show pending until funds bridge on-chain, expected monthly. Lineage optional per duna: open door, invite-only, or invite-then-open. Membership clarified: the $100 is Kinship Duna’s initial Compute purchase; each duna sets its own. → Real Work, Real Money §3, Roles §2, Organizations §3–4, Foundation §6

- Registration, not trust: “registered / unregistered.” The member-facing word for anything bound to the protocol is registered — traceable to a member (FROST wallet), their ally (NFT), an alliance or organization (Squads wallet), and through the WV Org ID to the Secretary of State — never “trusted,” and not “accountable” either: registration proves traceability, nothing stronger. Anything can register — a domain (DNS TXT), a page or piece of content (embedded code), a photo or video (hash). The decentralized Kiduna registry publishes the four address kinds; Kinship Codes carry them as JWT claims, which is how the registry rides the regular internet. Unregistered renders as “a stranger, not a threat.” → Protocol §4, Actions §2, Foundation §2

- Receipt sentences: machine-generated only. The plain sentence over a command receipt is generated by the graph service from the command’s own parameters — never hand-written — so sentence and command cannot disagree; commands that can’t yet generate an honest sentence show their raw name until they can. A build requirement of the graph service. → Protocol §3, Actions §2, Foundation §6

- The promotion ceremony: light, not fireworks. The gold ceremony (stamp, embers, haptic) marks signed acts and nothing else, forever; promotions and other things that happen to a member are announced by the ground briefly brightening. → Surfaces §2, Roles §2

- Holdings recognition: none, ever. No role, badge, or standing derives from balances; balances are never surfaced publicly or to other members. → Roles §2

- Institution recusal + disclosure. Members enrolled with an Institution cannot vote on that Institution’s contracts (enforced at the vote command), and enrollment is always disclosed as part of identity. → Protocol §2, Foundation §6, Actions §2

- Guild promotion path. The ally watches for money-shaped activity around a guild and offers promotion to an alliance in one sentence; guilds never grow wallet features. → Actions §2