Initiatives

What each team is shipping, tracked by indicators rather than dates. An initiative is done when every indicator reaches its target and holds steady — no calendar commitments. Click Read full memo on any card for the operator-level scope.

Live - fetched 2026-07-13 09:18 UTC-generated 2026-07-13 09:18 UTC

All platform growth sales delivery revenue coaching finance portfolio

Total

In flight

Complete

Retired

In flight

active initiatives; readiness read off the indicator dashboard, not a date

Sales close-orchestration initiative scope under no-rocks no-dates

In flight

sales·Filed May 16, 2026·5 indicators·Read full memo ↗

In progress

Scheduling consumer module presentscaffolded 2026-05-16 per 2026-05-16-sales-scheduling-consumer-module-scaffolded: modules/scheduling/ with dto/schema/repo/service/actions/routes/index, lib/delivery/lesson-hold-client.ts wrapping all four §4 endpoints with snake/camel boundary and discriminated outcome unions, /api/scheduling/lesson-holds/* mounted, /admin/scheduling/test debug page; 23 new tests pass; not yet called from operator workflow, eligibility + reservation upstream steps still at 0% on their own indicators→modules/scheduling/ (or equivalent) exists in the Sales repo following the per-domain module pattern, with dto/schema/repo/service/routes and a hold-create call shape against contracts/sales-scheduling-surface §4.1

Structural presence of the Sales consumer module for the sales-scheduling-surface contract; the first observable signal that the close-orchestration build has actually picked up rather than being deferred indefinitely

Eligibility by description call site livescaffolded 2026-05-16 per 2026-05-16-sales-eligibility-consumer-module-scaffolded: modules/eligibility/ with dto/schema/repo/service/actions/routes/index, lib/coaching/eligibility-client.ts wrapping §4.2.2 with snake/camel boundary and discriminated outcome union, /api/eligibility/by-description mounted, /admin/eligibility/test debug page, service-layer console log carries asOf + projectionAsOf per the validation file; 15 new tests pass; not yet called from operator workflow, stale-projection orchestration waits on the reservation consumer indicator→Sales calls Coaching's coach-availability §4.2.2 eligibility-by-description endpoint from the offer-construction seam with as_of from each response logged per coach-availability validation/sales-offer-construction.md

Operationalizes the existing coach-availability validation obligation on Sales (as_of logging per response) and provides the upstream evidence the offer-construction audit shape persists; this is where the eligibility set acted on becomes observable

Reservation request call site livescaffolded 2026-05-16 against INFERRED endpoint shape per 2026-05-16-sales-reservation-consumer-scaffolded-with-contract-gap: modules/reservation/ with dto/schema/repo/service/actions/routes/index, lib/revenue/reservation-client.ts wrapping POST /api/v1/reservations with snake/camel boundary and discriminated outcome union, /api/reservations mounted, /admin/reservations/test debug page; 13 new tests pass; placeholder shape pending Revenue contract addendum + lock-state vocabulary reconciliation requested on the close-orchestration thread→Sales calls Revenue's credit-reservation-lock surface to obtain a crr_ in requested state before any hold-create call, with the producer-transactional-guarantee shape on Sales' service-layer call sites per ADR-0009

Second of the four canonical close-path steps from contracts/sales-scheduling-surface §6.6; Revenue's surface is the upstream of Delivery's hold-create and gates the canonical retry pattern (release-and-reserve-fresh on HTTP 409) per the 2026-05-07 close-orchestration confirm

First hold create call in production0%; producer surface unbuilt on Delivery's side per 2026-05-16-delivery-sales-scheduling-surface-build-state-observation, Delivery's producer-side scoping commitment is the gating dependency→Sales' offer-construction path calls Delivery's sales-scheduling-surface §4.1 hold-create endpoint in production with at least one organization, returns 201, lock advances requested -> held, and delivery.lesson-hold.created lands on the dispatcher; equivalent sandbox/fixture-mode conformance test against validation/sales-close-orchestration.md and validation/lock-state-machine-conformance.md passing as the staging signal

End-to-end booking flow signal; the indicator that closes the close-orchestration pilot's structural readiness criterion. Stays at 0% until both the Sales consumer build AND Delivery's producer surface are callable in the same environment

Offer construction audit shape persistedscaffolded 2026-05-16: modules/workbench-sources/ exports insertOfferConstructionAuditEvent (typed OfferConstructionAuditInput interface) that writes a V1 AuditEvent with fixed eventKey sales.offer.constructed and source close-orchestration, structured metadata captures decisionAt + projectionAsOf + requestShape + selectedCoachId + selectedWindow + eligibilitySet + notes per the eligibility-thread agreed shape; summary auto-generated from coach+window; 1 new test in workbench-sources.repo.test.ts asserts the persisted shape; not yet called from operator workflow, orchestration call site lands when the reservation-request + first-hold-create indicators advance→Sales persists decision-time, projection-as-of (from each coach-availability response), request shape, selected coach/window when present, and the eligibility set acted on for the final pre-reservation eligibility read; audit rows queryable from a Sales-owned table or audit_event stream

The instrumentation shape from the closed eligibility thread (2026-05-15-delivery-eligibility-consumer-surface-positions); this indicator is the trailing-indicator home for the commitment that retired from the cross-domain ledger. Sales-owned source record for any future cross-consumer comparison report against Delivery's parallel assignment-seam audit

Complete

every indicator at target for a stable observation window

Sales initiative scope under the no-rocks no-dates shift

Complete

sales·Filed May 23, 2026·7 indicators·Read full memo ↗

In progress

Dispatcher dev stub offfalse (DISPATCHER_DEV_STUB=false in ../sales/.env)→DISPATCHER_DEV_STUB unset in production with clean lead.* emit through the real bus, stable observation windowstable 58drefreshed 58d ago

DISPATCHER_DEV_STUB env flag state in production plus producer-transactional-guarantee shape on lead.* emits; flip is Sales-internal code work since Phase 2 has shipped

trend:false (DISPATCHER_DEV_STUB=false in ../sales/.env)→completed: DISPATCHER_DEV_STUB=false and readiness smoke inserted a real dispatcher lead.created event→completed: DISPATCHER_DEV_STUB=false and readiness smoke inserted a real dispatcher lead.created event on 2026-05-07→false (DISPATCHER_DEV_STUB=false in ../sales/.env)

Auth dev stub offtrue (AUTH_DEV_STUB=true in ../sales/.env)→AUTH_DEV_STUB unset in production with operator-tenant-roles resolved through real auth sessions, stable observation windowstable 58drefreshed 58d ago

AUTH_DEV_STUB env flag state in production plus auth-resolution health; Platform bootstrap now returns tenant_id and Sales maps Platform owner/admin to the existing sales-ops-admin gate without creating new Platform role vocabulary

trend:false (AUTH_DEV_STUB=false in ../sales/.env)→completed: AUTH_DEV_STUB=false and auth bootstrap smoke passed with a real signed-in session→completed: AUTH_DEV_STUB=false and auth bootstrap smoke passed with a real signed-in session on 2026-05-07; local .env values are not authoritative for this production-facing indicator→true (AUTH_DEV_STUB=true in ../sales/.env)

Operator postgres opt in coverage0% (no operators)→100% of in-cadence operators on the new Sales appstable 58drefreshed 58d ago

Per-operator cadencePostgresReadsOptIn flag coverage; tracks the C-4 cohort rollout, opted-in operators use the new Sales app while opted-out operators continue using the legacy Airtable interface directly

trend:0% (no operators)→100% (1/1)→completed: 100% (1/1)→0% (no operators)

Airtable dev stub offfalse (AIRTABLE_DEV_STUB=false in ../sales/.env)→AIRTABLE_DEV_STUB unset in production with Airtable read paths gated behind canonical Postgres surfaces, stable observation windowstable 58drefreshed 58d ago

AIRTABLE_DEV_STUB env flag state in production; the stub gates Airtable reads while Sales' modules cut over to Postgres; flips off as the cadence runtime, lead pipeline, and Lead inbox fully retire their Airtable read paths

trend:false (AIRTABLE_DEV_STUB=false in ../sales/.env)→completed: AIRTABLE_DEV_STUB=false, operator-facing Sales app reads are Postgres-backed, and remaining Airtable usage is drift/mirror/migration tooling→completed: AIRTABLE_DEV_STUB=false, operator-facing Sales app reads are Postgres-backed, and remaining Airtable usage is drift/mirror/migration tooling on 2026-05-07→false (AIRTABLE_DEV_STUB=false in ../sales/.env)

Identity dev stub offfalse (IDENTITY_DEV_STUB=false in ../sales/.env)→IDENTITY_DEV_STUB unset in production with Person reads through the canonical Identity contract surface, stable observation windowstable 58drefreshed 58d ago

IDENTITY_DEV_STUB env flag state in production; the stub returns synthetic Person resolution while Sales' Lead-to-Person attachment via intake.matched and X-1 consumer-side reads cut over to canonical Identity v1.1; flips off when X-1 lands

trend:false (IDENTITY_DEV_STUB=false in ../sales/.env; readiness smoke passed against real Person-by-id and adult comms-routing)→completed: IDENTITY_DEV_STUB=false and readiness smoke passed against real Person-by-id plus adult comms-routing→completed: IDENTITY_DEV_STUB=false and readiness smoke passed against real Person-by-id plus adult comms-routing on 2026-05-07→false (IDENTITY_DEV_STUB=false in ../sales/.env)

Done

Cadence state drift ratecompleted: 0% drift (49 processed, 0 with drift after Airtable mirror backfill and readback patch on 2026-05-07)→zero drift over a stable observation windowrefreshed 67d ago

Postgres-Airtable cadence-state drift rate from the hourly drift-check script (C-6 in 2026-05-14-sales-cadence-runtime-cutover-design); precondition for retiring the Airtable write side

trend:0% drift (49 processed, 0 with drift after Airtable mirror backfill and readback patch)→completed: 0% drift (49 processed, 0 with drift after Airtable mirror backfill and readback patch)

Customer handoff emit healthcompleted: Sales subscriber transport, payload-composite dedup, close-handler feature flag, transactional first-lock emit, and handoff audit are ready; Revenue answered on 2026-05-07 that no new Sales work is requested→Sales-side customer.handoff readiness complete; Revenue canonical producer traffic observation tracked outside the Sales migration initiativestable 67drefreshed 67d ago

Sales-owned customer.handoff readiness for the migration initiative; Revenue canonical producer observation no longer gates Sales migration completion and is tracked in Revenue's cutover lane

trend:in progress: Sales emit ON; no canonical Revenue customer.handoff traffic observed in this window (since=2026-05-06T04:53:04.586Z, tenant=tnt_sguild, revenue=0, sales=0, firstLocks=0)→completed: Sales subscriber, payload-composite dedup, close-handler feature flag, and handoff audit are ready; Revenue reply requested in 2026-05-07-sales-revenue-customer-handoff-producer-observation-ask→completed: Sales subscriber transport, payload-composite dedup, close-handler feature flag, transactional first-lock emit, and handoff audit are ready; Revenue answered on 2026-05-07 that no new Sales work is requested