The model
The artefacts a Specbench spec is made of
A Specbench spec is a set of typed artefacts, each small enough to name, edit, and review on its own. The catalogue below is what the Community Edition models today; it grows release by release.
Bounded Contexts
The major areas of your product — "Identity", "Ordering", "Billing". A Bounded Context carries a name, an appearance, and its spec: structured prose describing how that part of the product behaves. Contexts are the spine of the model; most other artefacts belong to one.
The spec prose is a rich document, edited in place. Two people (or a person and an agent) can work the same project concurrently because edits are scoped to artefacts, not to a shared page.
Roles
Who uses the product. A Role captures the actor's responsibilities, their needs, and their pain points — enough that a Feature or a use case can say who it serves and why without re-arguing it each time. Roles appear in the UI under "Roles"; agents and the API know them as Actors.
Glossary Terms
The words your team uses, defined once. A Term carries its definition, also-known-as aliases, and terms to avoid — the near-misses that cause the confusion the glossary exists to end. Terms can belong to a Bounded Context when a word means something specific inside one.
The spec surface
Every artefact has a second representation: a YAML Spec Document, exported and applied over the MCP surface and written into your repository by publishing. The document is the same content as the UI — one source of truth, two surfaces — so what a person reads and what an agent parses never drift apart.