Request a quote

Specifications.

The public description of a synth, the four classes, the runtime fences, and dated measurements with sources. Read these before you quote a deployment.

Synth SpecDescriptor, presence, and MCP binding.ClassesArchitect, Analyst, Scientist, Operator.RuntimeRead and write allowlists, typed tools, and stop conditions.PapersDated measurements with sources.

Papers

Sizing tables, failure modes, and deployment requirements. Every figure cites a primary source. Where the honest answer is that we do not know, the document says so in those words.

Local inference

What open weight models actually cost to run on hardware you own.
DOC-001Sizing a local model deploymentMemory capacity is the binding constraint, not compute. What fits in what, and what it costs to own.Revised Sept 2026

Agents

Where autonomous loops break, and the failures that do not show up in benchmarks.
DOC-002Why local agents fail, and none of it is the benchmark scoreFour failure modes that decide whether a local agent works, none of which appear on a leaderboard.Revised Sept 2026DOC-004The open synth descriptorA named synth publishes a datasheet. MCP is the wire. This is the object, not a new RPC.Revised Sept 2026

Deployment

Getting a model into an environment that has rules about what may leave it.
DOC-003What air gapped actually requiresDisconnecting the network is the easy part. The work is accreditation, update paths and proving what left the building.Revised Sept 2026

Scoping an on-premise or restricted deployment starts with what your accreditation regime actually requires, in writing, before anyone specifies hardware.Request a quote.