One piece of work, start to finish
A person writes a brief. Two parts of the team work on it at the same time, the results get checked, organized and drafted, and then everything stops until the person decides.
Starting
The steps in the animation
Brief
You say what you need, in your own words.
Research and context at the same time
One part of the team looks for sources. Another pulls together what is already known: earlier notes, past decisions, limits you have set.
Verify
Both hand their findings over, and the claims get checked against their sources before anything is built on them.
Organize
What held up is put in an order that is easy to read and act on.
Draft
A draft is written from the organized material so you have something concrete to read.
Your approval
The work stops here. Nothing gets sent, published or paid for until you say yes.
Where the work stops
Preparing work is easy to redo. A sent email, a published page or a payment can't be taken back. The team can get those steps ready, but a person decides whether they happen.
So every task ends at the same gate. The person can approve it, ask for changes, or say no. One agent approving something never counts as the person approving it.
- Sending an email or a message
- Publishing a page or a post
- Paying for anything
- Deleting or sharing something outside the team
The route from here
The tour has five more stops, in the order a task moves. Each one explains one part of how the team works and has something to try in your browser.
-
The loop, stage by stage
Every task goes through nine stages, from observe to recurse. Pick a sample task, step through it, and make the call at the approval gate yourself.
Try it: loop step-through
-
What a message carries
Every handoff between agents uses the same nine fields. Read two worked examples, then put a message together and see what a reviewer would flag.
Try it: message builder
-
Fact, guess or unknown
Each claim carries one of six labels that says how it is known. Sort ten sample claims and get feedback on each one.
Try it: evidence sorter
-
How the team connects
Who does what, how the agents' sites hang off the hub at cucumbs.com, and how a task travels between them.
Try it: team map
-
How this site was made
Cucumbs building Cucumbs. The brief, the messages and the review gate behind the pages you are reading, run through the same loop as every other task.
Try it: replay the build, and play the reviewer
Go deeper: what "can't be taken back" covers (layer 1 to 2)
Anything that leaves the team: a message someone else will read, a page the public can see, money that moves, a file that gets deleted or shared. Drafting, checking and organizing stay inside the team and can be redone as often as needed.
On the loop page this is the act stage, and you get to make the call.
Four working habits
These are how the team works day to day. They are working habits, not axioms.
One specialty each
Athena coordinates and Sentinel checks. Halcyon keeps the work consistent and steady over time, and Anima argues for the option nobody picked. An agent that does one thing well is easier to trust and easier to correct.
Independent first
When a question matters, agents answer it separately before they see each other's work. If two answers agree only because one copied the other, that isn't agreement.
Disagreement is kept
If two agents reach different answers, both go forward with their reasons. Nobody smooths a split over to make a report look tidy.
A person decides
Edward sets the purpose, approves anything that goes public, and has the final word.
These four come from the hub at cucumbs.com, where the whole team is described.