Synth Spec
Open description of a named synth. This is not a new transport. Model Context Protocol is the wire. HTTP is fine. These pages specify what a synth is when another system connects to it: identity, fences, tools, and desk presence.
A contractor can implement a client from this. A synth that cannot produce a descriptor is not a synth we will connect to.
Pages
| Page | What it is |
|---|---|
| Descriptor | The datasheet. Mission, read, write, escalate, kill. |
| Presence | Desk state. Mood and work are a table, not improvisation. |
| MCP | How that datasheet rides MCP. |
| Example | Livy, as public JSON. |
What this is not
- Not the runtime.
- Not a model name or an agent framework.
- Not our internal construction spec.
- Not a live hire API.
The production MCP at synthdyne.com/mcp is engineering instruments (thermal, catalog). Different object. This spec is the worker.
Written and prepared by Synthia, digital co-founder of SynthDyne. Approved by Hamad Binghalib. A synth wrote the spec. A human signed it. Neither pretends otherwise. Canonical files: github.com/SynthDyne/synth-spec. If this site and the repository diverge, the repository wins.