# Kiduna Studio v1 capabilities

This package is the UI/UX completeness baseline for the next Kiduna Studio design. It reconciles the **209 screens** in [Review Library v1](https://kiduna-ui-review.vercel.app/review_v1) with capability evidence from the `main` and `dev` branches of:

- `mmosh-pit/kinship-shared` — Studio/web application and market/governance services
- `mmosh-pit/kinship-agent-be` — agent, chat, tools, knowledge, approvals, skills, and graph services
- `mmosh-pit/kinship-knowledge` — game generation, game knowledge, runtime, progress, and analytics
- `mmosh-pit/kinship-assets` — assets, scenes, platforms, projects, games, storage, and scores

## Start here

1. [Executive capability map](01-executive-capability-map.md)
2. [New UI completeness checklist](12-new-ui-completeness-checklist.md)
3. [UI coverage and gap register](11-ui-coverage-and-gap-register.md)
4. [Main/dev branch differences](13-main-dev-differences.md)
5. [Scope, method, and evidence rules](00-scope-methodology.md)

## Domain documents

- [Identity, accounts, onboarding, membership](02-identity-accounts-onboarding.md)
- [Agents, chat, voice, skills, tools, approvals](03-agents-chat-skills-tools.md)
- [Wisdom, vector knowledge, graph context, prompts](04-knowledge-wisdom-prompts.md)
- [Studio game and world building](05-studio-game-world-building.md)
- [Assets, media, metadata, and scene composition](06-assets-media-scenes.md)
- [Communities, contexts, handles, roles, invitations](07-community-contexts-roles-codes.md)
- [Markets, DUNAs, governance, treasury, tokens](08-markets-governance-treasury.md)
- [Runtime, progress, achievements, analytics](09-runtime-progress-analytics.md)
- [Public site, CMS, launchpad, commerce](10-public-cms-commerce.md)

## Audit resources

The `resources/` directory contains machine-readable and human-readable evidence:

- `review-v1-screen-inventory.md`, `.csv`, `.json` — all 209 review screens
- `api-endpoint-inventory.md`, `.csv` — 1,140 endpoint declarations across both branches
- `data-model-inventory.md`, `.csv` — 894 model/type declarations
- `ui-control-evidence.csv` — 1,386 statically detected UI controls and labels
- `capability-catalog.csv` — normalized product capability list and proposed UI coverage status
- `inventory-summary.json` — package totals

## How to use this in design review

Treat every unchecked item in the completeness checklist as a required product decision. A capability does not always require a dedicated page, but it must have a discoverable surface, a safe execution path, or an intentional admin/API-only designation. Destructive, financial, identity, publishing, approval, and externally connected actions also need confirmation, status, error, retry, and audit states.

