Briefs

A brief is background an agent should read your data with: your sales methodology, your brand voice, a glossary, a policy line. Entities answer what is this thing; a brief answers how should it be read. Write it once and every agent whose domain carries it gets the same framing.

Briefs live in Build → Briefs: a card grid or list, filtered by domain and type, with + for a new one. Search covers the body text, not just names.

How it works

A brief has two markdown boxes.

Box	Holds	Example
Content	Definitions, criteria, emphasis, voice	”A qualified opportunity has a named champion and an agreed evaluation plan. On renewals, weigh change in MRR over first-year ARR.”
Restrictions and Escalation	When to decline, when to escalate, what never to say	”Never quote discount authority figures; route pricing exceptions to Deal Desk.”

Restrictions stay in their own box so a reviewer can read the limits without hunting.

A brief opens ready to type. One Preview / Markdown control moves both boxes: switch to Preview to read it rendered, and Preview stays selected next time. Clear empties both, behind a confirmation.

A setting caps the two boxes’ combined size, and a count sits above them. A document long enough to need searching belongs in retrieval, not here.

Write one

Open a brief for three tabs — Content, Meaning and Domains — with Preview, Versions, Activate and Save in the header. Identity (name, type, description) sits behind the settings cog.

Meaning holds the synonyms: other names your people use for this material. The catalog advertises them, so an agent finds the brief by vocabulary, not by API name. They reach agents at activation, not at save.

Copy duplicates a brief as a draft, in no domain and not activated.

Types

business · brand · glossary · policy by default. The type is a hint for agents and a filter for you; it changes no behavior.

Extend the list at Admin → Settings → Behavior → Brief types, or pick + New type… in a brief’s type field; both write the same setting. Removing a type leaves existing briefs alone, but they won’t re-validate until you give them a current type.

Publish it

A brief serves from its activated version only. Save writes the draft, and nobody receives a draft. → Versions

Choose who receives it

Domains decide who gets a brief, exactly as they do for entities. A brief in no domain reaches nobody. Add it from the brief’s Domains tab or from a domain’s Briefs tab; either one does it. → Domain access

• “Everyone” is the default domain. Voice, glossary and methodology briefs usually belong here.
• A narrower audience is a narrower domain. Who holds the domain is who reads the brief.
• Customer safe is a separate switch: a domain marked Customer facing serves only briefs marked customer safe.

Choose how surely it arrives

Pick a delivery tier each time you add a brief to a domain.

Tier	The body arrives	Guarantee
Offered	on request, through Get Briefs	present if the agent asks
In catalog	in the catalog response, in full	present once per discovery call
Auto-inject	with every payload the domain serves	cannot be missed

In catalog suits material an agent should simply know — a glossary, a voice. Auto-inject alone re-states the framing on every call, so use it where a rule has to hold each time. A glossary read at the first turn can be gone by the thirtieth.

Injected briefs arrive in the order you set by dragging them on the domain page.

Notes

• Agents see briefs in the catalog index — name, type, one line — and fetch full text with Get Briefs.
• Get Briefs returns a version stamp. Echo it back and an unchanged set returns unchanged instead of the bodies. The stamp includes the fiscal period, so a quarter rollover always refreshes.
• A brief is what a person knows. What the platform knows — the fiscal calendar, the currencies, the org chart — is Info, computed rather than written.

What’s next

• Skills — packaged procedures, same page and same publishing model
• The admin agent — hand it a methodology deck and review what it drafts