Identity
What the object is and what must remain continuous while its state changes.
How Mullusi works
See a governed action form, stop, proceed, and settle.
This interactive illustration follows one software-change request as Mullusi makes its identity, rules, state, boundary, relationships, approval, evidence, and history explicit.
Illustrative scenario
Not live runtime. No production action is performed from this page.
InputSoftware change request
Decision pointNamed human approval
Completion ruleObserved and verified effect
OutputPersistent causal receipt
Mullusi governed workflow
Request → structure → constraints → approval → execution → evidence → settlement.
Illustrative governed execution scenario
Current transition
A request enters
- ΙIdentity
- ΛLaw
- ΣState
- ΓBoundary
- HHistory
Current stage
A request enters
The request exists, but its identity, rules, affected systems, authority, and completion evidence have not yet been made explicit.
- Governing rule
- No action is valid until the request has a stable identity and declared goal.
- Evidence state
- Intent is present; execution evidence does not exist.
Symbol anatomy
Every important object carries five visible responsibilities.
The visual grammar comes from the Mullusi symbol kernel, not from decorative particles.
Law
Which transitions are allowed, required, blocked, or approval-gated.
State
What is currently requested, blocked, approved, executing, verified, or settled.
Boundary
Which inputs, outputs, disclosures, and real-world effects are permitted.
History
Which causes, alternatives, approvals, observations, and results must be preserved.
Typed relationships
A line has to say what kind of relationship it represents.
The Observatory separates dependency, constraint, authority, execution, observation, and evidential support.
A step cannot proceed until another condition exists.
A policy narrows which possible paths are admissible.
A named authority permits a bounded effect.
An approved gate allows execution to reach the scoped target.
An executed action produces effects that can be measured.
Evidence strengthens a verification or final receipt.
Public boundary
What this page demonstrates—and what it does not.
It demonstrates
- A deterministic governed action sequence.
- Approval before execution.
- Observed evidence before verified success.
- Persistent causal history after settlement.
It does not claim
- Live public runtime access.
- Production execution from this page.
- Customer data processing.
- Open API, pilot, or proof-stamp availability.
Next route
Move from the visual explanation to the product and evidence boundary.
Use Mullu Govern for the product story, then Status or Proof for availability and evidence context.