# Dunaversity Engineering Handoff

Prepared: 2026-07-20  
Prototype: https://dunaversity-prototype.motodave.chatgpt.site

Package revision: **v2** — includes the persistent Studio ↔ Live switch in both prototype modes.

## Build target

Build the first working Dunaversity prototype described in `01_CONTROLLING_BRIEF/DUNAVERSITY_CODEX_BRIEF_v0.1.md`.

The production target is **one Flutter codebase** with adaptive **Studio** and **Live** layouts. The web prototype included here is interaction and visual evidence; it is not the production architecture.

## Source-of-truth order

If material conflicts, use this order:

1. `01_CONTROLLING_BRIEF/DUNAVERSITY_CODEX_BRIEF_v0.1.md` — controlling scope and acceptance criteria.
2. `01_IMPLEMENTATION_CHECKLIST.md` — engineering-oriented extraction of that brief.
3. `03_PROTOTYPES/dunaversity-web/DECISIONS.md` — decisions made to keep the web walkthrough demonstrable.
4. `02_USER_STORIES/` — additional Studio stories and continuity requirements.
5. `04_DESIGN_SYSTEM/` — visual and interaction grammar.
6. `05_CAPABILITY_REFERENCE/` and `06_KIDUNA_KIT/` — broader capability and system context.
7. `07_PRIOR_ENGINEERING_HANDOFF/` — previous evidence, plans, prototypes, and unresolved questions.

The controlling brief references `STORIES.md v0.1` but explicitly states that it is self-contained. No separate Dunaversity `STORIES.md` was present in the supplied files. The two additional story documents found in the workspace are included under `02_USER_STORIES/`.

## Package map

- `01_CONTROLLING_BRIEF/` — the complete Dunaversity brief supplied to Codex.
- `02_USER_STORIES/` — prioritized Studio stories and the earlier prototype story set.
- `03_PROTOTYPES/dunaversity-web/` — latest interactive prototype source, including README, decisions, seed fixture, design assets, and simulated walkthroughs.
- `03_PROTOTYPES/studio_v1/`, `studio_v2/`, `studio_v3/` — earlier static Studio prototypes.
- `04_DESIGN_SYSTEM/` — visual direction, interaction patterns, Realm experience model, evidence, and working design-system instructions.
- `05_CAPABILITY_REFERENCE/` — capability maps, coverage reports, and source traceability.
- `06_KIDUNA_KIT/` — broader Kiduna system, architecture, taxonomy, surface, role, governance, and design references.
- `07_PRIOR_ENGINEERING_HANDOFF/` — the prior complete Studio engineering package in extracted form.

## First engineering review

1. Read the controlling brief completely.
2. Run the Dunaversity web prototype and complete the Aashik, Matt, and Moto walkthroughs in order.
3. Review `03_PROTOTYPES/dunaversity-web/DECISIONS.md` so prototype conveniences are not mistaken for production decisions.
4. Review the architectural law, permission matrix, classification boundary, Action/Record contract, and simulated-money requirements before choosing state-management or persistence details.
5. Log any ambiguity that changes authority, privacy, treasury, identity, provenance, or agent autonomy before implementation.

## Running the latest prototype

From `03_PROTOTYPES/dunaversity-web/`:

```bash
npm install
npm run dev
```

The Studio / Live control previews both adaptive renderings. All prototype state is in memory and resets on reload. Payments, wallets, NFTs, voice, research, uploads, chains, and the Scene are simulated or stubbed.

## Package hygiene

This handoff excludes credentials, `.env` files, source-control metadata, dependencies, caches, local hosting identity, and generated build output. Install dependencies locally from the included lockfiles.
