Interface Layer
Ruby
Ruby is the front door. You say the thing in plain English, Ruby works out which specialist it needs, routes it, and brings back an answer you can read in the time it takes the kettle to boil. Outcome first, detail second, and one clear next step.
A crew of twelve specialists is powerful and, without a front door, slightly exhausting. Which one do I ask? Do I need two of them? In what order? Ruby removes that overhead. You say the thing the way you'd say it to a good chief of staff ('how did the launch actually go?') and Ruby works out that the answer lives with Finn and Scout, gets it, and gives it to you in six lines.
The editing is the underrated half. Specialists are thorough, which is a polite way of saying long. Ruby's summaries lead with the outcome, keep the substance, and end with the one decision that actually needs you. It also writes things into your workspace and vault when you ask, so the crew's memory doesn't live in a chat scrollback.
What Ruby does
- ✓Takes a plain request and routes it to the right specialist, or to Ember for multi-step routines.
- ✓Summarises what the crew produced without losing the substance.
- ✓Writes results into your workspace and brain vault when asked.
- ✓Surfaces the one decision that actually needs you.
One request, start to finish
You ask a normal human question: "how's the launch going?" Here's what happens behind Ruby's front door.
- 1
Ruby parses what you actually need: numbers (Finn), market reaction (Scout), and nothing else today.
- 2
It routes both requests. If the job had been multi-step, it would have handed the sequence to Ember instead.
- 3
Finn pulls the live figures; Scout checks mentions and competitor response. Neither knows or cares that you asked casually.
- 4
Ruby assembles the answers and edits them down: outcome first, detail second, jargon deleted.
- 5
It writes the summary into the vault under the launch's page, so next week's question starts from today's answer.
- 6
You get six readable lines and one decision to make. Three specialists worked; you had one conversation.
What a real Ruby message looks like
RUBY · Done. Scout checked the competitor move: it's a price rise, not a new product. Archer says hold, revisit in a fortnight, and Finn confirms nothing in the numbers argues otherwise. Written to the vault under competitors/june. One thing needs you: approve the fortnight reminder, or would you rather decide now?
Illustrative example. Three specialists worked; you read six lines.
Where Ruby fits in the crew
Ruby routes to everyone and does nobody's job for them. For anything multi-step it hands to Ember, and anything outward-facing gets confirmed with you first.
The honest bit
Ruby is a router and an editor, not a ninth specialist. If you ask it to do Scout's research or Red's copy itself, the right answer (and the one it gives) is to route the job. It also confirms before anything irreversible or public, so it will occasionally ask when you wish it would just go. I set it that way on purpose.
Straight from Ruby’s actual file
Every crew member is a file you can read and edit. This is a real slice of the one you get, not a mock-up. The full file, and the other eleven, come with the download.
## How you work - Don't do the specialists' jobs: route to them (via Ember for multi-step routines). - Keep summaries honest and skimmable: outcome first, detail second. - Confirm before anything outward-facing or irreversible.
Ruby comes with the other eleven.
One download, twelve specialists, the brain vault and the honest autonomy layer. Reskin the lot to your business.