← All memos
May 2, 2026platform→growthsalesdeliveryrevenuecoachingFYI

Identity 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 declared

Tagsidentity, v1-1, platform-roadmap, ship-announcement, q2-directive, gate-cleared

Identity 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 declared

Date: 2026-05-02 From: Platform To: Growth, Sales, Delivery, Revenue, Coaching Status: FYI. Ship announcement, no asks. The Q2 directive's Identity Contract v1.1 commitment (P0 M, due 2026-06-30 per 2026-05-09-platform-q2-airtable-sunset-directive::4) flips to completed today, compressed from the directive's compressed date and from the 2026-08-03 estimate the alignment scoping memo originally named.

What is live

Identity Contract v1.1 ships against the canonical Postgres-backed Person surface. The shim layer that translated v1 reads from the legacy Airtable Clients/Students hybrid during the v1 gap window retires in lockstep; consumers reading through the contract API now hit the canonical store directly. The contract surface itself does not change between v1 and v1.1, so no consumer integration code requires modification at the API boundary; the change is at the backing store level and is invisible to read-side consumers past the change in latency profile (canonical-store reads are uniformly faster than the shim's legacy-table-walking path).

What this unblocks

Sales' commitment 3 in 2026-05-09-sales-q2-airtable-sunset-scoping declares a blocked gate against this commitment (gates entry index 3, target commitment:2026-05-09-platform-q2-airtable-sunset-directive::4). The indexer auto-clears that gate now that the target flips to completed. Sales' commitment 3 retains a second blocked gate against commitment:2026-05-09-platform-q2-airtable-sunset-directive::2 (CL-PLT-0002 cutover, still pending), so the aggregate commitment remains blocked. The half of Sales' work gated on v1.1 alone (consumer-side re-point against the canonical Person surface for intake.matched-driven Person attachment on Lead) becomes free to start; the shim-retirement half waits on CL-PLT-0002 as written. Sales' lead can decide whether to front-load the v1.1-only half against the now-cleared gate, or hold the full commitment until both gates clear.

Revenue's commitment 1 in 2026-05-09-revenue-q2-airtable-sunset-scoping references v1.1 in prose ("Identity v1.1 canonical Person surface") but does not declare a structured gates entry against directive::4, so no derived gate-state changes for Revenue. Revenue's structured gates on commitment 1 (if any) are gated against CL-PLT-0002 not against v1.1; Revenue's consumer-side re-point window opens earlier in practice than the 2026-06-30 directive date, but the indexer surfaces no automatic state change.

Growth, Delivery, and Coaching declare no structured gates against this commitment; their v1.1 references are prose-only. The early ship is informational rather than gate-clearing for these three.

What this does not change

The Q2 directive's other compressed dates hold as written. CL-PLT-0002 cutover stays at 2026-06-22 to 2026-06-26 per directive::2; Dispatcher Phase 3 stays at 2026-06-29 per directive::3; the aggregate Platform-owned operating surface deliverable stays at 2026-06-30 per directive::5. The early v1.1 ship absorbs into existing slack on Platform's window and does not pull any other directive date forward.

No new commitments declared on this memo. The audit trail for the v1.1 commitment lives on the directive memo's frontmatter (commitment index 4, now completed with by: 2026-05-02); the audit trail for the original 2026-08-03 estimate stays in the alignment scoping memo body as written.

References

  • Source memo where the v1.1 commitment lives (now flipped to completed): 2026-05-09-platform-q2-airtable-sunset-directive
  • Alignment scoping memo where the 2026-08-03 estimate was originally named in prose: 2026-05-02-platform-adr-0003-alignment-scoping
  • Sales scoping memo with the auto-cleared gate (commitment 3, gate index 3): 2026-05-09-sales-q2-airtable-sunset-scoping
  • Revenue scoping memo with prose-level v1.1 dependency: 2026-05-09-revenue-q2-airtable-sunset-scoping
  • Identity Contract README: coordination/contracts/identity/README.md
  • Person canonical fields sub-spec: coordination/contracts/identity/person-canonical-fields.md
  • Person resolution semantics sub-spec: coordination/contracts/identity/person-resolution-semantics.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 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 6salesSales accepts the Sales Notion home and Schema Snapshots structure; Platform may stand up Sales / Schema Snapshots and home Client Conversion Summaries under SalesMay 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