Skip to content

One institution, distinct domains

The domains share Mpalo’s purpose and identity while adjusting language, visual density, and interaction to the work each one serves.

Shared purpose, calibrated expression

Domains do not get separate values. They apply the same institutional purpose to different audiences, tasks, and levels of technical depth.

Typography, color, and interaction may vary by domain. Their meaning should remain connected to the shared system, and a domain-specific choice should have a recorded reason.

Domain layers

Main public domain
Institutional identity and public purpose. Humanist and naturalist expression; accessible explanations lead, with technical detail available by choice.
Audience: public, partners, prospective users
API domain
Technical reference and integration. Precise contracts and task-based guidance retain human context and clear capability status.
Audience: developers integrating Mpalo services
Welcome domain
Account entry and verification. Authoritative, calm, and direct. Security steps, errors, and next actions are stated plainly.
Audience: people creating or accessing an account
Mind Platform
Operational and analytical work. Dense information is organized for scanning and control. Explanations stay concise and interactions remain predictable.
Audience: platform users doing focused work
Terminal and expert tools
High technical depth, explicit state, and useful verbosity. Keyboard operation and precise feedback are central.
Audience: expert operators and developers

These are intended design roles. They do not assert that every current page fully conforms. Each domain page in this hub should eventually link to its implemented tokens, components, and audits.

What changes as technical depth increases

  • Language: from broad purpose and plain explanations toward precise terms and explicit system state.
  • Density: from guided orientation toward compact, scannable information, without removing necessary context.
  • Visual expression: from humanist and naturalist emphasis toward technical hierarchy, while retaining Mpalo’s type roles and color meaning.
  • Interaction: from guided steps toward direct control, keyboard shortcuts, and explicit feedback.
  • Evidence: every layer distinguishes current behavior from direction, plans, and unknowns.
See the governed design categories