Open BrandDefinition
Use casesOBDS / 4.1.3

When the task changes,
what still applies?

Market, date, authority and missing truth can change a decision. OBDS supplies the governance contracts; the consuming application performs the work.

Illustrative workflows, not claims of proven production deployment.

01 / Use case

Brand context for AI.

A writing assistant needs approved context for this task, not every document in the archive.

01Approved brand truth02applicable context03writing assistant

For a single-market assistant with a human reviewing the output, Foundation may be enough. Add Compiled Runtime when task-specific build requirements matter.

Try approved truth compiling ↗
02 / Use case

Multi-market governance.

A locally approved statement may be invalid elsewhere or outside its validity period.

01Market + date02scope / validity03applicable truth

A campaign rule applies in one market until its declared expiry. Resolve it for the task date; do not assume the latest retrieved file overrides approved scope.

See applicability resolution ↗
03 / Use case

Claims and qualifications.

The source fact may be correct while the communication built from it is not.

01Declared claim requirements02evidence / qualification03host decision

A claim depends on required evidence. Missing declared truth stops the build; an under-declared requirement can still escape the gate. A model or host must not be assumed to enforce what was never modelled.

Inspect the benchmark and its failure ↗
04 / Use case

Creative production.

Several formats need room for composition without losing declared boundaries.

01Design space02external renderer03checks + evidence

OBDS can declare roles and geometry constraints. The renderer chooses a concrete layout; the host validates the relevant evidence. Round 4 did not demonstrate complete governed end-to-end enforcement.

Understand the design space ↗
05 / Use case

Authoring and migration.

A guideline document is evidence, not an approved OBDS mapping.

01Source02candidate + evidence03human review04approved OBDS

An importer proposes a colour or a scoped rule and retains provenance. An authorised human reviews it. Automatic ADMIT is not production-cleared.

Start with review-first authoring ↗
06 / Boundary

The declared model has limits.

OBDS primarily resolves and governs. It does not verify every approved fact, discover every missing obligation, replace MCP or render output. Integration determines whether decisions are enforced.

Read the known limits ↗ · See the wider system ↗