What does the Policy Review and Versioning Policy require?

Assign an owner, version, effective date, and review cycle to every policy. Re-review policies on the schedule defined by their category. Maintain a public change log for every Layer-1 and Layer-2 policy.

What does the Policy Review and Versioning Policy prohibit?

Do not ship a policy without an owner and a review cycle. Do not let a policy go past its review date without a written re-review.

Policies Internal operating policies

Policy Review and Versioning Policy

Every policy needs an owner, a version number, a review date, an approval status, and a change log.

Version: 0.1.0
Effective: May 20, 2026
Last reviewed: May 20, 2026
Review cycle: every 12 months
Master Policy Index entry: §4 #5

Every policy at Map.ca needs an owner, a version number, a review date, an approval status, and a change log. The doctrinal review cycles are: privacy, security, AI, civic, and child-safety policies every 6 months; terms, accessibility, partner, and ambassador policies annually; and incident-response and breach-response policies after every major incident.

This policy applies to every policy owner at Map.ca and to the engineering team that operates the Policies hub. The data schema in src/data/policy/items.ts enforces the versioning fields.