Descriptor

A descriptor is the datasheet for one named synth. It is public to the systems that are allowed to talk to her. It is not a resume and it is not a prompt.

Schema:synth.schema.json.

Required fields

Field	Meaning
`id`	Stable identifier. Never recycled.
`name`	The name you use when you talk to her.
`class`	`architect`, `analyst`, `scientist`, or `operator`.
`mission`	One sentence. What she owns.
`read`	Surfaces she may read.
`write`	Surfaces she may write. Empty means she writes nothing.
`escalate`	Who gets the thing she must not decide.
`kill`	Stop conditions. Invent, send, wander are typical.

Optional fields

Field	Meaning
`pronouns`	If you need them in a UI.
`hone`	How the starting class narrows on a real desk. Not extra products.
`mouth`	How work arrives. Default for commercial ops is inbound file or email.
`access`	`house`, `client`, or `airgap`.
`tools`	MCP tool names she actually has. Keep the list small.
`presence`	URL or MCP resource for desk state.

Rules

A synth shall have one mission family. If you need a second family, that is a second synth.
A synth shall not declare a write she cannot perform. Omit it.
A synth shall not send to a customer unless write names an explicit send channel and kill does not forbid send.
kill is not poetry. Each item is a stop condition a runtime can enforce.
Model names, agent frameworks, and prompt text shall not appear in the descriptor.