A Picture on the Row It Explains

A note on a board row, eleven lines long, three of them boxes drawn with plus signs and bars.

Nobody had checked the boxes since the day they were typed.

That is how pictures lived here. A plan was a row, and a row had notes, and when a plan needed a shape someone typed the shape by hand. The corners never met twice the same way. When the plan changed, the words changed and the boxes did not.

On a morning in September one line arrived. Add the drawing tool to the command line.

The tool already existed. A person far away had written a small editor that draws in the terminal, with a mouse, in plain characters, and had given it away. It ran on a different engine from the command line. So it was not taken in. It was called, the way a neighbour is called over the fence, and it kept its own house.

The want was not the drawing. The want was the picture sitting on the row it explained, in the row's own thread, where the next reader would already be looking.

The thread keeps four thousand bytes. A picture larger than that has two honest answers and one dishonest one. It can go whole. It can be refused whole, with both numbers named. Or it can be cut at the edge and reported as sent. The third answer is the one this board has been burned by before.

The first picture went up. The check that guarded it said it had been cut. Four hundred and eighty-three bytes sent, four hundred and eighty-two kept.

Nothing had been lost. The door trims a newline before it counts. The measurement had lied before the thing it measured did.

Then the door went quiet upstream, and a post that never landed came back reading ok, because one small word inside the answer had overwritten a larger one outside it.

The drawing had taken minutes. The receipt took the morning.

Now the door's own count decides what was kept, and a failure says whether it landed.

A picture on the row, eleven lines long, and every byte of it where it was sent.

Where the metaphor stops being true

• "Called, the way a neighbour is called" — the editor is spawned as a child process by packages/cli/src/draw.ts (resolveRunner): lazydraw on PATH, else bun x lazydraw@0.1.1. It is not a dependency of @oneie/cli, whose runtime deps stay commander + @oneie/sdk.
• "The door trims a newline before it counts" — resolvers/tasks.ts: bodyRaw.trim() then commentByteLen. draw.ts therefore reads submittedBytes/storedBytes/truncated from the response and never compares against its own byte count.
• "One small word overwrote a larger one" — { ok: false, ...inner } let an inner body's ok replace the failed outcome. Fixed to { ...inner, ok: false }. The same spread shape exists in packages/cli/src/media.ts unwrap(); there it is guarded by 'ok' in inner, but it was not audited here.
• Locked words used: group (the one group), people and agents, signal (the knock), the board's rows are Things. No dead names.
• NOT WIRED: no agent prompt names one draw; an attach marks no path; nothing counts attaches.

The family this story generates

Sentences that would be false if shipped

• "Agents attach their diagrams to the rows they file." — no agent prompt or skill names one draw yet.
• "Attaches are counted." — nothing counts them.
• "one draw works anywhere one works." — it needs Bun ≥ 1.3; without it the verb refuses on one line.
• "Diagrams of any size go on the board." — the thread keeps 4000 bytes; larger ones are refused whole.

The story shape — the chain, and the three rules

The fourteen parts walk one chain, from what is wanted to what was learned:

goal       states the Want plainly
  │
story      tells the seven beats
  │
plan       sets the path from the story to the work
  │
tasks      the rows /do executes, tagged on the board
  │
promise    what was agreed, its accepts frozen
  │
stakes     what changes if it is kept or missed
  │
events     signals — each one marks or warns a route
  │
proof      the &&-join of the accepts, run as written
  │
payment    money moves only where a person consents
  │
learning   a path or a status changes, so the next
           pick is not the last one

Three rules hold for every lifecycle, for people and for agents:

1. Promises at every touchpoint. Each stage where a person or an agent meets ONE carries one promise with one checkable proof (promise, check).
2. Agents help people move forward. Each stage names the agent that helps the person reach the next stage (helper).
3. Agents hand tasks to people. Where judgment, consent, a signature or money belongs to a person, the agent hands them the task — a human workflow step, or the task reassigned — and says what it hands over (hands_over).