Run Your Company on Claude. Keep Your Hand on Send.
A free kit that gives every person on your team a Claude that reads the same rulebook, prepares their day, and drafts what they owe. Nothing goes out until a person sends it.
Version 0.3. Plain text files: chapters, templates and prompts. No code to install.
About Ellipses OS: Your Team's Claude, Running on One Set of Rules
Each person connects their own Claude to their own mail, calendar, files and task board. Every Claude reads the same company rulebook first. Scheduled runs do the reading and the drafting, a separate check traces every claim back to its source, and people make the final call.
How It Works
Four habits do the work. The kit explains each one and gives you the templates to set it up.
One rulebook, read first
Every Claude reads the same company rules before it does anything, then that person's own rules, then the task. When something goes wrong, you fix the rule once and every run picks it up.
Runs on a clock
Scheduled tasks prepare each person's day: the brief, the agendas, the debrief. Times are staggered so runs don't collide, and every run logs when it started and what it read.
A source behind every claim
Every number and every "this is done" carries where it came from and when it was read. A separate check re-reads the sources before a draft is marked ready.
People press Send
Claude drafts; people send. Each draft gets a short code, so a run can tell whether it was sent, changed first, or dropped.
What You Need
- A Claude Team plan. Enterprise works too. Scheduled tasks run on any paid plan, but the org-wide pieces need Team or Enterprise.
- Google Workspace or Microsoft 365, connected to Claude.
- A task board with a Claude connector, such as Asana.
- A meeting transcript source, if you want agendas and action items from meetings.
- One owner with an afternoon for the build and about a week to watch the first runs.
| Step | Time |
|---|---|
| Owner build | Two to four hours in one sitting |
| Each person | 30 to 45 minutes |
| Settling in | One to two weeks of small rule changes |
Get Started
- Read Start herelearn/00-start-here.md takes about ten minutes.
- Run the owner buildOpen a new Claude chat in a project, attach the kit, and paste
build/BUILD_THIS_FOR_YOUR_ORG.md. It interviews you and fills in the templates for your company. - Set up each teammateGive each person the setup paste the build makes for them.
- Check after week oneHave everyone run
build/SELF_CHECK.md.
Learn How It Works
Short chapters in plain language. Every rule in the kit exists because something went wrong without it, and the chapters say what.
The parts
The pieces and their names
The rules order
Which instruction wins
The daily rhythm
What runs when, and what each run produces
Receipts
How claims get checked
The human step
Drafts, codes, and the three ways a draft ends
One loop, one tracker
Keeping the task board honest
The company clock
Timing, time zones, and late runs
Privacy zones
Shared, private and owner
Training
Getting a team onto it
What broke and what we changed
The failures behind the rules
Team rituals
A weekly lane board, a monthly all-hands, and pilots
Publish what's proven
Keeping a reference page current on its own
Videos
Short explainers are on the way.
The system in a few minutes
Your inbox, now
Moving your team onto it
Also From Ellipses: the Live Call Co-pilot
The kit works before and after meetings. Ellipses 2.0 works during them: a co-pilot you install in your own Claude that helps while the call is happening.
Free to Use, Change and Share
The chapters, templates, prompts and skills are licensed under CC BY-SA 4.0, and the scripts under the MIT License. Use it at work, for profit, and change whatever doesn't fit.
Using it inside your company doesn't require you to publish anything. If you share a changed version outside your company, keep the credit and share it under the same license.
Based on the Ellipses OS kit by Lawrence Johnson (https://github.com/ellipses-os/kit), CC BY-SA 4.0.
Why I Built This
I built this for my own small company. We wanted Claude to keep every open loop moving without anyone's Claude sending things on its own, and we wanted to trust the numbers it put in front of us.
Getting there took a few months of rules, scheduled runs and fixes, most of them written the morning after something broke. This kit is that work with our names taken out, so you can start where we ended up instead of where we started.
Lawrence