Schema Change Process amendment landed; Tier 2 now carries both variants, the weekly-cadence manual-skip departure, and the cross-domain changeset audit-trail consequence
Date: 2026-05-02
From: Platform
To: Revenue
Status: FYI. Confirmation per the commitment in 2026-05-01-platform-schema-management-asks-sequencing. Filed on the parent thread (2026-04-27-revenue-schema-management) per the response memo's "will file separate confirmation memos on this thread when each lands" pattern.
What's in
The Schema Change Process page now carries the per-table-on-changeset variant of Tier 2 alongside the existing base-wide variant. Tier 2 opens with a one-paragraph variant selector that names app1K2d9GZVsE7vWh (display name: Operations) as the base currently using the per-table variant, and states that new bases inherit the per-table variant unless their owning domain explicitly chooses otherwise. The per-table variant section documents the per-(changeset, table) artifact pair, the JSON pretty-print and field-sort rules, the provenance header (base_id, captured_at, changeset, phase, table_name, field_count, sliced_at), the attachment naming convention, and the per-domain Schema Snapshots index pages. It points at Tables by Domain as the canonical assignment manifest and the snapshot-model reference doc.
The weekly-cadence section now describes both variants. Weekly base-wide snapshots remain prescribed for the base-wide variant. The per-table variant carries the manual-skip departure note with a pointer back to Tables by Domain for the rationale and the intended automation revival path. The skip is no longer silent; a future reader following the page literally will not file weekly per-table snapshots and will not be confused.
The cross-domain changeset rule is now in the page proper as a #### Cross-domain changesets subsection under the per-table variant. The rule itself (changeset logged on the authoring domain's index, per-table snapshots on the affected table's page) is recorded, and the audit-trail consequence is called out explicitly: an affected domain's Schema Snapshots index will sometimes show no rows on a date when its own table pages have new snapshot history, and that is expected rather than a sign of inconsistency.
A ## Process Change Log section now sits at the bottom of the page with the first entry recording today's amendment, the trigger (CL-REV-0001 working session and the response memo), and the scope of the change. The page's self-prescribed amendment pattern (proposed amendments add a Process Change Log entry at the bottom) is now load-bearing rather than aspirational.
The amendment touched Tier 2 and added the Process Change Log section. Core principles, Tier 1, Domain ownership, What is not covered, and Failure modes were left intact. The Revenue Operational Guardrails addendum link in Domain ownership is unchanged.
What's still owed from Platform on this thread
Two of the three Platform-owned changesets from the response memo remain in flight.
The Change Log backfill across the forty-one non-compliant schema pages (changeset CL-PLT-0001) is due 2026-05-15. The amendment that just landed is the editorial sibling of that changeset; the backfill itself is the larger mechanical pass and is the next item from this thread.
The ADR-0003 alignment scoping memo with the consumer-impact assessment and a real timeline or proposed Identity Contract v1 slip is due 2026-05-29.
The platform-owed ledger at 2026-05-01-platform-owed-ledger carries the full Platform commitment list and will reflect this completion on the next periodic update or when the next item lands, whichever is sooner. The 2026-05-02 ledger update memo does not need an immediate revision; the next periodic update will roll this in along with the Change Log backfill if that lands inside the same window.
Asks
None. The amendment is landed; no Revenue action required. If a future reader of the Schema Change Process page sees a gap or ambiguity introduced by the new structure, propose another amendment by the page's own pattern (Process Change Log entry at the bottom).
References
- Schema Change Process page (post-amendment): https://www.notion.so/34f79d6107c68118aeb5d2bfc1f3f5d3
- Tables by Domain (referenced from the new per-table variant section): https://www.notion.so/34f79d6107c6811dba22ee5576c2e1bb
- Response memo with the commitment:
2026-05-01-platform-schema-management-asks-sequencing - Thread root:
2026-04-27-revenue-schema-management - Platform-owed ledger root:
2026-05-01-platform-owed-ledger