# Open Decisions and Contradictions

Do not resolve these silently.

## Current taxonomy

Kiduna Core Taxonomy Version 1.3.3 is the current complete consolidated document. It supersedes Version 1.3.2 while retaining all Sections 1–21 and adds the Gate 2 canonical boundary and provenance record.

Version 1.3.3 clarifies that the Field is always present but not necessarily continuously visible; that Realms and authorized Actors may remain active, coordinate, contribute, and request attention; and that a dominant Panel or bounded Scene remains inside Field context. Atlas, Focus, Pulse, Lens, Stage, and one-center shell remain design terms rather than canonical objects.

### Field and Atlas terminology correction

Earlier working documents sometimes used **Field** to mean an optional spatial overview. Version 1.3.3 makes the distinction explicit: the Field is the complete living Kidunaverse environment and Studio is a Surface into it. The accepted focused behavior remains valid, but **Atlas** is only a working proposal for possible broad orientation. Atlas is not canonical taxonomy.

## Legacy-to-canonical vocabulary

The V1 capability audit contains older overlapping terms:

- context / platform;
- project / gathering;
- market / DUNA;
- agent / avatar / Presence / member;
- performer / worker / Actor;
- knowledge / wisdom;
- movement / mission;
- team / alliance; and
- skill / ability / automation.

Decisions are required for which legacy terms map to canonical Realms, Presences, Actors, Elements, Artifacts, Scenes, Roles, Offerings, and other concepts. Until then, keep original source language in traceability and use canonical language only where the mapping is unambiguous.

## Product decisions

| Decision | Recommendation | Status |
|---|---|---|
| Default inside surface | Main conversation/workspace; Atlas entered on demand. | Proposed |
| Top-level mode label | Test **Chat**, **Work**, and a combined label in context; do not add a third permanent mode prematurely. | Open |
| Realm header | Keep Realm identity and purpose persistently visible but quiet. | Proposed |
| Multiple chats | One main conversation with contextual routing; dedicated history may be filtered by Realm, Actor, Presence, or Element. | Proposed |
| Element expansion | Preview → Lens → Stage based on depth and duration. | Proposed |
| “Chat with Element” | Route through Ki or a relevant Actor with the Element attached as context. | Proposed |
| Collaborator visibility | Ambient unless speaking, changing work, or providing required authority. | Proposed |
| Color | One primary accent; gold/mint/red reserved for semantic states. | Proposed |
| Atlas role | Optional orientation, relationship, discovery, and return presentation within the Field—not the universal task interface. **Atlas** remains a proposed name. | Proposed |
| Realm boundaries | Visible in Atlas or Realm inspection; not a permanent container around all work. | Proposed |
| Panels | Temporary Lens/Stage rather than permanent multi-column chrome. | Proposed |
| Realm templates | Seed intelligence contracts for common Realm types while preserving Realm-specific design. | Open |
| Compute | Quiet Pulse by default; detail appears for limits, cost, policy, or user request. | Proposed |
| Treasury | Realm Lens plus explicit governed Action flows; never a generic wallet card alone. | Proposed |
| Cross-Realm attention | At most one quiet, material, authorized attention signal in the focused surface; broader review on demand. | Proposed for Gate 2B |
| Contribution envelope | Source, scope, visibility, authority, provenance, retention, correction, and Record travel with a contribution. | Proposed for Gate 2B / Gate 3 validation |
| Collective reflection | Ki may synthesize only consented contributions eligible for the receiving scope and must preserve uncertainty and minority views. | Proposed; requires policy validation |
| Scene necessity | Use a Scene only when bounded spatial, temporal, simulated, performative, or embodied interaction materially improves understanding or participation. | Proposed for Gate 2B validation |

## Gate 2 Realm decisions

| Decision | Current position | Status |
|---|---|---|
| Inner Clinic legal/clinical custodian | Unknown; no compliance or production claim may be made. | Open — C-007 |
| Inner Clinic participating Institutions | Owner-proposed; official missions verified, relationships not verified. | Open — C-009 |
| Inner Clinic contribution canon | Personal, Community, Alliance, Organization, Institution, and public scopes need governance authority. | Open — C-008 |
| Nature of Work source corpus and participant policy | Not supplied. The contract can define required boundaries but not assert current readiness. | Open — C-010 |
| Organizational collective learning | Never derived from private Ki conversations; use explicit contribution and consent paths. | Proposed |
| 2nd Cavalry current member count | Do not choose among 3,192, 4,377, 4,371 invited, or “over 4,400” without object/date reconciliation. | Open — C-001 |
| Dragoon Base migration authority | Inventory, custody, licenses, consent, deletions, and verification are not supplied. | Open — C-002/C-016 |
| Service Alliance / SADUNA / Kiduna Club structure | Keep distinct and confidential where sourced from the backbrief; status requires confirmation. | Open — C-003/C-004/C-019 |
| Historical reconstruction authority | Require provenance, contestability, and a named editorial authority before a Scene is accepted as documentary. | Proposed |
| Program as Realm type | Use `Program Realm (Other Realm Type)` until canon changes. | Open — C-011 |
| Record as canonical object | Identify each Record's Artifact/event/registry representation; do not assume a new canonical object. | Open — C-012 |

## Contradiction with earlier visual direction

Earlier direction asked for a broad accent palette to distinguish organizations. Current direction prefers less color and stronger hierarchy. Treat the current request as superseding the earlier palette proposal for operating UI. Realm-specific content may still carry distinctive imagery and color within the restrained shell.

## Contradiction with screen-based completeness

The V1 audit's recommended navigation families are useful for coverage, but a literal navigation implementation would reproduce the fragmented product. Use them as audit categories, not automatically as top-level user navigation.

## Evidence needed before final handoff

- Accepted mapping from legacy repository terms to canonical taxonomy.
- Accepted one-center shell.
- Accepted Realm Intelligence Contract.
- Accepted Element lifecycle and Lens/Stage behavior.
- Accepted Atlas role and layer grammar.
- Accepted capability-to-pattern matrix.
