domain doctrineThe Codices

Codex 6 — Experience Doctrine

The experience doctrine: confidence as the product, and the register in which the institution speaks.

Authority rank
3
Version
v1.2
Adopted
unrecorded
Held by
Executive Office
System
SYS-09

Source · docs/codices/CODEX-6-experience-doctrine.md

Register

Timeless, institutional, premium, intelligent, calm, minimal, professional, trustworthy. The interface should feel as though it was designed by people who expect to be judged in fifty years.

Required

  • Semantic design tokens for every colour, gradient, and shadow. No hardcoded colour utilities in components.
  • Typographic hierarchy that carries meaning: eyebrow, numeral, hairline, body, marginalia.
  • Generous restraint: whitespace, one idea per view, no competing focal points.
  • Reusable primitives. A pattern used twice becomes a component.
  • Accessibility: keyboard operability, visible focus, sufficient contrast, correct landmarks and headings, alternative text, respect for reduced-motion.
  • Localization readiness: no concatenated sentences, no text baked into images, layouts that survive longer strings.
  • Every content route carries its own metadata: a unique title under 60 characters, a description under 160, and social tags.

Forbidden

  • Startup clichés, purple-on-white gradients, default sans stacks used as identity.
  • "AI aesthetics": glows, neon, generated-looking ornament.
  • Social-media patterns: infinite feeds, vanity counts, notification pressure.
  • Gamification that manipulates attention: streak guilt, artificial scarcity, countdowns.
  • Dark patterns of any kind, including hard-to-find cancellation.
  • Loud marketing voice in institutional surfaces.

Writing

Plain, declarative, unornamented. Institutional register, not advertising. Terms are used in their technical sense once the institution has defined them. Claims are specific or absent. Never promise certification, compliance, or audit outcomes without documented evidence and approved wording.

Consistency

New surfaces reuse the existing design system, layout primitives, spacing, and navigation patterns. A page that feels bolted on is a defect, regardless of how good it looks alone.

Institutional UX

This is where Anabasis differs from software built to be used. Our surfaces are built to make people capable.

Confidence is the product. A person should leave every screen more certain of what is true, what they have done, and what to do next. Uncertainty is the failure state, not boredom.

One idea, one primary action. Each view has a single clear next step. Secondary paths are available but never compete for the eye.

Progressive disclosure. Depth is revealed as the person reaches for it. Complexity is earned by the user, never imposed on arrival. Advanced controls exist, are discoverable, and stay out of the way until wanted.

Beginners supported, experts respected. The same surface serves both by layering — plain language on the outside, precision underneath — not by forking into a simple product and a real one. Nothing is condescending; nothing assumes vocabulary the institution has not yet taught.

Cognitive load is a defect metric. Each of the following is a bug to be filed and fixed: unexplained jargon, unlabelled state, ambiguous destinations, hidden consequences, more than one plausible reading of a control, and any form asking for information the institution already holds.

Guide rather than instruct. Sequence, defaults, and structure carry the person forward. Long instructional copy is a symptom of a structural problem.

Mastery is rewarded with capability and standing — access, responsibility, credentials, recognition by name. Never with points, streaks, levels, or badges of mere participation.

Prohibited at the interaction level, restating Codex 1, Article VI as an interface rule: manufactured urgency, countdowns, artificial scarcity, loss-framed nudges, notification pressure, infinite feeds, vanity counts, consent bundled into unrelated actions, obstructed cancellation or export, and any mechanic designed to make leaving feel costly.

Accessibility and reversibility. Every action a person can take, they can understand, undo where undoing is possible, and be told plainly where it is not.

The acceptance test. Every interaction answers one question: did this make the person's life better? If the honest answer is "it increased engagement", the interaction fails and is removed.