System Library

Unit App System Library

Canonical standards, invariants, and implementation doctrine for building Unit product systems.

Source of truth
Pillars

Three pillars, one system

Every Unit module — wallet, vault, identity, future — sits on the same three pillars. Engineers, reviewers, and integrators all read from these surfaces.

System principle

Standards are how the system is built — not documentation after the fact.

If a module can't be previewed, tested, explained, and handed off, it is not complete.

Who reads this

Three audiences, one library

Different roles read this library at different points in the lifecycle. Standards apply identically to all three.

Engineers

Before coding

  • Read the module spec and the invariant map.
  • Identify the closed state model and forbidden patterns.
  • Pick the correct design tokens; do not invent new ones.
  • Plan the preview + test pipeline before writing TSX.
Reviewers

Before approval

  • Run the reviewer checklist against the change set.
  • Confirm spec → screen → preview → test parity.
  • Verify forbidden patterns are absent (grep + assertions).
  • Confirm the completion report carries this pass.
Integrators

Before main-app promotion

  • Run the live-codebase alignment audit.
  • Map module states to live GraphQL / chain states.
  • Confirm decimal precision and fee semantics align.
  • Verify role separation (user vs operator) is enforced.
Quick links

Start here