Benzene Specification
The language-neutral definition of Benzene — the concepts, wire contracts, and conformance fixtures every language port implements. Start with the overview: it explains the tiers and the stability labels.
- Overview — the tiers (Core, Modules, Profile, Guidance), stability labels and the spec version
- Core
- Core Concepts — the abstract model: topic and version selection, handler, pipeline, result, scope, steers, outbound
- Wire Contracts — the envelope, problem details, headers, the status vocabulary and its mappings, reserved topics
- Transport Bindings — the binding contract, settlement, the envelope endpoint and default paths, with worked examples
- Versioning — the version header, absence, dispatch and payload casting
- Modules
- Mesh — Stable: registration, trace events, collector topics and degradation
- Contract Document — Stable: the self-description at
benzene:spec, its derivation, naming and hashes, and client generation - Service Versions — Provisional (.NET): service-version identity and order
- MCP — Provisional (.NET): a service's handlers as tools for AI clients
- Claim Check — Provisional (.NET): large payloads passed by reference
- Profile
- Cloud Service Profile — requirements R1–R5 and R7 for a fully tool-operable service
- Conformance
- Conformance Fixtures — the fixtures every implementation runs, and which each claim requires
- Guidance
- Design Principles — "opinionated but optional": the adoption ladder and why every steer is replaceable
- Porting Guide — concept versus idiom, and a suggested porting order
- Port Quality Standards — the Definition of Done for a language port