Vibeleaderboard
← Course overviewModule 09 · Coordinate several pieces of work · Beta
Lesson 9.3

Module contents

Coordinate several pieces of work

Lesson 3 of 5

What has to cross each seam of the map?

The map has seams: between each worker's part and the reconciled table, and between the table and the recommendation. Something crosses each seam, and what crosses decides whether the next step can check what it received or has to take it on trust. This lesson names the person or agent who sits at the seams, says what the shared information is and where it lives, and traces in detail what is lost when a worker sends back a conclusion instead of the evidence behind it.

Numbered links identify sources. Underlined terms offer a definition without leaving the lesson.

Shared information lives where every worker can find it

Before the workers start, three things have to be true of what they share. Every worker needs the same rubric, the same supplier list and the same constraints, so those live in files in the shared folder, named in every assignment, and no worker is told them in a message that another worker never sees. Module 4's information plan said this for one session: put each thing the task needs where it will be found. With several workers the rule matters more, because a fact given to one worker and not another produces returns that disagree for no visible reason.

The second thing is that shared does not mean everything. F-Greenway does not need Marlow's pages in its context, and giving them to it invites the overlap the scope line was written to prevent. What is shared is what every part depends on, which the dependency map shows: the given inputs at the top.

The third thing is that someone owns the seams. This course calls that person or agent the : the one who writes the assignments, receives the returns, checks them against the map, resolves disagreements between them, and either writes the integrated result or assigns it. In the supplier case the treasurer is the coordinator and assignment R is the coordinator's own work. A coordinator can be an agent session, and often is. A single coordinator is a design choice, not a necessity: the seams can instead be owned by rules every worker follows, such as a merge rule that says how returns are combined and a review rule that says who checks what before anything is combined, and Anthropic's compiler project described in the next lesson ran without any orchestrating agent, on shared rules and a shared repository. What no design can do without is ownership of the seams. Work with several workers and neither a coordinator nor rules has returns that nobody reconciles, and the recommendation is written from whichever return was read last.

A handoff is the return plus what the next step needs to check it

Module 4 described several ways work crosses from one context to another: a handoff summary written for the next context, a session resumed from its saved record, and context the next step retrieves for itself from files. All three are in play here, and this lesson is about the first, in the form the supplier assignments chose: a return file plus saved pages. An is a worker's return written so that the coordinator can check it without redoing the work. This course sets four parts for it, as an authored design rather than a rule taken from any product: the identity of each source, meaning which page or file and when it was read; the relevant rows or passages, quoted, not paraphrased; the worker's uncertainty, meaning what it could not find, what it found in two versions, and what it decided; and the artifact itself, meaning the saved page or file, in the shared folder, so that the coordinator can open it.

The reason for each part is a question the coordinator will otherwise have to ask. Without the source identity: where did this come from? Without the passage: does the source actually say this? Without the uncertainty: is this a fact or the worker's best guess? Without the artifact: can I see the passage in its surroundings? The last matters because a quoted passage can be accurate and still misleading on its own; Fernbank's "trade accounts available on application" read differently once the rest of the page shows it is addressed to nurseries buying wholesale. The saved page is kept so that the conditions around a passage can be read, not only the passage.

A worker's session may also be resumable from its saved record, and a coordinator who can reopen it can ask a question the return did not answer. That is a second route, and it depends on the harness keeping the session and on the coordinator having access to it. The return file is the route that does not depend on either, which is why the assignments make it the one that must exist.

What a short conclusion loses

Suppose E-all had returned this instead of the eligibility file the assignment asked for:

Eligibility checked. Marlow is not eligible. Greenway and Fernbank are eligible.

Trace what the coordinator can do with it. The coordinator can accept it, in which case the recommendation rests on a sentence whose basis nobody has seen, and module 8's rule about completion messages applies: it is a claim, consistent with the work and unsupported by it. The coordinator can redo the check, which costs the time the delegation was meant to save. Or the coordinator can go back and ask: reopen the worker's session if it was kept and is reachable, or start a new one, which has to retrieve the pages again.

