Prepare release note
Draft a public update for a site change and keep status context visible.
Product preview
A work request becomes a reviewed record.
Mullu Govern is shaped around one practical loop: capture the request, preview the proposed action, route review, and keep the record attached to the result.
- 01PlanScope and context visible
- 02ReviewHuman approval required
- 03RecordEvidence and decision retained
OwnerReviewer
EvidenceAttached
Open1 question
ResultNot executed
Workflow map
The product loop stays review-first.
Mullu Govern is framed around a bounded work loop. Each step keeps context, authority, and record state visible before the next state is reached.
-
01
Request
Capture the work intent, owner, context, and expected result.
-
02
Plan
Turn the request into a bounded proposed action with known open questions.
-
03
Review
Hold important changes until a human reviewer can accept or redirect the plan.
-
04
Approve
Record the decision boundary and the reason the work can move forward.
-
05
Record
Keep evidence, outcome, repair notes, and remaining follow-up attached.
Current availability
Mullu Govern is the first product path under the Mullusi umbrella.
This route explains the product direction: planning, review, approvals, records, and work that needs a clear decision path. Live product-service execution is not claimed until signed gateway, witness, and runtime conformance evidence publish.
- Mullusi
- Company and product umbrella for Mullu and related public routes.
- Mullu Govern
- Foundation product direction for planning, review, approvals, records, and work that needs a clear decision path. Mullu remains the suite family.
- Runtime state
- AwaitingEvidence until /health, /gateway/witness, and /runtime/conformance are signed and reachable.
- What that means
- Not blocked, not promised. The service claim waits until named runtime proof is published and verified.
- Public proof
- mullusi.com/proof/ remains available for visitors who need technical status and runtime evidence details.
What it does
Three practical work loops.
The first public route stays focused on work that needs review, a record, and a clear next state.
Plan work
Turn an intent, request, or task into a visible plan with context, boundaries, and the next proposed action.
Review proposed actions
Keep human authority in the loop before important execution steps move forward.
Keep evidence and decisions
Preserve what was requested, what changed, why it changed, and what remains open for follow-up.
Future surfaces stay behind Mullu Govern.
The public product focus is Mullu Govern: plan, review, approve, record. The surfaces below remain staged directions until their own proof, support, and runtime boundaries close.
Mullu Govern
Planning and review workspace for requests, proposed actions, approvals, and records.
Mullu Inspect
Browser and page review support for understanding public or internal work surfaces.
Mullu CLI
Terminal workflow support with visible commands, review state, and bounded effects.
Mullu Code
Repository work, code changes, tests, and release support.
Mullu Desk
Document, local app, and workspace task support.
Mullu Control Plane
Team workspace for approvals, budgets, history, and deployment readiness.
How it works
From request to reviewed result.
- A work request is turned into a proposed action with context and visible status.
- Important steps can be reviewed before execution and recorded afterward.
- Teams keep the reason, result, repair notes, and history attached to the work.
- The proof route remains available for visitors who need technical status details.