Product and fit
Ask whether Mullu Govern fits your team and which actions you would put under review.
One person, one product, no investors. Mullusi is building the pause before a risky software action: a named approver, the evidence beside the request, and one record of what was decided.
Software and operations teams already have chat, tickets and dashboards. What they lack is a plain pause before a risky action runs. Mullusi exists to build that pause and nothing else.
The founder does the product design, the systems architecture, the software and the research behind everything on this site.
This website, a review demo that runs in your browser, the documentation, a status page and a security page. Every claim on these pages points at something you can check yourself.
The hosted product is not open yet. What has to happen first is tracked on the status page as Available, Not yet or Planned, with no dates attached.
The same review and record may one day serve research work in mathematics, physics, engineering, biology, chemistry and music; each is Planned, with no demo and no dates.
Commitments the company holds itself to.
Every page says what is available and what is not yet, in those words.
No automatic approvals. A named approver says yes or holds, and the requester is never the approver.
Nothing is claimed on this site that cannot be checked from the site itself: headers, status.json, security.txt.
Held or approved, every reviewed action leaves the same record: request, plan, questions, decision, rollback.
No investors, no grants and no customers yet. The founder pays for the work; voluntary support goes to hosting, domains and development time.
Support the work →Replies come from the founder. No form, no account.
Ask whether Mullu Govern fits your team and which actions you would put under review.
Questions about the approach, the record format, the Amharic work and Mfidel, or a collaboration or publication.