Ι
Immutable public boundary
Mullusi is presented as one governed system across website, docs, release evidence, sandbox, metrics, and contact paths.
[ሙሉ]
Mullu
[Mullu]
Mullusi — the company. Mullu — the flagship product.
Software that checks, traces, and proves every decision before it runs.
Mullu evaluates a proposed action against your rules, records an append-only trace of exactly why, and returns a verdict — before anything executes. It turns governed symbolic reasoning into work you can audit and reproduce. The live runtime is still publishing its signed evidence; until then, this site is the public proof boundary.
In plain terms: Mullu checks whether work is allowed, explains why, and leaves a proof record.
Start Here
Choose the surface
A first visit should route quickly: product, proof, sandbox, or public structure.
Public Surface Metrics
Public surface metrics
Every number below is computed at load time from the same governed JSON the rest of the site renders. If it is shown here, it is verifiable.
- Mullu
- Flagship product route
- 1
- Deployed public surface
- AwaitingEvidence
- Live runtime
Checked before it runsTraceable reasoningFail-closed by default
Tamper-evident traceDomain engines, stagedVerifiable public surface
Checked before it runsTraceable reasoningFail-closed by default
Tamper-evident traceDomain engines, stagedVerifiable public surface
Govern Cloud v1
Govern evaluation service
Start with one vertical contract: authorized request, deterministic evaluation, append-only trace, proof state, repair action, and dashboard visibility.
In plain terms: send an action, get back a verdict, the reason, an audit trace, and a proof stamp.
Use Cases
Use-case fit
Illustrative scenarios — the shape of value the governed runtime will deliver once evidence is published.
Production Claim Boundary
Production claim boundary
The website proves the public company and product route boundary. It does not claim a live governed runtime until the deployment witness endpoints publish signed evidence.
- Mullusi
- Company, research, governance authority, trust boundary, and public domain owner.
- Mullu
- Flagship governed product under Mullusi for proof-backed symbolic work.
- Live Runtime
- AwaitingEvidence until /health, /gateway/witness, and /runtime/conformance close.
- Proof Route
- mullusi.com/proof/ is the public boundary for verified and pending evidence.
Evidence Plane
Evidence plane
Every page answers the same questions: what exists, where it lives, how it is governed, what remains planned, and whether live runtime evidence is closed.
In plain terms: if it is stated here, you can check where it lives and how it is governed.
Λ
Claims tied to evidence
Public claims are separated into the deployed website, private incubation, planned domains, and operational interfaces.
Σ
Content is data-backed
Deployment card, staged domain engines, interface links, proof lanes, and roadmap stages are modeled as structured records.
H
Expansion without redesign
New product surfaces and domains enter the public site through data updates before they need dedicated pages.
Architecture
Governed public spine
The site is structured around Mullusi's invariant model. Public pages point only to the deployed website surface, staged domain engines, proof artifacts, demos, or planned roadmap slots without exposing private incubation work.
In plain terms: every public claim points to a real surface, a planned slot, or nothing — never a guess.
01
Input
Observe task, paper, engine, or product intent.
02
Activate Symbols
Map the task into the system's symbol, rule, and causal-chain terms.
03
Propagate Constraints
Apply governance rules: budget, policy, causality, proof, and lineage.
04
Detect Conflicts
Expose unresolved claims, missing evidence, unsafe transitions, and naming risk.
05
Settle Judgment
Publish only stable meaning, action, deployed surface, demo, or roadmap state.
Interfaces
Public routes
Interface links are treated as managed records so new public routes can be added without reworking the layout.
Docs
Reference material, architecture notes, and public learning paths.
Open Docs →Sandbox
Experimental surface for governed demonstrations and prototypes.
Open Sandbox →API
Public gateway reserved for service contracts and machine-facing endpoints.
Open API →Metrics
Evidence plane reserved for runtime metrics, audits, graphs, and release witnesses.
Open Metrics →Service Stack
Service stack
Packages help users connect, validate, and submit work. Hosted services perform governance, preserve traces, issue proof stamps, and expose operational control.
Product Graph
Product graph
The public site now separates the Mullusi umbrella, the Mullu product route, and the proof boundary. Product-shaped runtime, SDK, science, language, and interface work remains private until release gates are met.
In plain terms: Mullu is public-facing first; the other engines wait for proof-ready release gates.
Mullu
Flagship governed product for proof-backed work, private beta access, product surfaces, and runtime-bound symbolic execution.
Mullu Control Plane
Governance, channels, approvals, budgets, audit traces, multi-provider runtime boundaries, and live witness closure work.
SDK & Cells
MSIC, symbol cells, causal-chain linking, mesh binding, deterministic memory routing, Φ traversal.
Evidence & Interfaces
Search, inspect, capsule, 3D, SCC harnesses, trace surfaces, and proof-carrying public demos.
Science Engines
Science roadmap
Math, physics, engineering, biology, chemistry, and music are staged as governed product families, connected by a cross-domain bridge layer. None are exposed as product-ready public-source releases yet.
In plain terms: the roadmap is sequential; staged domains do not compete with the live product path.
Math
private incubationPhysics
private incubationEngineering
private incubationBiology
private incubationChemistry
private incubationMusic
private incubationUnified Science
private incubationPublic Surface Registry
Public surface registry
Search the deployed public surfaces. Product, runtime, SDK, science, and research source repositories are intentionally excluded from this catalog unless Mullusi approves a separate public-source release.
0
Deployed public surfaces
0
Categories
0
Public product surfaces
Lineage handoff
Registry state feeds release state. A private incubation project becomes a public surface only when its proof surface, docs route, and demo boundary are ready.
Roadmap
Release gates
The public site is ready for direct surface expansion, but each new domain stays private until it has a route, demo boundary, docs route, governance status, and product card that can be defended.
01
Register
Add or revise a deployed public-surface record in the structured registry.
02
Attach
Connect docs, demo, proof, status, and contact routes.
03
Verify
Confirm claims, accessibility, local rendering, and public boundary constraints.
04
Publish
Expose the product surface only after the public boundary is verified.
Judgment Kernel
Judgment kernel
Ψ(PS, SE, EFF, SG, PRR, CPM, ERL, PCE, PCB, K) → J***
Website claims follow the same discipline as the system: observable public surface, stated boundary, reversible update, and no silent failure. That is why the public graph separates deployed surfaces, private incubation, staged domains, and operational interfaces.
In plain terms: Ψ is the judgment step. It releases a public claim only when state, effects, safety guards, proof, and lineage all hold. Anything unresolved, nothing is published.
Architect Note
Architect note
The company surface stays centered on the Mullusi system: deployed website surface, private incubation boundary, staged domain engines, and public evidence. The creator profile is intentionally secondary; it exists only to make stewardship and contact paths explicit.
Frontier Signal
Frontier signal
A daily ranked digest of notable technology, science breakthroughs, and research releases, refreshed automatically from public discussion.
Expansion
Promote after proof
Each new domain can move from private incubation to public surface when the route, demo boundary, docs route, governance status, and release boundary are verified. Mullu remains the first product path under the Mullusi umbrella.