Cucumbs demo

Cucumbs / demo / part 2 of 6: the order

One task, nine stages

Every task in Cucumbs moves through the same loop: observe, understand, decompose, delegate, compare, reconcile, synthesize, act, recurse. Only one of those stages changes anything outside the team, and it always waits for a person.

Layer 2: the order. The overview showed six boxes. Underneath them is a loop of nine stages. The rent-increase letter below is the task this tour follows down through the next layers.

Step through a sample task

Pick one of three made-up tasks and watch it move through the nine stages. Play it, pause it, or step one stage at a time. When it reaches act, it stops and waits for you.

The step-through needs JavaScript. The nine stages are described in full below, with one sample task written out.

Go deeper: why compare comes before reconcile (layer 2 to 4)

Agents answer separately first. If they compared notes too early, an agreement might only mean that one copied the other. Compare looks at the independent results side by side. Reconcile then settles only what a source can settle, and keeps the rest as an open disagreement.

The evidence page shows the same idea one claim at a time.

The nine stages

Most of the loop is about getting the picture right before anyone builds on it. Who does what is simplified from the roster on cucumbs.com.

  1. Observe

    Take in the brief and everything already on record about it: earlier notes, past decisions, limits the person has set.

    Usually: Athena, with Core for what is already on record

  2. Understand

    Say the goal back in plain words, along with the limits and what done looks like. If something is unclear, ask the person before going further.

    Usually: Athena

  3. Decompose

    Split the task into pieces that can be worked on separately and checked separately.

    Usually: Athena

  4. Delegate

    Hand each piece to the agent whose specialty fits, in a message with the shared shape. Pieces that don't depend on each other go out at the same time.

    Usually: Athena, to the specialists

  5. Compare

    Put the independent results side by side. Note where they agree, where they don't, and what hasn't been checked yet.

    Usually: Sentinel checks; Anima argues for the other option

  6. Reconcile

    Settle the disagreements that a source can settle. Keep the ones it can't, with both sides and their reasons.

    Usually: Sentinel and Halcyon

  7. Synthesize

    Combine what held up into one result the person can read: a draft, a comparison, a short recommendation.

    Usually: Athena, with Halcyon checking it fits what came before

  8. Act

    Get the action ready, then stop. The person approves it, asks for changes, or says no.

    Usually: Prepared by the team, decided by the person

  9. Recurse

    Record what happened and what is still open. If the person asked for changes, go back to the stage where the change belongs.

    Usually: Orion records it; Core keeps the names straight

Written out: answering a rent-increase letter

This is one of the sample tasks from the step-through. The person wrote: “My landlord says rent goes up in 45 days. Draft a reply. Don't send anything.”

  1. Observe. The letter, the lease and a note that the person wants to stay in the flat go on the record.
  2. Understand. The goal is a polite reply that asks about the notice period. Nothing is sent without the person.
  3. Decompose. Three pieces: what the lease says about notice, what local rules say, and how the reply should sound.
  4. Delegate. The lease reading and the rules search go to different agents at the same time.
  5. Compare. The lease has a 60-day notice clause. One forum post claims the city caps increases, and no other source says so.
  6. Reconcile. The notice clause is a FACT, read in the lease. The cap stays REPORTED and goes in the reply as a question, not a claim.
  7. Synthesize. A short reply points to the 60-day clause and asks whether the increase can start later.
  8. Act. The reply is ready to send, and it waits for the person.
  9. Recurse. Whatever the person decides, the outcome and the open question about the cap go on the record for next time.

Why it loops

The last stage feeds the first. What was learned, what was corrected and what is still open goes back on the shared record, so the next task starts from a record instead of from memory.

When the person asks for changes, the work doesn't start over. It goes back to the stage where the change belongs, usually synthesize, and comes back through the gate again.

The loop and the four steps

The hub describes four steps every message goes through: compress, transmit, reconstruct, verify. Those four happen inside each handoff. The nine stages on this page describe the task as a whole, from the brief to the record.

See what a handoff message carries