Mullu, by Mullusi

Mullu

Symbols are atomic. Meaning is relational. Traversal is governed. Judgment is earned.

Governed symbolic intelligence for real work: personal operations, enterprise workflows, deployment, research, code, documents, communication, and proof-backed execution.

Request access Read architecture Review proof boundary

private beta while trademark, domain, and deployment gates complete.

Production Claim Boundary

Mullu is a symbolic product under the Mullusi umbrella.

This product route explains the Mullu surface. It does not claim live production runtime closure until Mullusi publishes signed gateway, witness, and runtime conformance evidence.

Mullusi
Company, governance authority, research boundary, and public trust owner.
Mullu
Flagship governed product for proof-backed work and symbolic execution surfaces.
Runtime state
AwaitingEvidence until /health, /gateway/witness, and /runtime/conformance are signed and reachable.
Public proof
mullusi.com/proof/ separates verified website evidence from pending deployment witness closure.

One product, governed surfaces.

Mullu

Governed work across files, research, workflows, deployment, connectors, and memory.

Mullu Inspect

Symbolic browser inspection and evidence capture for public and internal surfaces.

Mullu CLI

Terminal-native governed execution with traceable commands and bounded effects.

Mullu Code

Repository work, code authoring, review, tests, and release support.

Mullu Desk

Computer-use workflows across documents, local apps, and workspace actions.

Mullu Control Plane

Enterprise governance, approval, audit, budgets, lineage, and deployment controls.

Governed execution

Work should leave proof.

  • Every governed action is auditable, budget-controlled, policy-enforced, and approval-gated when risk requires it.
  • Mullu preserves the causal chain behind work: who asked, what changed, which constraints applied, what evidence closed the task, and what memory was admitted afterward.
  • Mullusi remains the company and governance authority behind the product, research, audit, and infrastructure layers.
  • The public proof boundary separates published website evidence from pending live runtime witness closure.