The Motion half of the demo book was two engagements, which was enough to show
that the loop works and not enough to show what the product is for. The page
that matters asks whether the motion is repeating, and a stage rail of zeroes
cannot answer it.
Eight engagements now, one at every open stage, hanging off demand deals the
demand book already creates — the pipeline happened to have exactly one open
deal at each of the eight, so no deal was invented and the quoted pipeline
counts are unchanged. Forty-four artefacts, nineteen scores, one promotion.
Three things the book is laid out to prove that a folder of templates cannot.
Every stage is occupied, and every one of the twelve starter templates is
instantiated at least once, so "stages covered 8/8" is a measurement rather
than a claim about the seed.
Scores move, and sometimes move down. Nineteen scores across eight
trajectories, with nine dimensions regressing somewhere — the Verity
fine-tuning record runs 62.5 -> 60.5 -> 84.0 -> 80.8, because a scorecard that
only ever rises is a ratchet and teaches a reader to distrust it. Every score
is computed with `motionScoreBasisPoints` and banded with `motionBand` rather
than written as a literal, so the seed and the product cannot disagree about
what the same dimensions are worth.
The artefact bodies are the customer's own facts — named people, real volumes,
the specific thing going wrong, and a live unresolved risk in each. An artefact
whose body is the template with the blanks still in it is precisely what this
data exists to disprove. Six of the forty-four have no template at all, which
is the honest shape of an engagement and the reason `kind` is carried on the
artefact rather than derived: `engagement_artifacts.kind` is NOT NULL and a
derived kind would have been null for exactly those six.
The bodies live in JSON beside the loader for the same reason the starter
library's do — forty-four markdown bodies as backtick strings is a module
nobody can review.
The promotion copies `body` from the artefact verbatim, as `promoteArtifact`
does, rather than writing a hand-authored version 2. A demo that produced a row
the real path could not have produced would teach the wrong shape of the table.
Two name collisions the authors could not see are fixed: a Quillon contact
shared a full name with a demo seller, and an Aurelian one shared a surname
with another. `usage_count` is raised once per template rather than once per
artefact, so it stays symmetrical with the decrement `clear()` already does —
verified by tearing the book down and confirming the library returns to twelve
templates with every counter back at zero, since a counter left above zero
makes a starter template permanently un-editable.
Motion was written against a base five commits behind main, so the
integration is the interesting part of this commit:
- The migration is renumbered 0014 -> 0015. Main shipped
0014_piggy_conversations, and two migrations sharing an index is a
journal that applies one of them.
- The seed-idempotency gate keeps main's all-tables diff rather than the
motion_templates counter this branch added; the general check subsumes
the specific one.
- Nav gains a Motion group alongside main's new Workspace group, and
Piggy keeps the mark main gave it.
- Stat keeps main's container-scaled figure, which already carries the
min-w-0 this branch added for the same reason.
- Piggy's page labels keep main's refusal wording for the four pages with
no tool of their own, and gain the three Motion routes.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The ledger answers which contracted capacity is sold, to whom, at what
margin. It says nothing about the motion — the repeatable practice that
turns a customer conversation into a scoped deployment, and turns that
deployment into something the next one reuses.
Motion is deliberately not a parallel entity tree. DEMAND_STAGES already
is the motion, so Motion binds reusable artefacts to the stages of a
demand deal that already exists: an engagement hangs off one deal,
cascade deleted, one per deal by unique constraint.
Nine closed kinds, each declaring which stages it serves, and a starter
library of twelve templates covering all eight open stages.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The demo seed's summary was hardcoded when the book was split into modules,
and it drifted the moment the book grew: it reported 12 demand deals and 5
capacity commitments against a database holding 13 and 6. Caught by reading
the seed's own output beside the table it had just written.
Nobody would have noticed for a while, because the numbers were close enough
to look right — which is the whole problem. That output is the only feedback
`pnpm db:demo` gives an operator, and a command that misreports what it did
teaches you to stop reading it.
Counted in SQL now, including the number of distinct stages, so the line
about the pipeline covering every stage is a measurement rather than a
promise the seed makes about itself.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Piggy answered in raw markdown, threw away every tool result it streamed,
and fought the reader's scroll on every token. The three surfaces that
made it worth having — what it read, how it reasoned, what it cost — were
all on the wire and none of them reached the screen.
The transcript is now composed of five parts under components/piggy:
answers render through streamdown, the container sticks to the bottom
without pinning the reader there, tool steps say what they read and link
to the record, and each turn carries its model and token count. Three
lifecycle bugs went with them: Stop left a permanent spinner, a truncated
stream was indistinguishable from thinking, and a failed send destroyed
the message it failed to send.
Underneath, the inference path grew timeouts, jittered retries on 429 and
5xx, tolerance of the malformed frames a 30B model emits, and an
agent_runs row per turn so chat spend is observable. The system prompt now
states that a field ending in Cents is cents — without it nemotron renders
costPerGpuHourCents: 189 as "$189 per GPU-hour", which is a 100x error on
the most scrutinised number in the room.
The demo book was arithmetically incoherent: every deal's value
contradicted its own allocation revenue by up to 3.6x, nothing had ever
closed, no customer had any paper, and the marketplace was empty. Deal
value is now derived from the allocation, the book clears 5.3% across five
blocks with one deliberately underwater, and the renewal, compliance and
agent-provenance machinery finally has rows to act on. A --clear that
deleted every obligation, SLA term and capacity request in the database
regardless of origin is scoped to the demo's own ids.
Around that: accounts have a detail page, ⌘K searches the book, Settings
can mint the API keys it always claimed to, and deploy.sh actually ships
the agent instead of silently skipping its compose profile.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
karti
claude