//HOW IT WORKS
One request. Six explicit decisions.
A hypothetical copy request shows where authority is selected, where work stops and why a human approval remains separate from a model result.
//ILLUSTRATIVE TASK
Prepare brand copy for an Austrian product page.
The requester names the brand, Austrian market, product family, output class and proposed message. The example describes the intended run contract; it is not a claim that this complete client flow is live.
01THE RUN
From a request to an authorised result.
- 01
Resolve
Identify the task and select applicable Brand Truth and any separately authorised product facts. A brand claim approved only for another market is excluded by Brand Core.
Applicable authority and scope
- 02
Compile
Pin the selected sources, rules, prompt and versions into the run context. A missing required source stops the task.
Context manifest and versions
- 03
Execute
Call the permitted model operation with the pinned context. The response is a proposal.
Operation and response record
- 04
Verify
Check the proposed output against the bound rules and source restrictions. A failed check blocks the handoff.
Checks and reasons
- 05
Approve
An authorised person reviews the proposal and evidence, then makes a separate decision.
Reviewer and decision
- 06
Deliver
Release only the approved version through the configured destination and keep the delivery record.
Version and destination
- Task
- Brand copy for AT
- Source
- Brand claim A, approved only for DE
- Resolve
- No applicable claim
- Execution
- No model call, no proposal
- Reason
- Market scope mismatch
- Source
- Brand claim B, approved for AT
- Proposal
- Draft copy referencing claim B
- Verify
- Checks and versions recorded
- Approve
- Human decision pending
- Deliver
- Eligible only after separate approval
02A VISIBLE STOP
Relevant is not the same as applicable.
If the only available brand claim belongs to a different market, Brand Core should return no applicable claim. The model should not be asked to improvise authority. A person must repair the source or the request before the run proceeds.
03WHAT THE RECORD SHOULD ANSWER
What must a later approval record explain?
The record should identify the admitted surface, chosen authority, exact versions, checks, human decision and destination. This is the target contract. Current proof remains bounded to the documented synthetic paths.