Claude Code First, specification version 0.1.0. The plain-language guide

Version 0.1.0. Grade R3/S4.

F406 Projects that ship a surface to other agents put a counted ceiling on what it costs the consuming agent, held by a test

FieldValue
Statusactive
TopicEnvironment, permissions, and agent-facing products
GradeR3/S4
CasesShio, roadkeep, freewilly, winwright
Contrarynone
Harness factsH3, H9

Claim

Each project that ships tools, a skill or a command surface for other agents measured what that surface costs a consuming agent (tool schema, skill text, responses) and held it under a declared ceiling that a test or lint enforces, and in Shio that check fired and the change was reshaped rather than the ceiling raised.

Mechanism

A tool schema or a skill description is paid by every session of every consumer, whether or not it is used, and it grows one reasonable sentence at a time. A ceiling stated in a file a test reads turns growth into a failure the author has to answer: trim, split, or raise the number with a reason. The projects priced the two costs apart: what loads before any work (tool lists, skill descriptions) and what loads on use (skill bodies, H3; command responses).

Observations

Independence

Four origins. Shio's SH132 is the earliest and is its own. roadkeep's ceilings are its own lint and tests, recorded against its own growth. freewilly borrowed the argument from Shio, as its decision record says, but built its own budget file and changed it in response to its own failures: a band in which a "response that grew by 100 tokens landed inside it silently" [freewilly@c1c2eaf:agent-budget.json#L109] (DD78), and a gate red for the wrong reason (DD64, [freewilly@ecaad33]), so it counts as a second origin under the copy rule. winwright's skill test (WW69, 2026-08-26) predates roadkeep's skill split (RK1437, 2026-08-31) and is its own.

Counter-evidence

H9 weakens the shared premise for tool schemas: with tool search on, which the documentation read on 2026-09-24 calls the default, Claude Code does not send every tool definition up front, so the cost Shio and freewilly describe as re-sent on every turn may now be smaller than their figures. Their measurements count the serialized schema, not what reached a model's context. The gates also cost something: freewilly's budget gate went red for the wrong reason, "the budget gate that can go red for the wrong reason" [freewilly@f514e11], and needed deterministic inputs before it could be trusted. polyweave's surface has no such ceiling at the pin; its filed task on it is outside the pin.

Grade

R3: four independent origins in four projects; polyweave has none, so R4 is not reached. S4: Shio's ledger records its tool-list ceiling being exceeded by a change on two occasions, and the change was reshaped to pass, which is a check that encodes the finding seen to fire. The other three projects reach S3 with counted figures.