Institutional operating system
ARUMBU
By Retro Daddy Soft Tools (RDST)An operating system for institutions, built so that people, work, decisions, authority, finances, documents and institutional memory stay connected in one place.
In private development and testing.
Product evidence
The product is real and running. We are not showing screenshots yet, because the interface is still being refined and we would rather show it when it is worth showing.
Why it exists
Institutions end up spread across tools.
Most growing organisations end up spread across separate tools. People information sits in one system, tasks in another, approvals in email or chat, finances somewhere else, and the decisions that actually mattered get buried in conversations. ARUMBU is being built to give an institution one operating layer where all of that stays joined up. Rather than only showing information, it is designed around what an institution has to do: approve, assign, delegate, escalate, complete, review and remember.
- Work scattered across disconnected software
- Notification and attention overload
- Institutional memory lost when people move on
- Confusion over who holds authority to approve
- Rigid software that cannot match how an organisation actually works
- A need for AI to operate inside clear boundaries
How it works
Ideas behind it
- 01
Built around verbs
Institutional movement is treated as actions rather than records. Approve, Assign, Delegate, Escalate and Complete are the shape of the product, not features bolted onto a database.
- 02
The Attention Contract
ARUMBU separates what genuinely needs your action from what you only need to be aware of. Home is built around that split rather than a single undifferentiated feed.
- 03
Authority follows Position
Responsibility and permissions attach to organisational Positions and the authority structure around them, so a decision routes to a role rather than to a person who happens to be available.
- 04
One institutional spine
People, Work, Money, Documents, Projects and History are designed against a shared institutional model rather than kept as separate products that occasionally sync.
- 05
Institution neutral by design
The architecture is intended to adapt its terminology and structures to different kinds of organisation, instead of assuming every institution works the same way.
What it does today
What works today
Everything below is built and running in the product now.
People and organisation
- People directory with records and memberships
- Position-based organisational structure and position holders
- Affiliations and capabilities as first-class parts of the workforce model
- Centralised permission resolution and position-based authorisation
- Institutional identity, authentication and TOTP enforcement
Work and decisions
- Tasks and approvals through one unified Work model
- Multi-step approval chains and decision flows
- Requesters cannot approve their own item where the rule applies
- Escalation through the authority and reporting structure
- Procedure authoring, and Procedures that run as Tasks
Money, records and projects
- Financial records, transactions, expenses and asset functionality
- Projects
- Document management
- A registry of customers and community stakeholders
- Reports and analytics
Everyday use
- Home, with Act Now, Be Aware and a business brief
- Search across domains, exercised against real data
- Institutional history as part of the operating model
- Institution and account configuration
- Responsive navigation and mobile behaviour
Not built yet
The product vision is wider than what runs today. These are directions we are working towards, and none of them is part of ARUMBU right now.
- A native mobile application
- Sovereign and on-premise deployment
- An extension ecosystem and vertical extensions
- Predictive operational intelligence
- Integration with outside systems
Who it is for
ARUMBU is being built for organisations rather than individual consumers.
- Growing companies and corporate groups
- Healthcare organisations
- Manufacturing environments, including garment manufacturing
- Schools and universities
- Multi-branch organisations
This is who ARUMBU is being designed for, not a list of who is already running it. There is no named pilot customer to point to yet, and we would rather say so.
Tamizhi, and where intelligence sits
Tamizhi is being developed as a governed advisory layer inside ARUMBU. It is designed to observe and to recommend. It is not designed to run an institution, and it does not quietly change institutional state on its own. The engine and the recommendation architecture are real, and the wider cognitive system is still under development.
Alongside it, deterministic rules and analytics produce operational observations without depending on generative AI at all. That is deliberate. An institution should be able to trust what it is being told about itself.
Where it stands today
In private development and testing.
ARUMBU is an early-stage working product. Real authentication and database-backed workflows exist, substantial functionality is in place, and the system has been exercised against synthetic institutional datasets. The interface is actively being refined and several major capabilities are still ahead of us. It is not generally available, and it has not been proven at enterprise scale.
ARUMBU is developed by Retro Daddy Soft Tools (RDST), within the wider Retro Daddy ecosystem.
Want to know more about ARUMBU?
There is no public signup or demo booking yet. If you want to hear where this is going, or you think your organisation is the kind of place it should be tested in, write to us and we will reply properly.