loom/cart

T

jeffryandClaude Opus 5 0e827851ec the cart agreement, v0

Published to give the document an address.

The README states what the agreement depends on (annotating/v0), the four roles
it leaves to adopters, and the one among them that is not a preference — when one
party cannot feel a cost, the decision belongs to the party who can, and an agent
will not feel a cart filling.

Also states what is known and unresolved: an out-of-scope need has no exit.
Conversion emits the artifact and the declines, and a thing that came up, was
correctly out of scope, and was neither refused nor decided is neither of those,
so today "out of scope" means "lost". Proposed as a third exit, not adopted, and
loom's to make.

This is the copy adopted by staribridge/substrate on 2026-08-21 and reconciled to
v0 the same day, read many times and never edited. If loom's own copy differs,
this one is wrong.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-07 10:53:44 -04:00

.loom/published

the cart agreement, v0

2026-09-07 10:53:44 -04:00

README.md

the cart agreement, v0

2026-09-07 10:53:44 -04:00

README.md

cart

How two parties work out what something means before one of them changes it — including when neither of them knows.

The agreement — v0

A cart is one bounded exchange. It starts, it runs, it converts, and then it is gone. The directory is only where a cart happens.

What it depends on

annotating/v0. Dailies are annotated, and everything here rests on that.

Four roles it leaves to you

An agreement adopted with these uncast has not been adopted. It has been filed.

Where a cart lives
What durable record declines go into
What isolates work in progress while a cart is open
Who decides when the round ends — and this one is not a preference. When one party cannot feel a cost, the decision belongs to the party who can. An agent will not feel a cart filling and will keep writing until told to stop.

The agreement asks these as prompts. Answer them where you adopt it, not here.

Known and unresolved

An out-of-scope need has no exit. Conversion emits the artifact and the declines — and a thing that came up, was correctly out of scope, and was neither refused nor decided is neither of those. Today "out of scope" means "lost."

Proposed as a third exit and not yet adopted; it is loom's to make. Recorded in bedrock's event log, cart almanac.

Provenance of this copy

Adopted by staribridge/substrate on 2026-08-21 and reconciled to v0 the same day. Read many times, never edited. If loom's own copy differs, this one is wrong and should be replaced before anybody adopts it.