The Field is always present · conversation creates context · prototype truth matters: local outcomes may be simulated, but identity, authority, receipts, and provenance are never fabricated.

Open the prototype → · The prototype record — a living record of the source materials, decisions, reversals, infrastructure, and working artifacts behind it (Genesis Series 01, five phases so far).

## 1. What this is

The first functional prototype: not screens, a working system. David enters a clear Field; Ki greets first; organizations, people, and Projects become visible only as the conversation gives them meaning — the canonical Create-from-Within loop (a Persona, their Ally, and the ability to bring one more person in well). Three rules control the work: the Field is always present (Clear, Context, and Focus change the HUD’s weight, never whether the world exists) · conversation creates context (Ki is the initial interface; the world appears in response to intention, not navigation) · prototype truth matters (local outcomes may be simulated; identity, authority, receipts, and provenance are never fabricated — and the interface labels its execution mode).

## 2. The canonical Ki package — download it

The prototype separates what Ki is, what Ki knows, how Ki works, and what the deterministic system records:

- The Stance — Ki System Prompt, Functional Prototype v1.0 — Ki’s identity, authority boundary (the Source rule), truth order, retrieval rules, permission language, response style, and simulation discipline. A versioned system prompt: the runtime contract.
- The Wisdom — Genesis Ally Complete Operating Knowledge v2.5 — the consolidated corpus (built from Kiduna Kit v2.5, snapshot through 2026-07-14), split by Markdown structure with source file, status, and heading path preserved, ingested into pgvector for permission-scoped retrieval by meaning.
- The Skills — ki-prototype-skills (zip, 14 packages) — Markdown skill packages, each with SKILL.md, references, and an OpenAI agent config: `ki-run-prototype` (the runtime contract, bootstrap, tool contracts, skill routing, the prototype world) · `ki-render-field` · `ki-protect-system` · `ki-manage-ally-identities` · `ki-manage-relationships` · `ki-manage-organizations` · `ki-run-projects` · `ki-run-actions` · `ki-run-forums` · `ki-use-wisdom` · `ki-use-connections` · `ki-supervise-actors` · `ki-create-capabilities` · `ki-manage-compute`.

## 2a. The Dunaversity prototype · 2026-07-20

Open the Dunaversity prototype → — the first working walkthrough of the launch loop: a Catalyst creates a course in Studio, a learner takes it in Live, with the persistent Studio ↔︎ Live switch in both modes. Web prototype as interaction and visual evidence; the production target remains one Flutter codebase. Its complete engineering package: Dunaversity Engineering Handoff v2 (zip) — the controlling Codex brief, implementation checklist, prioritized stories, the web prototype source with decision log and seed fixture, the three static Studio prototypes, the working design system, capability reference, and the prior Studio handoff, with a stated source-of-truth order. The Dunaversity spec itself lives in dunaversity/: the spine, the pathways, the stories, and the brief.

## 2b. The preliminary engineering handoff · 2026-07-19

Kiduna Studio — Preliminary Engineering Handoff (zip) — the source-backed UI/UX model for production engineering: the five Outside-the-Studio journeys, the accepted Gate 1 one-center experiment, the three Gate 2B.1 primary Realm Scenes, the static review site, Design Lab source (commit e729fec), the design-system governance (gates, contracts, matrices, decisions), engineering plan, prioritized user stories, acceptance matrix, and OPEN_DECISIONS_AND_RISKS. Deliberately preliminary: after Gate 2B.1, before Gate 2B.2 — design fixtures and working terms (Atlas, Focus, Pulse, Lens, Stage) are NOT canonical product truth. Live review: kiduna.design/?persona=david.

## 3. The stack under it

Surface: Next.js 16 / React 19 (the Field and the record) · State: PostgreSQL 16 (workspace state, messages, events, receipts) · Wisdom: pgvector, provenance-preserving · Graph: Apache AGE locally (Personas, Allies, Relationships, Organizations, Projects, Actions, Records) — hosted graph runtime still to be chosen; Neon runs Postgres + pgvector in production · Hosting: GitHub → Vercel, continuous deployment. Identity is chosen before entry and fixed for the session; focused conversations and artifacts rise to 94% opacity over the persistent Field; the rejected panel-based redesign is preserved in Git history as a lesson — espresso ground, sky interactions, restrained mint, and gold only for signature-level acts.

## 4. Real now, simulated now, next

Real: the deployed interface, session-fixed identity, the database, persisted workspace, Wisdom storage and retrieval, the versioned source package, the local graph runtime, the pipeline. Simulated (labeled, never hidden): Ki’s domain Actions — invitation preparation, Organization formation, Project creation, Actor invocation, and the resulting Records. Next: deepen Ki’s first conversation one decision at a time; define David’s relationship context for Jeya and Aashik; make the Profiler Action inspectable; let the first real Project and artifact emerge inside the Field.

2026-07-15: section created — the functional prototype live at kiduna.design; the Ki package (Stance v1.0 · Wisdom v2.5 · 14 Skills) posted for download. Full history: versions.