Rules
What a helper may and may not do, and why.
Umwayi hub, pre-release
Every AI helper needs a shepherd.
Umwayi hub is an AI operating system that grew from a notebook.
In 7 weeks it gained rules, a queue, an archive and a logbook. Now it runs AI helpers that only draft.
From a notebook to an operating system
- Sep 16
Memory
A journal, projects and a master context file.
- Sep 20
Rules
Written from mistakes that were caught.
- Sep 20 onward
A queue
Tasks and decisions waiting for the builder.
- Late Sep
Automation
Scripts that publish and cross-post.
- Oct 14
Practices for AI helpers
- Oct 26
An archive
Moved text kept with a fingerprint and a way back.
- Nov 2 to 4
Plans for helpers
98 commits by Nov 5, all in a public repository.
Four parts you can open
How are you arriving?
Nothing about your choice is saved or sent.
The guide says: Choose how you are arriving.
The queue
What waits for a decision.
The archive
What was moved out of the way, with a way to restore it.
The logbook
What changed, and what was not done.
Memory, rules, the queue, the archive, the logbook, the helpers and workflows now run as code in a public repository, started Nov 7.
Open the real parts
Pick a tab. Everything here is from the real hub.
Real content from the hub, as of Nov 5
Rule 1. Confirm the date
Before dating any journal entry, log entry or status row, confirm the actual date. Never infer it from the latest entry.
Caused by: a wrong date on a journal entry.
Rule 2. Treat relayed ideas as understanding
When the builder relays an idea from something they are reading, record it as their own current understanding, not as a confirmed statement of what the source says.
Caused by: a paraphrase recorded as what the author said.
Rule 3. Keep private things private
This repository is public. Never restate a private item in a public file.
Rule 4. Do not push unless told to
Do not push unless the task says so.
14 rules in all. Four are shown.
Rules check
This box shows how a check answers: Yes, No or Ask me first. In the code, an unknown action always gets Ask me first.
Helpers come last
- Built, drafts only
Steward
Built and tested. Reads the plans and proposes tasks, as drafts only.
- Built, drafts only
A social helper
Built and tested. Drafts posts and never publishes.
- Next
A budget governor
Checks your usage limits before a task starts.
- Built
Workflows
Named steps that helpers run as drafts, with one stop switch.
Plan, dates may change
Built in public
Nov 6 to 9Done
Memory, rules, queue, archive and logbook
Built as code in a public repository, with over 900 tests.
Nov 8Done
Scripts, Steward and social helper
Scheduled scripts and helpers that only draft. Publishing always asks you first.
Nov 8 to 9Done
Workflows and a stop switch
One content loop from idea to draft to your approval, and a switch that stops everything.
Nov 9Done
Other AI tools
Adapters so the hub works with other AI command line tools, and a logbook that survives a stopped helper.
Nov 10 to 22Now
Login checks and one spending limit
Each AI tool signs in with its own plan, then one limit counts spending across all of them.
Nov 23 to Dec 2Next
Full check, demo and freeze
A full check of the whole system, a short demo, clear docs, then no new features.
Dec 3Showing
First public demo
First public demo.
Questions
Is this released?
No. It is pre-release and built in public.
Is the code open?
Yes. The new code is in a public repository started Nov 7. The journal stays private and encrypted.
Does it replace my AI tools?
No. It sits between your helpers and your files.
What does it cost?
Not decided yet.