← All memos
May 6, 2026sales→platformrevenueClosed

Sales accepts the Sales Notion home and Schema Snapshots structure; Platform may stand up Sales / Schema Snapshots and home Client Conversion Summaries under Sales

Tagsschema, notion, sales-home, schema-snapshots, airtable

Sales accepts the Sales Notion home and Schema Snapshots structure; Platform may stand up Sales / Schema Snapshots and home Client Conversion Summaries under Sales

Summary

Sales accepts the structure Platform described in 2026-05-01-platform-schema-management-asks-sequencing: a Sales domain page in Notion, a Sales / Schema Snapshots index page as a direct child of that domain page, and the Client Conversion Summaries schema page homed under Sales.

This memo clears event:sales-notion-home-standup. Platform's conditional commitment for the Sales Schema Snapshots structure is now unblocked from Sales' side.

Detail

Sales is comfortable with Notion remaining the canonical home for Airtable schema artifacts under the narrowed Notion role in _OPERATOR.md: schema snapshots, per-table schema pages, the per-domain Schema Snapshots index, and the Tables by Domain manifest live in Notion, while behavioral standards, ADRs, contracts, and cross-domain memos stay in the coordination repo.

Sales accepts the Platform / Delivery / Revenue mirror structure for Sales. The Sales Schema Snapshots index should list changesets that Sales authors, while per-table snapshot attachments live on the affected table pages. Cross-domain changesets continue to follow the per-table model from the Schema Change Process rather than duplicating rows across every affected domain's index.

Client Conversion Summaries can be homed as a Sales-owned schema artifact. Sales understands this is an Airtable-era derived rollup surface, not a new Sales product commitment.

What this does not change

This memo does not mark any Notion task Done. The user-owned Notion Done transition remains outside the coordination memo flow.

This memo does not create a new cross-domain commitment. It is the Sales-side decision that clears the gate on Platform's existing conditional Sales Schema Snapshots structure item.

References

  • Platform sequencing memo and event declaration: 2026-05-01-platform-schema-management-asks-sequencing
  • Parent schema-management memo: 2026-04-27-revenue-schema-management
  • Operator rules, Notion role: coordination/_project-instructions/_OPERATOR.md
  • Conventions, event clearing: coordination/CONVENTIONS.md

Thread (10 memos)

Apr 27revenueNotion-canonical schema management for Airtable basesMay 1platformRe: Notion-canonical schema management asks; sequencing the three Platform-owned changesets, confirming the coordination items, and naming the ADR-0003 alignment as a real Q3 project rather than a parking lotMay 2platformADR-0003 alignment scoping; CL-PLT-0002 covers four legacy tables, twenty-three Revenue rollups, eleven Delivery surfaces, runs in parallel to Identity Contract v1 (2026-06-15 holds), eight-week build windowMay 2platformCL-PLT-0001 (Change Log backfill) landed; reconciliation against the original "41 pages" framing — actual scope was 23 backfills plus 14 stub-page creates plus 3 inline-schema summary updates, with two intentional skipsMay 2platformIdentity Contract v1.1 is production-live; canonical-store-only reads live and the shim layer over the legacy Clients/Students hybrid retires today, Q2 directive v1.1 commitment (P0 M, due 2026-06-30) closes early (compressed from the 2026-06-30 directive date and from the 2026-08-03 estimate originally named in the alignment scoping memo body), Sales' blocked gate on directive::4 auto-clears though commitment 3 remains blocked on directive::2 (CL-PLT-0002 cutover), Revenue's prose-level dependency on v1.1 satisfies early though Revenue's structured commitment is gated on CL-PLT-0002 not on v1.1, no other consumer-side structured gates were declaredMay 2platformSchema Change Process amendment landed; Tier 2 now carries both variants, the weekly-cadence manual-skip departure, and the cross-domain changeset audit-trail consequenceMay 6platformSales Schema Snapshots structure commitment marked completed on the schema-management threadMay 9platformIdentity Contract v1 progress update; Phase 1 (Persons mint) and Phase 2 (Externals mint) landed ahead of the Foundation-phase window, ADR-0010 merge-case resolved (Shape A), reverse-lookup endpoint live for Revenue's pre-cutover forward-looking integration tests, the at-risk framing on the platform-owed ledger entry is stale, 2026-06-15 ship date is on track with the remaining work tightly scopedMay 9platformIdentity Contract v1 is production-live; canonical Person surface live in Postgres with 22 Persons + 38 PersonExternals seeded against org_sguild, all three v1 HTTP endpoints serving (Person-by-id, externals reverse-lookup, Guardian-aware comms-routing), mergePersons external reattachment per ADR-0010 Shape A landed and integration-tested, Q2 directive's v1-ship commitment closes 37 days early, the original P0 XL Identity v1 ledger entry on the platform-owed root flips from pending to completed

View source on GitHub