# Learning Kiduna

This primer explains how to approach Kiduna. It is not a second taxonomy. When wording or scope differs, `../canon/Kiduna-Canon-Taxonomy.md` controls.

## Kiduna in one sentence

Kiduna is a living environment in which humans can create, relate, organize, govern, exchange value, learn, and act across distinct contexts while keeping identity, authority, and consent intelligible.

## The basic conceptual grammar

Kiduna begins with a few first-principles distinctions:

- **Elements** are what exists and interacts.
- **Relationships** describe how things are connected.
- **Forces** describe what acts upon the system over time.
- **Actions** are defined operations that produce effects or change state.
- **Capacities** describe what a Realm or intelligence knows, can access, can do, and can remain coherent around.

The Canon supplies the exact definitions and the rest of the categories used to design and understand Kiduna.

## Human presence and bounded intelligence

The Source is the human. The human may become present within a Realm through an Avatar, which is a Source-controlled representation rather than a separate identity. Allies are intelligences with which a Source or Realm collaborates. Actors are intelligent operators with bounded work.

This separation matters. Representation does not become personhood; assistance does not become human consent; competence does not become permission; and a Realm-scoped Role does not become universal authority.

## Realms and Scenes

A Realm is a context in which identity, intelligence, relationships, resources, governance, and activity come together. A Scene is a situated composition through which a Realm becomes present, experiential, and interactive.

This encourages a shift from “which screen should exist?” to “what situation is the Source entering, what is meaningful here, what may happen, and who is authorized?” A Scene can remain semantically stable while its presentation changes for a Source, Surface, Dimension, or Form.

## Forge, Rehearse, and Field

The same underlying work can be experienced through three concurrent Modes:

- **Forge** is where changes are made.
- **Rehearse** is where a Draft is reviewed and tested.
- **Field** is where Sources participate in a Final published experience.

The lifecycle is Forge → publish as Draft → Rehearse → publish as Final → Field. Publishing changes availability, not the identity of the underlying work.

## Five Forms

The Canon names five primary Forms through which a Scene may be expressed:

- **Literal Spatial** — a recognizable place or environment.
- **Symbolic** — meaning through symbols, objects, and visual language.
- **Impressionistic** — atmosphere, feeling, motion, light, and texture.
- **Diagrammatic** — structure, relationship, flow, and state.
- **Hybrid** — a purposeful combination of Forms.

The images in `../assets/forms/` illustrate these possibilities. They are not a required look, a fixed interface shell, or current product screenshots. Trusted labels, state, and rights should remain explicit rather than being hidden inside decorative or generated imagery.

## Resources and value

Resources are usable holdings and instruments. The current Canon defines eight Resource types: Capacity, Badge, Code, Coupon, Invitation, Ticket, Gift, and Reward. Capacity means prepaid utility credit; it must not be confused with plural Capacities, which are foundational capabilities.

Resources can carry utility, proof, access, benefit, opportunity, admission, or value. A Resource may affect a Role, Offer, Exchange, or Action, but it does not silently create membership, consent, identity, or authority.

## Trust is structural

Kiduna work should preserve several boundaries:

- Prepare possible work freely; commit consequential effects deliberately.
- Make the active Realm, Source, target, Role, permission, and Action intelligible.
- Keep access, action authority, spending authority, and governance authority distinct.
- Preserve the difference between a claim, evidence, interpretation, draft, publication, and completed Action.
- Keep origins, evidence, and current state visible.
- Do not let convenience silently join Realms or expand permissions.
- Make failures, uncertainty, correction, reversal, and recovery understandable.
- Do not weaken privacy, accessibility, or authority because Capacity or another resource is scarce.

These are explanatory design principles, not substitutes for the Canon or for domain-specific law and policy.

## Designed for whole human lives

Kiduna should remain coherent for people whose lives cross many legitimate contexts:

- a person balancing discovery, family, culture, political commitment, and demanding research;
- a practitioner holding care and accountability together without turning reflection into surveillance;
- a creator protecting consent, rights, labor, and participant relationships across a complex production;
- a steward coordinating family, service, institutions, health information, youth development, and small business without collapsing their boundaries.

The common standard is to help people carry complex intentions across time and contexts without allowing convenience to erase dignity, relationship, or control.

## How to work with this Kit

Useful requests include:

- “Teach me the categories and how they fit together.”
- “Return the canonical definition of Source, Avatar, Ally, and Actor.”
- “Classify this idea and show where the classification is uncertain.”
- “Prepare a Realm or Scene proposal using the current taxonomy.”
- “Compare this product language to Canon and identify conflicts.”
- “Draft a proposed Canon change, but do not present it as approved.”

Always ask whether a statement is canonical, interpretive, proposed, or implementation-specific. That habit is the shortest route to learning Kiduna accurately.
