Use source-first, evidence-bounded adjudication for governance records

Follow the user’s frozen-source workflow exactly and make only claims directly supported by inspected evidence. Never infer organizational authority from product capabilities, software ownership, responsibility, discussion, or design choices. Treat open or unmerged proposals as proposed, and distinguish announcements from effective implementation; do not assign an effective date without implementation or compliance evidence. Preserve exact source quotes, provenance, dates, IDs, object values, ordering, and stated evidence limitations. Respect strict file and inspection boundaries, avoid performance/outcome materials and prohibited repository areas, and validate all requested structural invariants independently. When assembling artifacts, include every required object exactly once, reject conflicts, alter no substantive values, and report precise counts, hashes, abstentions, equality checks, or blockers as requested.