Doctrine · the room agreement
What Naya refuses, and what it commits to.
A working system has to know what it will and will not do — before the pressure of a quarter or a board or a churn metric tries to teach it otherwise. These are the refusals and the commitments Naya is built on.
Read time · 3 minutes · Last revised April 2026 · Held quietly
Part one · what the system refuses
No streaks. No badges. No red. No optimize.
- Refusal 01 — No streaks. Continuity is a feeling, not a counter. The thread doesn't break because you missed a day — it was never measured. Continuity ≠ Counter
- Refusal 02 — No badges. Presence is not a reward mechanic. We don't pay you in shapes for showing up. The room itself is the only reward there is. Presence ≠ Reward
- Refusal 03 — No red. Urgency is a body state, not a color. Naya will never use alarm to recapture your attention. The palette stays warm and quiet, even when something matters. Urgency ≠ Color
- Refusal 04 — No optimize. Naya does not improve you. It accompanies you. There is no better version of you to ship by Q4 — only the one already here. Naya ≠ Improvement engine
A refusal alone is not a doctrine. Here is what the system commits to instead.
Part two · what the system commits to
Naya adapts to the rhythm of being alive, not the rhythm of maximum output.
The day is not optimized. It is observed. The system meets you where you actually are — including the hours where you are nowhere in particular at all.
- Commitment 01 — Stillness is not failure. A morning where nothing is captured is still a morning the system held. We will not retroactively call it a missed day.
- Commitment 02 — Recovery is not inefficiency. The hours that look like nothing are the hours that make the other hours possible. The system treats them as load-bearing, not as gaps to close.
- Commitment 03 — Pauses are load-bearing. A pause carries the work forward in a different posture. The continuity feed reflects this — what was held is still there when you return, with no escalation.
The thread of self is not allowed to drop because a process did.