Now list what the sentence does not say. Which constraint did Marlow fail? Both are hard constraints, and the committee will ask. What did the page say, in its own words? "Card payment at time of order" and "we are unable to offer credit accounts to new customers" are different findings; the second might be negotiable. Is "eligible" a finding or an absence, meaning the worker found a passage that says invoice payment is accepted, or found nothing that says it is not? Module 1's distinction between supported and not disproven is exactly this. When was the page read, and which page? The evidence-bearing version of the same return answers all of it:

Marlow Plant Supply
  delivers to the area:   met.  delivery page, saved pages/eligibility/marlow-delivery.html,
                          read 2026-10-06: "We deliver to all mainland addresses."
  invoice payment, 30d:   not met.  terms page, saved .../marlow-terms.html:
                          "Payment is taken by card at the time of order. We do
                          not offer account terms."
  uncertainty:            none on these two; the page does not mention
                          community groups specifically
Greenway Seeds Ltd
  delivers to the area:   met.  delivery page, saved .../greenway-delivery.html:
                          "We deliver to all mainland addresses."
  invoice payment, 30d:   met.  terms page, saved .../greenway-terms.html:
                          "Schools, charities and community groups may pay
                          by invoice within 30 days."
Fernbank Nurseries
  delivers to the area:   met.  delivery page, saved .../fernbank-delivery.html: [passage]
  invoice payment, 30d:   unknown.  terms page, saved .../fernbank-terms.html, says
                          "trade accounts available on application" in a section
                          addressed to wholesale buyers, and nothing about invoice
                          terms for groups; not asked

The two returns reach the same verdict on Marlow and different verdicts on Fernbank, and the difference is the point. The short return said eligible; the full return says unknown, and says why, and the recommendation the committee reads will say that Fernbank's invoice terms need a phone call before an order. A conclusion without its rows does not merely lose detail. It can be wrong in a way that its form conceals.

A summary can be designed with the next step in mind, and the assignments did exactly that: the evidence line tells the worker what the coordinator will need. What no worker can anticipate is every question, which is why the artifact travels with the summary. The site's Intel section carries a September 2026 post from Spotify's engineering blog about routing parts of a coding agent's work to sub-agents on cheaper models, which return summary text; the site's entry records that the summaries lost information the main session then lacked, and that the delegation added waiting time. 4 That is one company's report about its own code tooling, cited through the site's summary; the shape of the loss is the one traced above.

Carry this forward

  • Shared inputs live in files every worker is pointed at; what is shared is what every part depends on, not everything. A coordinator owns the seams: writes assignments, receives returns, checks and reconciles them, and integrates or assigns the integration.
  • An evidence-bearing handoff carries source identity, quoted passages, the worker's uncertainty and the artifact itself, so the coordinator can check it without redoing it. A quoted passage can mislead without its surroundings, which is why the saved page travels too.
  • A conclusion without its rows can only be accepted, redone or asked about. It hides which constraint failed, what the page said, whether a verdict is a finding or an absence, and when it was read, and it can be wrong in a way its form conceals.
  • A summary can be designed for the next step, and the assignment's evidence line does that. It cannot anticipate every question, so the artifact stays available, and a resumable session is a second route when the harness keeps one.

Lesson check

Three returns arrive for Fernbank's invoice terms. Which one can the coordinator use without going back to the worker, and why?

Choose an answer for each question.

This is a practice check. Answers reset when you leave this page. Results are not saved and do not place you in another module or award a qualification.

So far each worker has written only its own files. The next lesson lets two of them write to the same one, watches what happens, and separates isolation from integration.

Sources · Reviewed 2026-09-29
  1. 4. VibeLeaderboard Intel: Spotify engineering (September 2026), Spotify's Backstage Portal cut my Claude Code token usage by 90%

Sources support nearby explanations. Product details can change. Scenarios and model results are authored illustrations unless a lesson explicitly identifies a recorded execution. Module 7 identifies its offline code checks.