Skip to content
Muoto Docs

Concepts

Explanatory material for how Muoto works. Planned topics:

  • Kernel and moldable layer — what the kernel owns and what the application can reshape.
  • AppRevisions — immutable snapshots, activation, and why changes never happen in place.
  • Molding — the loop of propose, validate, activate, and roll back.
  • Work, attempts, and lanes — durable orchestration semantics.
  • Capabilities and audit — how extensions get authority and how it is recorded.
  • Live evolution — old work pinned to old revisions while new work uses new ones.

These pages are under construction. Architecture decisions are always sourced from the engineering contracts (DESIGN.md and KERNEL_CONTRACT.md), which this section explains but never replaces.