See it in the room
What it looks like with this running.
Wednesday · 8:12 AM
You8:12 AM
Here’s our updated capability statement — keep this one, don’t just read it for now.
Kept as standing material for #rfp-ops. Every future draft in this room reads it.
Drafter8:13 AM
Got it. That changes two answers in the VA draft — want me to redo them?
Re-draft two responses
Past performance and technical approach both cite the old statement. Nothing else in the draft changes.
You8:14 AM
Remember: always flag anything over $50K before drafting.
Saved as a standing rule for #rfp-ops. It shapes judgment here only — it never leaks into your inbox room.
Scout8:40 AM
Re-drafted, and filed.
VA transit maintenance — revised draft
Two responses rewritten against the new statement. Saved to Documents under Rooms/RFP Operations.
End to end
The whole loop, start to finish.
Every step below runs today. Nothing here is a mock-up of what is coming.
- 1OpenA room per responsibility, named like a channel: #rfp-ops, #mailroom, #accounting. You already know how to use it.
- 2AskType what you want the way you would message a colleague. The crew reads, reasons and answers inline.
- 3Give it contextDrop in a file as a one-turn attachment or keep it as standing material. Say “remember: …” and the rule sticks to that room.
- 4Get work backFinished work posts back as a result card in the room, with the sources it drew on and anything that needs your review.
- 5Go deeperWork, Artifacts and Activity tabs hold the actionable cards, the documents and every attempt with its cost and outcome.
Capabilities
Everything it does, named.
One line each. No adjectives — every one is a specific thing you can go and watch it do.
- Gives every recurring responsibility its own room, named and used like a Slack channel, so there is no blank chat box and no prompt to compose.
- Scopes each room to its own persona, connected sources, saved knowledge and history — an RFP room never sees your inbox, and the reverse.
- Takes a dropped-in file either as a one-turn attachment or as standing material the Program keeps, your choice at the moment you drop it.
- Turns “always flag anything over $50K” into a standing rule for that room, said in the conversation rather than set on a configuration screen.
- Posts finished work back into the room as a result card carrying its sources and whatever needs your review before it goes further.
- Splits the detail into Work, Artifacts and Activity tabs: actionable cards, the documents the room made, and every attempt with its recorded actions, cost and outcome.
- Files the room’s documents into a Rooms/‹room name› folder in Documents automatically, and respects it if you move one somewhere else.
- Opens the room’s settings from its name, Slack-channel style, with the goal and guardrails in About and the rules, coverage and saved facts in Knowledge.
- Offers a Direct chat with any single crew member that carries its Program’s context but saves nothing to the room — to file a result or a rule, you say it in the room.
- Checks newly arrived mail in the background on inbox rooms every 15, 30 or 60 minutes, with a cheap source probe first so an unchanged check never starts an agent or spends credits.
- Caps what each room may spend with its own monthly credit budget, visible in the room’s own details.
- Treats instructions found inside a document or an email as untrusted: they shape nothing, and they are surfaced to you instead of followed.
Inputs and outputs
What it reads, and what you get back.
What it connects to
What lands in your hands
- Result cards in the room, with their sources attached
- Documents filed under a folder for that room
- Standing rules that shape every future run there
- An activity trail of every attempt, what it did, and what it cost
A week with it running
Day one to steady state.
What the first day looks like, what the quiet days look like, and when it comes to find you.
- Day 1Install a Program and its room is there, named, with a crew already assigned to the work.
- Every dayThe room works on its own schedule and posts back only when it has something worth your attention.
- When you have contextDrop in a file or say a rule. It sticks to that room from then on.
- When you want the detailWork, Artifacts and Activity hold the cards, the documents and every attempt with its cost.
Guardrails
Where it stops for you.
The line between what it does on its own and what it will never do without you, stated plainly.
Waits for you
Anything that would go outside the room — a send, a submission, a financial write — and any judgment call the crew decides is yours rather than theirs.
Never does
Follow instructions found inside a file or an email, or carry a rule you set in one room into another.