Architecture

How Mullusi and Mullu fit together

Mullusi is the company umbrella and shared foundation. Mullu is the symbolic product family beneath it, with Mullu Govern as the first public product route.

In plain terms: Mullusi owns the company direction and release accountability; Mullu names the products; proof, status, docs, and infrastructure support those products.

Company umbrella Mullusi: identity, strategy, stewardship, governance, research, and public domains.

The company remains accountable for the portfolio and every public release boundary.

Product family Mullu: named symbolic products with explicit contracts and user boundaries.

Mullu Govern is the first public product route; future Mullu products remain staged until their gates close.

Product workflow Request, plan, review, approval, record, and repair path.

Each Mullu product gives its work a visible structure before important action moves.

Shared foundation Proof, status, security, docs, API, dashboard, sandbox, metrics, and research systems.

These Mullusi surfaces support the product family; they are not separate product brands and remain staged where evidence is incomplete.

01

Need

A team has work that needs planning, review, approval, or a clear record.

02

Product path

Mullu Govern gives that work a visible route, context, and next proposed action.

03

Review

Important steps can be checked before they move forward.

04

Record

The reason, decision, result, and repair notes stay attached to the work.

05

Status

Visitors can see what is published now, what is reserved, and where release evidence is still pending.

Read order

Open the next route by question.

Architecture is the map. Use these routes when the next question is about the product, demo, evidence, public directory, or contact path.

System map

Public routes show the product shape without exposing private internals.

Mullusi is the company umbrella. Mullu is the symbolic product family, and Mullu Govern is its first public product route. Status, Proof, Playground, Sciences, and Surfaces are shared company support surfaces for availability, evidence, demos, future domains, and public routes. Product engines, dashboards, and operational data stay private until ready.

  • Public pages describe what visitors can use or inspect now.
  • Private product work is not presented as open customer access.
  • Status and proof pages carry technical runtime details.
  • Architecture is a public map only; it is not a proof stamp or runtime-access claim.
Next Step

Move from map to product.

Start with Mullu Govern for the product story, then use Status or Proof when you need availability and evidence details.