# Mandy + Danny change control

## Who decides?

- **Mandy:** approves brand voice, visual direction, preferred examples, official creative assets and messaging.
- **Danny:** verifies website implementation, accessibility, responsive behavior, file constraints and technical dependencies.
- **Both:** approve a new system-wide version. Any change to locked production work follows the Master Handoff change-control process separately.

## Four statuses

`Approved by us` / `Observed in existing materials` / `Proposed for review` / `Still unresolved`.

## For each change

1. Log the proposed change in `guide/decision-register.csv` with source, reason and effect on channels.
2. Create a branch: `proposal/<short-description>` and, if needed, update the visual page and example assets.
3. Mandy reviews whether it feels like RACE, including student experience and accurate, supportive wording.
4. Danny reviews desktop/mobile, contrast, CSS token consistency, link behavior, focus, and any WordPress/HighLevel dependencies.
5. If a **locked** page/form/workflow/CTA/tracking component is affected, identify risk first and use a safe scoped QA process; never automatically deploy a global rule.
6. Record both approvals and decision date in the GitHub pull request. Merge to `main` only after approval.
7. Bump version: PATCH for correction, MINOR for a new approved pattern, MAJOR for a breaking change. Tag `v1.0.0-approved` after first complete approval.
8. Update `CHANGELOG.md`, `VERSION.json`, references and a short QA checklist. Keep old versions available.

## Release rules

- Only releases explicitly tagged `-approved` are approved across channels.
- All `-draft` versions are review materials, even where they contain already approved facts/colors.
- Mark deprecated rules instead of silently removing them.
- Separate *mutable program data* (tuition, start dates, schedules, program facts) from relatively stable *design rules*. Verify facts with current admissions/campus owners.

## File and privacy guidelines

Use a **private** GitHub repository. Do not commit student photos without cleared permissions, lead data, form submissions, API keys, advertising credentials, or private school documents to a public website. GitHub Pages is generally public-facing; use an access-controlled host for a private visual reference.


## Updated release gate - v0.2.1

Mandy confirmed on October 30, 2026 that RACE has permission to use the supplied photographs and pictured models publicly in website/marketing materials. Danny still needs to verify that only web-sized imagery is included, metadata is stripped, and presentation/alt text are appropriate. The supplied logo is a candidate file, not yet a certified official master.