brand-authority

# 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 1. 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. 2. 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. 3. If the fetch returns usable guidance, extract the rules relevant to this de...