# Decision Log

This is the compact record of approved design constraints. `OPEN_DECISIONS.md` contains unresolved questions.

| ID | Status | Decision or hypothesis | Basis | Revisit when |
|---|---|---|---|---|
| D-001 | Accepted at Gate 0; canonically compatible with 1.3.3 · 2026-07-19 | Studio is the primary desktop/laptop Surface into the always-present Field; its default presentation is a focused conversational workspace centered on the active Realm. | Owner approval plus canonical Sections 1–2 and 8 | A later canonical version or user evidence changes the Surface model |
| D-002 | Accepted at Gate 0 · 2026-07-19 | One active Realm, one current Focus, and one dominant work surface organize each scene. | Owner approval; user request for clean, powerful hierarchy | A proven journey requires parallel focus |
| D-003 | Accepted at Gate 0 as a design hypothesis; reaffirmed non-canonical in 1.3.3 · 2026-07-19 | Atlas is the working name for a possible broad orientation presentation within the Field. The Field itself is the complete environment and is never an optional mode. | Owner approval plus canonical Section 1 boundary | Atlas fails orientation tests, is rejected, or receives a different/canonical name |
| D-004 | Accepted at Gate 1 · 2026-07-19 | Elements appear as contextual instruments and recede when their work is complete. | Owner acceptance of scheduling instrument, Source Lens, and Artifact Stage | Users lose necessary continuity |
| D-005 | Inherited visual direction | Espresso-black foundation, warm cream type, blue primary action, restrained gold, mint, and red semantics. | Outside-the-Field designs and user feedback | Accessibility or cross-surface testing fails |
| D-006 | Inherited form direction | Stable circles, spheres, arcs, and nature-like geometry; avoid lumpy irregular boundaries. | User feedback on Pass 3 | A specific semantic need proves otherwise |
| D-007 | Accepted at Gate 1 · 2026-07-19 | The one-center shell may move from calm conversation to an inline instrument and an Artifact Stage without introducing the Field or permanent multi-panel chrome. | Owner acceptance of the three-scene Gate 1 prototype | Gate 2 reveals a Realm-intelligence conflict with the shell |
| D-008 | Superseded at Gate 2A · 2026-07-19 | Kiduna Core Taxonomy Version 1.3.2 superseded Version 1.3.1 and supplied the complete Sections 1–21 baseline. | Owner-supplied consolidated taxonomy | Superseded by D-009 / Version 1.3.3 |
| D-009 | Canonical source · 2026-07-19 | Kiduna Core Taxonomy Version 1.3.3 supersedes Version 1.3.2. It clarifies the Field as always-present but not necessarily continuously visible context and makes ongoing, collective, authorized Realm agency explicit. | Owner's Gate 2 activation plus full Version 1.3.2 | A later owner-authorized canonical version is created |
| D-010 | Owner direction · 2026-07-19 | Each subsequent design turn includes a taxonomy-impact check and either a versioned update with provenance or an explicit “no taxonomy change.” | Gate 2 activation | Owner changes the design-governance cadence |
| D-011 | Gate 2A working constraint · 2026-07-19 | Gate 2A uses “dominant conversational surface” as a neutral term; Chat, Work, and the relationship of Ki to the Panel remain unresolved. | Open terminology plus Version 1.3.3 boundary | Owner accepts a tested term |
| D-012 | Accepted at Gate 2A · 2026-07-19 | Canonical Taxonomy Version 1.3.3, the three Realm Intelligence Contracts, collective-agency model, cross-Realm behavior matrix, and Gate 2B scene briefs are accepted as the design basis for Gate 2B testing. Acceptance does not convert non-canonical design terms into taxonomy or establish missing production authority. | Owner instruction: “Approve Gate 2A and begin Gate 2B.1 only.” | Realm testing reveals a contradiction or the owner revises the contracts |
| D-013 | Owner-directed review sequence · 2026-07-19 | Gate 2B is split into Gate 2B.1 primary scenes and a later, separately authorized exceptional-scene pass. Gate 2B.1 contains exactly the three approved primary scenes and does not begin Gate 2B.2. | Owner scope instruction | Owner accepts/revises Gate 2B.1 and explicitly authorizes the next pass |
| D-014 | Owner-directed preliminary handoff · 2026-07-19 | Between Gate 2B.1 and Gate 2B.2, provide engineering with a versioned UI/UX evidence package for planning and reversible foundational work. This is not the final Gate 7 handoff, production authorization, or acceptance of unresolved design proposals. | Owner request to pause and prepare engineering planning material | Gate 2B.2 and later gates supply exceptional states, grammar, coverage, and final implementation authority |

## Update rule

At every gate, change a row to **Accepted**, **Rejected**, **Revised**, or **Deferred**; record the evidence and date. Never convert a proposal into an inherited requirement.
