OutlineDriven Brand authority
Contract
| Field | Bound contract |
|---|---|
| Trigger | User asks for branded or style-governed output. |
| Authority | Reversible local: write only the named local deliverable file(s); the brand authority itself is read, never mutated. Rollback is deleting or overwriting the local deliverable file(s). |
| Side effect | Local deliverable file(s) written under the working directory; no publish, deploy, remote, credential, or hosted-authority mutation. |
| Done | The deliverable follows the fetched brand authority and states the material constraints that shaped it. |
Inputs
- The deliverable request: what to create, revise, or review (e.g., launch page, doc, HTML/CSS component, UI mockup, prompt, social asset, copy, presentation).
- The brand authority source: a URL or local file path to the canonical brand/style guidance. If the user did not name one, ask for it before producing any output; do not proceed from memory.
Procedure
- Confirm the deliverable request and the brand authority source. If either is missing or ambiguous, ask the user before mutating any file. Done when: both the request and the authority source are confirmed.
- Fetch the brand authority from the supplied URL, or read it from the supplied local path. Do not rely on recalled brand rules when a fetchable authority exists. Done when: the brand authority is fetched and available for extraction.
- If the fetch returns usable guidance, extract the rules relevant to this deliverable: visual style, color usage, typography, voice and tone, component rules, naming and capitalization, and implementation guidance. Done when: the relevant rules are extracted from the authority.
- Apply the extracted rules to produce, revise, or review the deliverable. Write only the named local deliverable file(s); never write to the authority source or any remote target. Done when: the deliverable is produced or revised following the extracted rules.
- In the delivered result, state the material brand constraints that shaped the output (e.g., a specific palette, type scale, voice rule, or naming convention that determined a choice). Done when: the material constraints are stated in the result.
Failure and recovery
- Authority unreachable or empty: state that the canonical brand authority was unavailable and ask the user whether to proceed with best-effort guidance or to retry the fetch. Do not fabricate brand rules and present them as authoritative.
- Ambiguous deliverable request: ask for clarification before writing; do not guess scope.
- Partial result: never ship a deliverable that claims brand authority it did not actually fetch. If you extracted only some guidance, apply only that guidance and note the gap.
- Non-mutation: the hosted or local authority is read-only; recovery from a wrong local deliverable is overwrite or delete of that local file only.
Output
One or more local deliverable file(s) conforming to the fetched authority, plus a short note of the material brand constraints that shaped the result, if the authority was unavailable, the output is the unavailability notice and the user prompt, no branded artifact.