---
file: decisions.md
owner_role: <martech-lead>
approver_role: <per entry>
status: draft
version: 1
effective_from: <YYYY-MM-DD>
last_reviewed: <YYYY-MM-DD>
review_by: <none; append-only>
review_cadence: append on each decision, release and incident
change_triggers: [decision made or superseded, release, data incident, context file version change, access review]
open_items: 0
---

# Decisions

Copy to `martech-context/decisions.md`. Set `status: approved` once the creation entry below names the approver. Append-only, newest first in each section. A decision is replaced by a new entry that supersedes it; the old entry changes only its `status`.

## Open items

- <question> | owner: <role> | due: <YYYY-MM-DD>

## Approval policy

Who may approve which change, and the limits of that approval. Skills that write to live systems read this before acting.

- Change class: <for example negative keywords, budget change, tag publish, CRM bulk update, audience sync, vendor context store update>
  - Approver role: <role>
  - Maximum objects per batch: <n>
  - Maximum spend change: <amount and currency per day, or not applicable>
  - Freeze windows: <dates or recurring periods, for example month-end close, launch weeks>
  - Approval expires after: <hours or days>
  - Decision: <ID of the entry that set this policy>

## Decisions

### D-<YYYYMMDD>-<n>: <title>

- Date: <YYYY-MM-DD>
- Status: <proposed | accepted | superseded by D-...>
- Context: <what forced the decision, with evidence>
- Decision: <what was decided, precisely; include full current lists where other skills need them, for example every domain in the cross-domain list or every rule in a custom channel group, in order>
- Alternatives considered: <options and why not>
- Consequences: <effect on reported numbers; series break and from which date; what must be updated>
- Effective from: <YYYY-MM-DD>
- Affects: <files and their new versions, metric IDs, tools, dashboards, skills>
- Owner: <role>; approved by: <role> on <YYYY-MM-DD>
- Review trigger: <what would reopen it>

Typical subjects: creation, refresh or targeted update of this folder (with each file's version); consent model per region (basic or advanced, category mapping, withdrawal rule); reporting time zone or currency changes; attribution model and window changes; custom channel groups, unwanted referrals, cross-domain list; UTM cutovers and value mappings; naming exceptions; identity model and account boundary; messaging policy (frequency caps, quiet hours, control groups); competitor, served-region and existing-customer rules for paid search; tool selections and removals; access reviews after an agency or owner change; metric definition changes and historical treatment.

## Release log

Changes to systems that can move numbers.

- <YYYY-MM-DD> | <system> | <change> | <version or reference> | released by <role>

## Data incidents

Date ranges where numbers are wrong or missing.

- <YYYY-MM-DD to YYYY-MM-DD, or "from YYYY-MM-DD, open"> | <tools and metric IDs affected> | <cause> | treatment: <annotated | restated | excluded> | record: <incident record location or none>