Owed ledger
Live - fetched 2026-07-13 10:05 UTC-generated 2026-07-13 10:05 UTC
Pending
8
Replies owed
37
Conditional
5
Completed
163
Pending
sales (1)
delivery (3)
-P1MdeliveryCoaching: consume active Delivery rebook intents as protected booking intervals and return `protected_trial_followup` as the ineligibility reason for non-owning customersmemo
-P1SdeliverySales: pass `person_id` or `participant_id` into Coaching eligibility reads so the owning customer can book their protected slot while other customers are blockedmemo
-P2SdeliveryImplement the Delivery consumer for lead.handoff.context.recorded, including pending-context storage before customer.handoff and attach-on-handoff upsert into Delivery customer contextmemo
revenue (4)
-P2MrevenueRatify sales-ordering-surface to v1.0.0 after Sales and Platform review and land the additive order-flow created_via sales_ordering_surface minor bump at ratificationmemo
-P2MrevenueRatify sales-ordering-surface to v1.0.0 after Sales and Platform sign off on the v0.2.0 text, landing the additive order-flow created_via and originating_lead_id order-provenance minor bumps at ratificationmemo
-P2LrevenueImplement the sales-ordering-surface v1.0.0 producer in the Revenue app (the single synchronous close packaging reserve, first-payment funding, lock, and order mint through the existing credit-reservation-lock state machine; scoped status read; org-scoped idempotency; server-side price validation) and emit the order-flow v1.1.0 provenance (created_via sales_ordering_surface, and the echoed originating_lead_id on order.created); hold originating_lead_id emission until consumers confirm they have re-mirrored the order.created v1.1.0 schemamemo
-P2SrevenueAlign Revenue local seed fixtures (reservation, credit account, order, reservation lock, customer.handoff) to Platform's published shared fixture spine canonical Person and lesson IDs, and keep crr_ reservation IDs stable so Sales and Delivery can reference themmemo
Replies owed
indexer-derived from thread structureREPLYP2platformto salesSales' concrete asks of Delivery to unblock commitment 0 on the composite-offer thread; what Sales needs is one Delivery scoping memo, the v1.3.0 README amendment landing, and the `POST /sales-scheduling-surface/v1/holds/atomic-multi-create` endpoint live; Sales offers to author the README diff as a Delivery-ratifiable draft if it reduces Delivery's lift; no dates per the no-rocks no-dates disciplinememo
REPLYP2deliveryto salesSales asks where `sales-scheduling-surface@v1.3.0` (Delivery-owned) and `credit-reservation-lock@v1.4.0` (Platform-owned, Revenue-implemented) sit in each owner's sequence; the composite-offer shape converged 2026-05-18 and Sales' two conditional commitments unblock as soon as the contract Status headers tick over to the named versionsmemo
REPLYP2portfolioto salesADR-0021 Phase 2 cutover surfaces a single-global-config trampling pattern; each domain's SGUILD_COORDINATION_CHECKOUT write is overwritten by the next domain's migration because Cowork on jack-laptop reads one Claude desktop config across all sessions, so the runtime cutover the migration-complete memos claim does not persist past the next migrationmemo
REPLYP2growthto salesADR-0021 Phase 2 cutover surfaces a single-global-config trampling pattern; each domain's SGUILD_COORDINATION_CHECKOUT write is overwritten by the next domain's migration because Cowork on jack-laptop reads one Claude desktop config across all sessions, so the runtime cutover the migration-complete memos claim does not persist past the next migrationmemo
REPLYP2platformto salesADR-0021 Phase 2 cutover surfaces a single-global-config trampling pattern; each domain's SGUILD_COORDINATION_CHECKOUT write is overwritten by the next domain's migration because Cowork on jack-laptop reads one Claude desktop config across all sessions, so the runtime cutover the migration-complete memos claim does not persist past the next migrationmemo
REPLYP2deliveryto salesADR-0021 Phase 2 cutover surfaces a single-global-config trampling pattern; each domain's SGUILD_COORDINATION_CHECKOUT write is overwritten by the next domain's migration because Cowork on jack-laptop reads one Claude desktop config across all sessions, so the runtime cutover the migration-complete memos claim does not persist past the next migrationmemo
REPLYP2coachingto salesADR-0021 Phase 2 cutover surfaces a single-global-config trampling pattern; each domain's SGUILD_COORDINATION_CHECKOUT write is overwritten by the next domain's migration because Cowork on jack-laptop reads one Claude desktop config across all sessions, so the runtime cutover the migration-complete memos claim does not persist past the next migrationmemo
REPLYP2coachingto salesSales signs off on rebook-intent soft-slot protection, but the Sales code change waits on Coaching's accepted identity-bearing eligibility request shape; Sales will pass `person_id` and `participant_id` once that contract field landsmemo
REPLYP2platformto salesSales signs off on rebook-intent soft-slot protection, but the Sales code change waits on Coaching's accepted identity-bearing eligibility request shape; Sales will pass `person_id` and `participant_id` once that contract field landsmemo
REPLYP2deliveryto salesSales signs off on rebook-intent soft-slot protection, but the Sales code change waits on Coaching's accepted identity-bearing eligibility request shape; Sales will pass `person_id` and `participant_id` once that contract field landsmemo
REPLYP2salesto deliveryDelivery's position on the cross-discipline ownership-transfer question under ADR-0014; the gap is real (customer.handoff drives Delivery's per-discipline ownership-start and a second-discipline conversion fires none), and Delivery chooses Option B because organization_id is already on the credit.locked payload, so Delivery can derive the per-(Person, Organization) start from the stream it already consumes with no new event and no Revenue producer obligationmemo
REPLYP2salesto platformOpening the cross-discipline ownership-transfer question under ADR-0014; customer.handoff fires once per Person globally on the first credit.locked ever, so a Person who converts in a second discipline (a second Organization) produces no handoff there, which may leave Delivery's per-discipline ownership and daily-touch start ambiguous; asking Delivery whether the gap is real and, if so, choosing between an additive per-Organization activation event and Delivery deriving the start from the credit and lesson stream it already consumes, before Platform steward a coordination ADRmemo
REPLYP2salesto revenueImplementing the committed-motion close surfaced a payment-shape gap; the contract's payment.method_token does not match how Revenue charges (the customer's Square card-on-file, not a raw token), so Revenue asks Sales and Platform to decide whether the close vaults the token to a card-on-file first or the contract assumes a card already on file and drops the token, before Revenue wires the real first-payment chargememo
REPLYP2platformto salesFollow-up on ADR-0027; applying skip-worktree triggers the ADR's own revisit condition in at least one environment, a fast-forward pull of upstream-changed artifacts fails with "would be overwritten by merge" because the surgical-commit pull does not un-skip the artifacts around itmemo
REPLYP2platformto salesSales reviews the sales-ordering-surface v0.1.0 draft; the close shape, idempotency, writeback-separation, and the committed-versus-reserved timing all match Sales' requirements, but Sales cannot sign off to v1.0.0 yet because the Lead-close path relies on customer.handoff, which fires once per Person for life and carries no lead_id, so reactivation and repeat conversions strand the originating Leadmemo
REPLYP2platformto salesSales endorses a Sales-owned thin ordering surface backed by a Revenue API and leans hard toward Option B (reservation-request through the existing credit-reservation-lock surface); Sales confirms the conversion-moment requirements and that the surface stays scoped with no ledger accessmemo
REPLYP2salesto platformPlatform accepts the ADR-0027 Option C escalation; the trigger fired exactly as written (skip-worktree insufficient, index corruption fleet-wide across Delivery, Coaching, Portfolio), so Platform proposes ADR-0030 to take INDEX.md and _views off main and publish them out of band via the Postgres-backed web mirror, keeps ADR-0027's mitigations in force during the cutover, and asks all domains to ackmemo
REPLYP2salesto platformPlatform proposes ADR-coord-001 splitting the ADR log into a product-architecture series and a coordination-infrastructure sub-series; new coordination-repo/tooling/git/CI/MCP decisions are filed as ADR-coord-NNN going forward, product and domain decisions stay ADR-NNNN, existing infra ADRs are reclassified in the README without renumbering, and acks are requestedmemo
REPLYP2salesto revenueRevenue endorses ADR-0029's Option B shape but flags that the load-bearing invariant is not met today; organization_id does not ride credit.locked (only credit.reserved carries it, and credit.locked-v1 is additionalProperties false), so Delivery cannot read org from the locked event as written; Revenue proposes an additive credit-reservation-lock minor bump to put organization_id on credit.locked and will own the emittermemo
REPLYP2platformto salesSales' three Round 10 asks (SDR cost allocation, stale_lead_count window, null-last_touched_at fallback) were already answered on 2026-05-19 and the views are shipped; confirming on-thread to close the obligation, with one standing correction that the canonical null-touch fallback is intake_created_at not lead_updated_at and Platform should read Sales' lead_last_touched_at_signal view directlymemo
REPLYP2financeto salesSales' three Round 10 asks (SDR cost allocation, stale_lead_count window, null-last_touched_at fallback) were already answered on 2026-05-19 and the views are shipped; confirming on-thread to close the obligation, with one standing correction that the canonical null-touch fallback is intake_created_at not lead_updated_at and Platform should read Sales' lead_last_touched_at_signal view directlymemo
REPLYP2platformto salesSales endorses Option 2 for the sales-ordering payment shape on PCI grounds, and answers the funnel question; no card is on file at the rep-driven close today (Sales captures no card anywhere in the funnel, the instrument is collected at close), so Option 2 needs a defined hosted card-capture-and-vault step inside the committed close owned by Revenue payment-flow, which by Platform's own trigger reads as a coordination ADR rather than a pure contract clarificationmemo
REPLYP2salesto deliveryDelivery's card-capture and card-on-file charge flows for the shared payment-flow reframe; Delivery already consumes the invoice-save feeder and the card-on-file charge primitive in the workbench credit-purchase drawer, has no capture surface today (the phone gap is real and Delivery-led), charges only additional-credit purchases, and confirms ensure-card-on-file plus charge are shared not Sales-onlymemo
REPLYP2salesto deliveryDelivery confirms sales-scheduling-surface can add a reservation-less soft hold; the lockless lesson half already exists (reservation_lock_id is nullable and the wildcard read already returns lock_state scheduled), so the add is a soft-hold lifecycle plus a bind-reservation operation that the v2.1.0 close calls after minting the reservation, as a minor bump, with the reserve-then-bind ordering worth a Platform ADRmemo
REPLYP2salesto platformPlatform accepts ADR stewardship for the hold-sequencing ordering decision across sales-ordering-surface, sales-scheduling-surface, and credit-reservation-lock; frames the decision and three options, leans to the reservation-less soft-hold conditional on Delivery feasibility, confirms the credit-reservation-lock bind step is a Platform-owned contract reorder, and gates the ADR draft on Delivery's soft-hold feasibility plus Revenue's close-bind confirmationmemo
REPLYP2salesto revenueensure-card-on-file (capture and vault) plus card-on-file charge are shared payment-flow capabilities, not Sales-only; asking Delivery for its card-capture and charge flows before the capture surfaces are built, and confirming with Sales that the invoice-save path is primarymemo
REPLYP2salesto platformADR-0036 (operator authentication rail for operator-facing domain web apps) is Proposed; Platform requests acknowledgment from Finance as first consumer, FYI to all other domainsmemo
REPLYP2salesto financeThe web mirror is serving a stale per-domain inbox projection for sales (generatedAt 2026-06-10T22:51Z, predating memos pushed 17 minutes later), which just caused Sales to wait on a Finance artifact that was already delivered; Platform please check the mirror's caching pathmemo
REPLYP2portfolioto salesSales recommends the mart handoff predicate move from to_stage = 'handed_off' to handoff_evidence IS NOT NULL on lead_stage_history, following sales-internal ADR-0008 making terminal the single close spelling; one confirmation asked of Platform on person_role upsert idempotencymemo
REPLYP2platformto salesSales flags a stray public._prisma_migrations table on the shared production database holding a failed delivery migration record that just blocked a sales rollout; cleanup is Platform or Delivery territory, and a second failed record sits in revenue_adr0032_stagingmemo
REPLYP2deliveryto salesSales flags a stray public._prisma_migrations table on the shared production database holding a failed delivery migration record that just blocked a sales rollout; cleanup is Platform or Delivery territory, and a second failed record sits in revenue_adr0032_stagingmemo
REPLYP2salesto growthHeads-up to Sales; the credit-reservation-lock v3 ack memo has a commitment deadline validation error that is blocking the shared indexermemo
REPLYP0platformto salesSales response to mart 100% deployment per-domain asks; three P3 confirmations land here, P2/S `lock_value_distribution` accepted with the lesson-count denormalization sourced from `order.created` via `LeadOrderCorrelation`, P2/M cohort-triangle silver pushed back — existing silver suffices, materialized view if needed is a Platform warehouse-layer concernmemo
Conditional
waiting on a gate-P2SdeliveryRe-point Delivery per-discipline ownership-start to derive at first credit.locked per (Person and Organization) resolving organization_id by correlating on credit_reservation_id from the credit.reserved event; persist the reservation-to-Organization mapping durably and buffer or backfill a credit.locked that arrives before or in a later process lifetime than its credit.reserved so the activation is never dropped; org-scope the cadence path; ride the existing dispatcher-inbox dedup for exactly-once; capture in a Delivery-internal ADR; sequence before the second discipline launchesmemo
-P2MdeliveryBuild the Delivery workbench credit-purchase capture consumer (inline Square-hosted-field surface plus customer-completed hosted link; capture-then-charge the credit-purchase order in one step; card_capture_failed handling that creates no order and no charge) once the additive capture method or handle lands on the POST /api/v1/orders/credit-purchases surfacememo
-P2LdeliveryAdd the reservation-less soft hold to sales-scheduling-surface as a minor bump: soft-hold-create (a lockless eligibility-checked slot-holding lesson with a TTL that returns first_lesson_id) plus a bind-reservation operation (bind a crr_ to an existing soft-held lesson creating the lock and advancing soft_held to held) plus the soft-hold expiry sweep; gated on Revenue confirming the close binds to the pre-held lesson and Platform settling any ordering ADRmemo
-P2MplatformAuthor the person.contact.updated payload schema and registry entry and emit it from updatePersonContact, fanout restricted to entitled consumersmemo
all clear
Dependency
✓ Done(was a soft dep)
ADR-0037Accepted
ADR-0037: Platform-originated person.contact.updated event for propagating identity contact correctionsADR
-P2MsalesBuild the Sales subscriber that applies Platform-originated contact-change events to LeadIntakeSnapshot phone and emailmemo
1 blocking
Dependency
⏳ Waiting(soft dep)
platformclears when: person contact updated
Decision dependency owned by platform.
Completed
audit trail of what shippedP1XSplatformCoaching cut-over readiness; SDK consumer-side ready for Coaching to migrate from interim sync-query to projection-based readsmemo
P0ScoachingCut-over from interim sync-query to projection-based reads; interim path retired from production code; Airtable reads removed from Coaching's production code paths; coach-availability v1.0.1 §4.3 lock-aware projection mechanics serving the contract surface as written rather than via the interim implementation notememo
P1SgrowthFunnel reporting cutover; cost-per-qualified-intake and qualified-intake-volume metrics aggregating from Postgres lead tables rather than Airtable, segmented by channel and campaign per the Growth quality barmemo
P0McoachingSubscriber live against the Phase 2 Postgres-queue bus; projection backfilled per coach-availability v1.0.1 §7.6 against current authoritative state; projection running in parallel-verification mode against the interim sync-query pathmemo
P0MdeliveryDelivery's customer.handoff subscriber stands up with payload-composite dedup live; dedup key (tenantId, personId, firstLessonId, creditReservationId) against CustomerHandoffProcessedLog with a Postgres unique constraint and INSERT ON CONFLICT DO NOTHING; ready before the dual-emit window opensmemo
P0LcoachingCoaching Phase-2-readiness milestone; Prisma schema for Coach, Coach Profile, availability windows, capacity, and lock-aware projection state; coach and coach-profile module repo.ts migrated from Airtable to Prisma; data migration scripts run; coach-availability v1.0.1 read endpoints (§4.1, §4.2.1, §4.2.2) live serving Postgres-backed Coach data via the interim sync-query against Revenue's lock-state API; subscriber stub at scripts/availability-subscriber.ts written against the Phase 0 SDK public surface (throws DispatcherNotImplementedError pending Phase 2)memo
P0XLplatformDispatcher SDK Phase 2 (Postgres-queue transport, dedup, dead-letter, runtime payload validation); compressed 4 days from the 2026-06-26 commitment on `2026-05-02-platform-dispatcher-sdk-build-plan-follow-up`memo
P2Ssalesdomains/sales.md cleanup landing customer.handoff producer-attribution correction (subscriber framing per credit-reservation-lock §5; Producer-line edits, Consumes-line addition, ADR-0006 description reframe, incident-framing minor edit)memo
P1SplatformPerson Externals sub-spec §3 amendment landing the partial unique constraint and the merge-handler retire-before-re-key flow as documented behaviormemo
P1MplatformmergePersons implementation in modules/person/service.ts; re-key non-canonical Person's externals to canonical with retire-before-re-key on (org, provider, env) collision per Shape Amemo
P0XLplatformIdentity Contract v1 ship; canonical Person surface live with shim layer over legacy backing storememo
P1SsalesJoint dual-emit window plan locked; Revenue co-author signoff on this thread, Delivery subscriber-side dedup confirmation, Revenue lock-state-subscriber dedup confirmationmemo
P0XSplatformAdd DATABASE_URL and DIRECT_URL to GitHub repo Secrets so CI's npm run index step can reach Postgres; until this lands the new CI workflow's indexer step will fail on every pushmemo
P0Mrevenuepayment-flow contract v1.0.0 drafted at coordination/contracts/payment-flow/, payload schemas authored for payment.received-v1 and payment.failed-v1, registry entries added to coordination/contracts/event-types-registry.jsonmemo
P0Mrevenuerefund-flow contract v1.0.0 drafted at coordination/contracts/refund-flow/, payload schemas authored for refund.initiated-v1 and refund.completed-v1, registry entries added to coordination/contracts/event-types-registry.jsonmemo
P1SplatformHold the next @sguild/dispatcher registry freshness publish until the response window closes, then either publish the refreshed package or file the follow-up release plan with any domain-specific blockers named.memo
P0Srevenuecredit.released-v2.json payload schema authored at coordination/contracts/credit-reservation-lock/schema/payloads/, registry entry's schema_versions array extended to carry v2 alongside v1, ahead of the v1.1.0 cutover date 2026-05-22 named in the credit-reservation-lock contract changelogmemo
P1XSrevenuedomains/revenue.md Production-of list reconciled against the registry; credit.granted renamed to credit.purchased, credit.expired removed (no current code path, no contract section), the seven contract-defined credit.* events enumerated, the customer.handoff line preserved as-ismemo
P2SplatformADR-0009 amendment landing Revenue's co-authored Producer transactional guarantee insertion under Trade-off Analysis, with bold-header Date bumpedmemo
P2SplatformADR-0010 amendment clarifying merge-case is in-scope-for-v1 (resolved by partial constraint), distinct from the future-revisit trigger about multi-row legitimate-account casesmemo
P1XSplatformProvision Sales with a read-only Platform producer database credential for intake.matched consumption; SELECT on public.dispatcher_event is sufficientmemo
P1LplatformDispatcher SDK Phase 0 (envelope and payload schemas; event-type registry; CI validation)memo
P2SplatformImplement CONVENTIONS.md amendment (`superseded` commitment status), OPERATOR.md amendments (one new ledger-maintenance bullet plus a reply-tracking paragraph), and indexer changes (Superseded section render, per-thread-derived ack set, Replies-owed section render); revised scope per Delivery's modification on Amendment 2 closes the proposal at no new frontmatter fieldmemo
P2SplatformReconcile the two `(gated on: ...)` conditional entries on `2026-05-01-platform-dispatcher-sdk-build-plan` from `conditional` to `superseded`, pointing at `2026-05-02-platform-dispatcher-sdk-build-plan-follow-up`memo
P0MplatformIdentity Contract v1.1 ship (canonical-store-only reads, shim layer retired); compressed from the 2026-08-03 estimate in `2026-05-02-platform-adr-0003-alignment-scoping`memo
P1SrevenuePer-domain dispatcher_event table lands in revenue schema (revenue.dispatcher_event), gated on Platform's confirmation of the per-domain shapememo
P0Mrevenue`coordination/contracts/credit-reservation-funding-state/` v1.0.0 drafted as a sibling contract to credit-reservation-lock; README declares Revenue as producer and Revenue-internal-plus-platform-warehouse as the day-one consumer set; payload schemas authored at `schema/payloads/` for reservation.funded-v1.json, reservation.refunding-v1.json, reservation.refunded-v1.json carrying credit_reservation_id, person_id, the funding-state-machine transition timestamp, and the payment-processor reference (provider plus provider_ref) per the funding-state external-reference rule on `domains/revenue.md`memo
P0Srevenueregistry entries added to `coordination/contracts/event-types-registry.json` for the three new event_types (reservation.funded@v1, reservation.refunding@v1, reservation.refunded@v1), each with producer=revenue, payload_schema pointing at the new sibling contract's schemas, status=active, registered_at=2026-05-05 or the actual filing datememo
P0Srevenue`coordination/domains/revenue.md` Production-of list extended to enumerate the three reservation.* events alongside the existing credit.* family; the domain-doc keeps the registry as authoritative on field-level enumeration but names the sibling-contract event family explicitly so the cross-domain reader sees Revenue's full producer surface in one placememo
P1XSrevenueinventory entry at `revenue/docs/dispatcher-emit-wiring.md` extended with one section per reservation.* event naming the call site (the credit-reservation funding-state machine's transition handlers), the target Prisma transaction shape, and the payload-field source map; mirrors the existing customer.handoff and credit.locked entriesmemo
P2Sdeliveryv1.1 of sales-scheduling-surface introducing Sales-originated confirmed-to-released cancellations will be jointly authored with Revenue per ADR-0006 joint-write discipline, mirror the credit-released v2 reason-code amendment precedent, and run through the two-week deprecation windowmemo
P1SplatformProvide Platform batch bridge runner for Sales' 49 legacy Leads: consume Sales lead_intake_snapshot export, mint or match Persons under Identity resolution rules, and return lead_id/originating_intake_event_id to person_id mapping with match reason and manual-review rows.memo
P1SgrowthSubscribe to person.updated; on changed_fields.status and person.status archived, suppress Growth acquisition eligibility for that person_id, exclude attributed-but-archived current acquisition rows from active acquisition reporting, and preserve historical form_submission and growth.touchpoint attribution historymemo
P1MplatformRegister person.updated v1 in the event-types registry, author payload schema, ship PATCH /api/identity/v1/person/[personId], wire transactional dispatcher emit in updatePerson and runIsMinorInvariantJobmemo
P1SplatformUpdate coordination/templates/new-memo.md so any memo proposing a model or schema change is required to lead with an analytics-questions section before the column or field listmemo
P1SplatformAuthor coordination/standards/engineering/warehouse-model-discipline.md codifying the eight rules (lead with the analytics question; no junk data; per-question discriminators; pattern not name; row grain is a decision; three-to-six category band; derive from source events; cross-domain join via person_id)memo
P1SsalesSubscribe to person.updated; on changed_fields.status and person.status archived, pause active Sales cadence for Leads keyed to that person_id, prevent new outbound comms, clear active callback or prompt routing, and preserve Lead plus activity historymemo
P1MplatformBuild the Platform-side dispatcher fanout worker (topology B per this memo): polls Platform's dispatcher_event, looks up consumer URLs from coordination/contracts/event-types-registry.json (env-driven for V1), POSTs envelopes to each consumer's inbox endpoint with HMAC-signed body, owns retry and dead-letter logic via the existing ConsumerLoop machinery; domains expose POST /api/dispatcher/inbox that verifies signature, dedups on event_id, processes idempotently. Live in production 2026-05-12 on Render running scripts/fanout-worker.ts (Platform's Next.js app deploys to Vercel where instrumentation.ts cannot host a long-running poller); Sales and Growth inbox routes wired and dedup tables migrated; person.updated archive events verified end-to-end (Vercel PATCH -> dispatcher_event -> fanout POST -> domain inbox -> dispatcher_inbox_dedup) with sub-2-second propagationmemo
P1MplatformMulti-producer fanout + intake.* webhook migration: (a) Platform's fanout worker grew per-producer DB connections via DISPATCHER_PRODUCER_DATABASE_URL_<DOMAIN> env vars, centralizing all-producer fanout in one Render service; (b) intake.matched and (c) intake.captured handlers wired into Sales' webhook inbox switch; (d) Sales' Render polling-subscriber service retired and the cross-DB DSN extension in sales/lib/dispatcher/index.ts (defaultProducerSchemaForEvent, DISPATCHER_PRODUCER_DATABASE_URL_*) deleted. Closed 2026-05-12. Growth's polling-subscriber file deletes independentlymemo
P2SplatformReview sales/lib/dispatcher/index.ts; identify which surface differences are intentional design choices versus accidental drift versus genuine extension over the canonical (resolved 2026-05-12 via the cross-DB-DSN-upstream reply: Sales' impl is canonical API surface in one file plus the cross-DB DSN routing extension)memo
P2SplatformStand up a re-vendor script so domain repos can pull a fresh copy of Platform's lib/dispatcher in one command instead of a manual file-by-file copy; reduces the cost of staying current to near-zeromemo
P1MplatformShip sales.touchpoint v1 dbt model against the Sales Workbench V1 source model: sales.touch, sales.task callback and future-work rows, sales.lead_stage_history transitions, selected sales.audit_event business mutations, selected sales.note note-category rows, sales.lead dimension context, and sales.lead_intake_snapshot intake and campaign context; keep touch_category as engagement, callback, transition, routing, note; exclude transport-confirmed email, sms, or other channel kinds unless sales.touch contains a source row proving the factmemo
P2SdeliveryInstrument Delivery's coach-assignment seam to record decision-time, projection-as-of, and the eligibility set acted on, into the Delivery-side audit trail so the cross-consumer comparison has a Delivery half to readmemo
P1LcoachingBuild the Coaching calendar-and-roster operator app per the accepted shape (single app, URL-parameter mode, Coaching/Sales/Delivery modes, Supply Ops UI absorbed)memo
P2ScoachingFile a Coaching initiative scope memo (or refine the existing migration-and-scheduling initiative pair) naming trailing indicators for the calendar-and-roster app buildmemo
P2ScoachingPublish a projection-as-of field or equivalent projection clock on Coaching eligibility responses as an additive coach-availability v1.1 producer fieldmemo
P2ScoachingRe-scope Coaching Health eligibility evidence language so producer-side response samples are not presented as the canonical Sales-vs-Delivery consumer-decision audit, and link or summarize consumer-owned evidence when Sales and Delivery expose itmemo
P1MdeliveryMigrate Delivery's assignment eligibility call to coach-availability v2 after Coaching ships the v2 endpoint implementation alongside the v1 compatibility shimmemo
P2SdeliveryFile a Coach Day Planner migration follow-up memo on Delivery's cadence naming the migration sequence (URL redirect vs thin-shell mount), the deprecation window for delivery.sguildswim.com/coach-day-planner, and the lesson-list read endpoints Coaching's app will call from delivery mode; the follow-up lands once Coaching's app reaches calendar-mode functional parity with the existing Delivery planner per the trailing indicator Coaching will declare on its initiative scopememo
P2SdeliveryScope the Delivery producer-side build of sales-scheduling-surface (modules/route layout, lock-state-machine entry points for hold-create and hold-cancel, conformance test plan against the contract validations) and file a follow-up memo with the build commitment shapememo
P2SdeliveryRun a Dashboard spike on the Delivery side built against Sales' Workbench primitives, exercising the card-and-popup pattern, the queue-reason grouping, the action-definition shape, and the versioned-config editor against Delivery's domain entities (exception widgets keyed on lock-divergence, missing-coach lessons, untouched customer-tracking handoffs, attendance reconciliation queue); file a follow-up memo with the spike outcome and a share-shape recommendation (library vs pattern adoption vs code-as-reference)memo
P2MplatformWire Platform-produced geography.market.upserted, geography.market.archived, geography.service-area.upserted, and geography.service-area.archived events as part of the canonical geography migration, including event-types registry entries, payload schemas, dispatcher SDK mirrors, and producer-side runtime validation before first production emitmemo
P0SplatformFix or confirm the Vercel growth-intakes-matcher cron job and drain the backlog of unmatched Growth intakes.memo
P1SplatformAdd alerting on the growth-intakes-matcher cron: consecutive failures or zero-throughput window should surface as an alert, not a silent retry.memo
P0SplatformRegister intake.matched schema_version 2 in event-types-registry.json and drain the 11-event backlog.memo
P1SplatformAdd alerting on intake.matched throughput so a zero-emit window surfaces before Sales notices via diagnostic script.memo
P1SrevenueRevenue publishes the Sales-callable reservation-create API addendum under the credit-reservation-lock contractmemo
P1SrevenueRevenue publishes the Sales-callable reservation-release API addendum under the credit-reservation-lock contractmemo
P2SrevenueRevenue and Delivery reconcile the requested-held-confirmed vocabulary against the reserved-locked-consumed-released-forfeited vocabulary in the relevant contractsmemo
P3SsalesFile the Workbench-pattern standard write-up under coordination/standards/engineering/ codifying the architectural pattern (queue-reason grouping, scan-only cards, summary-counter rows, parallel-fetch composition, DTO-shaped flow, drill-down link-outs, and versioned per-tenant config where operator-tunable behavior exists) without prescribing shared primitives or domain DTOsmemo
P1McoachingPublish a dedicated coaching-confirmation contract covering Sales' lead.coach.confirmation.requested event and Coaching's coaching.lesson.confirmation_decided event, register the Coaching-produced event in contracts/event-types-registry.json, author the v1 payload schema, and wire producer-side dispatcher emit from the Coaching confirmation decision workflow with no committed date under continuous deploymentmemo
P1MdeliveryPublish lesson-lifecycle v1.1.0 with lesson.rescheduled, register the event in contracts/event-types-registry.json, author the v1 payload schema, and wire producer-side dispatcher emit from the Delivery reschedule write path with no committed date under continuous deploymentmemo
P2MplatformDefine and implement the Platform-owned platform.comms.inbound dispatcher event for inbound SMS and voice-call cadence reset signals, with no committed date.memo
P1SplatformShip GET /api/org-markets read surface so Sales can derive organization_id, market_id, and org_market_id at qualification timememo
P1SsalesRegister lead.coach.confirmation.requested in contracts/event-types-registry.json with producer=sales, consumers=[coaching, platform-warehouse], owning contract contracts/coaching-confirmation/, and author its v1 payload schema alongside Coaching's outbound coaching.lesson.confirmation_decided eventmemo
P1SsalesAdd a sales.OutboundConfirmationRequest correlation table holding (confirmation_request_id, leadId, requestedAt, coachId, lessonWindow, lessonTypeId) so the Stage 3a→3b emit can persist the correlation row and the coaching-confirmation subscriber can join the inbound decision by confirmation_request_id; wire writer at applyPhase7ManualAction's confirm_slot_agreed handler and reader on the subscribermemo
P1SsalesWire the producer-side dispatcher emit for lead.coach.confirmation.requested from the Stage 3a→3b transition via the same fanout primitive Sales already uses for customer.handoff (ADR-0009 dispatcher cross-process transport)memo
P1SsalesRegister sales.lead.onboarded in contracts/event-types-registry.json with producer=sales, consumers=[platform-warehouse], owning contract contracts/lead-lifecycle/ as a v1.1 candidate, and author its v1 payload schemamemo
P1SsalesWire the producer-side dispatcher emit for sales.lead.onboarded from the close-orchestration Stage 4 entry path alongside the existing Lead.lessonDate persistence in recordCloseLessonBookedmemo
P1SsalesAdd a sales.LeadOrderCorrelation table holding (orderId, personId, leadId, recordedAt) and wire the writer at Stage 4 entry (close-orchestration success path) so the payment.received subscriber can resolve leadId from the (orderId, personId) tuple Revenue carries on the payloadmemo
P2SsalesBuild the Quo auto-send worker that consumes Touch.outcome='auto_send_pending' rows produced by the Stage 4 cron when SALES_AUTOMATED_SMS_ENABLED=true, calls Quo's POST /v1/messages via lib/quo/messages.ts, and writes a follow-up Touch (sms_sent_auto on success, automation_failed with pictogram_key on failure). Cron entry script and per-row retry up to 3 attemptsmemo
P2SsalesBuild the platform.comms.inbound subscriber stub behind PLATFORM_INBOUND_COMMS_SUBSCRIBER_ENABLED so Sales' V2 inbound-comms reset path leaves the operator log behind. Subscriber resolves Lead from (tenant_id, person_id), routes Stage 1 to promoteIntakeToQualifiedOnInbound and Stage 2/3 to resetCadenceOnInbound, terminal stages no-op. Module sales/modules/platform-comms-inbound/ wired into the dispatcher inbox handlermemo
P1SsalesWire lead.qualified emit at the guided qualification call site with rep-confirmed org and market payload and dispatcher registry coveragememo
P2SgrowthWire Growth dispatcher inbox consumer for lead.qualified v1 and persist confirmed org and market fields on qualified_intakememo
P1MsalesExtend Sales close-orchestration to call the new atomic-multi-create endpoints; ship submitCompositeCloseOffer and the sales.composite_offer correlation table; keep submitCloseLesson untouched as the single-lesson pathmemo
P2SsalesShip multi-select lesson types in the Availability planner with computed total window and cert-union eligibility compositionmemo
P2ScoachingPublish a coach-availability v2 minor cleanup that adds the Coaching-owned roster read, documents display-metadata ownership, and reconciles the market_id filter language with the deployed route behaviormemo
P1ScoachingBackfill the missing Jack Dallas booking into coach_lesson_booking and repair the projection path so active reserved or locked lessons appear in availability bookings overlaysmemo
P2MdeliveryAmend contracts/sales-scheduling-surface/README.md Status header to v1.3.0: add §4.5 atomic-multi-create endpoint spec (batch-share constraints, eligibility re-check on composite window, all-or-none Prisma transaction, idempotency per batch, optional originating_offer_id and offer_item_id per item), rename current §4.5 Event surface to §4.6, extend delivery.lesson-hold.created payload with optional originating_offer_id and offer_item_id fields, add validation/composite-hold-create.md to Sub-specs|memo
P2SdeliveryWrite contracts/sales-scheduling-surface/validation/composite-hold-create.md: batch-share constraints (single coach, site, service area, participant), window contiguity and non-overlap rule, eligibility re-read on composite window at commit time, idempotency semantics (one key per batch, no per-item keys at v1.3.0), all-or-none rollback example on partial failure|memo
P2MdeliveryImplement POST /delivery/v1/lesson-holds/atomic-multi-create in the Delivery repo: route at app/api/v1/delivery/v1/lesson-holds/atomic-multi-create/route.ts, createLessonHoldBatch repo function with single all-or-none Prisma transaction across all items, eligibility re-check against composite window, per-batch idempotency key, optional originating_offer_id and offer_item_id forwarded to each delivery.lesson-hold.created event|memo
P2SplatformAmend contracts/credit-reservation-lock/README.md to v1.4.0 per the 2026-05-18 converged composite-offer shape: atomic multi-create reservation endpoint, one Revenue transaction for N reservations and N credit.reserved emits, one Idempotency-Key per batch (no per-item keys), customer.handoff deterministic earliest-lesson_starts_at then credit_reservation_id tie-breaker, validation notememo
P2SplatformBuild /schema endpoint factory + per-section /schema routes per §11.3 (gates §12 acceptance for every section)memo
P2SplatformWire Coaching cost trio compute (coach_cost_per_hour, coach_cost_per_completed_lesson, coach_compensation_total) against the silver rate-column extension Coaching shipped 2026-05-19memo
P2MplatformBuild refresh scheduler: a worker that walks the registry, checks last_successful_refresh_at against max_staleness_minutes, triggers compute for stale metrics independent of pull trafficmemo
P2MplatformWire /corrections write-side detection: recompute-prior-period diff against snapshot in each compute*Metrics function, emit correction event via recordCorrection()memo
P3SplatformSurface upstream_unavailable detection on /health endpoint (currently always returns empty array)memo
P2SplatformWire ad_spend_reconciled cross-warehouse compute in lib/mart/sections/revenue.ts against Growth's campaign_spend_daily silvermemo
P2MplatformWire Coaching utilization metrics (coach_capacity_hours, coach_scheduled_hours, coach_completed_hours, coach_idle_hours, coach_utilization_scheduled, coach_utilization_completed) against availability_template + lesson_booking per Coaching's documented derivationmemo
P2MplatformWire Delivery metrics (lesson_no_show_count, lesson_reschedule_count, dormant_student_count, churn_post_lock_count) against the schema columns Delivery shipped todaymemo
P2MplatformWire Sales cohort triangle (4 metrics) as entity_rows against sales.lead + sales.lead_stage_history (no separate cohort silver needed per Sales' pushback)memo
P2MplatformWire Growth metrics (ad_spend, lead_volume, lead_intake_count, lead_qualified_rate, cpl, cost_per_qualified_lead, source_mix) against the silver Growth landed todaymemo
P2SplatformWire Finance contribution_margin, pnl_summary v0, and cac_per_first_lock as cross-domain composites of what's now livememo
P2SplatformSurface this §9 scoping pushback to the Them OS spec owner via the appropriate external channel and file the response on this thread when it landsmemo
P3XSplatformWithdraw `2026-05-19-platform-coordination-mart-section-proposal` (this memo supersedes it); the §10.9 governance review is no longer being requestedmemo
P2SplatformSurface these two spec gaps to the Them OS spec owner via the appropriate external channel and file the response on this thread when it landsmemo
P2SplatformWithdraw the Path A build commitment (Initiative / InitiativeIndicator / Incident / AttentionItem Postgres tables); not needed — Sguild is not the system of record for thesememo
P2SplatformWithdraw the /coordination/health commitment under §10.3 framing; if Sguild builds a health endpoint later for engineering-coordination purposes, that is a separate project and not part of the mart contractmemo
P2SplatformRedraft the external reply to Them OS, pushing §10 back with the correct framing: mart serves metrics; initiatives are Them-OS-authored state; Sguild does not expose its own coordination repo as forecasting contextmemo
P2SplatformSurface the §9 scoping pushback to the Them OS spec owner via the appropriate external channel and file the response on this thread when it landsmemo
P1SplatformApply the pre-publish registry corrections from this release plan: add Coaching as a consumer for lesson.cancelled and lesson.delivered, and verify the package bundle includes canonical delivery.lesson-hold.* entries with no underscored aliases.memo
P1SplatformPublish the next @sguild/dispatcher freshness package after the registry corrections validate, then bump consuming domains off the stale 2.0.0 bundle.memo
P2MdeliveryBuild the Delivery synthetic local seed pack covering customer CRM defaults, customers, handoffs, lessons, attendance, reservation locks, dispatcher outbox and inbox rows, DLQ samples, and required Platform and Coaching fixture mirrorsmemo
P2SdeliveryFinish Delivery local env safety for the mesh, including .env.local precedence, db target verification for the delivery schema, remote DSN protection, and documented sibling schema requirements for cross-domain fixture tablesmemo
P2MdeliveryAdd Delivery dispatcher proof checks for wired-now lesson and hold producer events plus wired Revenue and Sales consumer events, with credit.funded marked registered-but-no-op until Delivery has a visible local projection assertionmemo
P2SdeliveryPublish Delivery cron inventory and local tick proof for audit-locks, lesson-site-drift, and terminal-lesson-settlement, with terminal settlement defaulting to dry-run in local mesh operationmemo
P2SdeliveryWire Delivery port 3004 bootstrap compatibility, migrations, seed command sequence, and smoke checks into the shared local mesh contract or orchestration helpermemo
P0SdeliveryPublish and implement a Delivery participant resolution or ensure surface keyed by organization_id and person_id for Sales-originated first bookings, returning the Delivery-owned participant_id before Revenue reservation-creatememo
P2MplatformImplement the external-actions runner HTTP-callback path to producer-domain execute endpointsmemo
P2MsalesBuild a Sales synthetic local seed pack for Workbench config, leads, cadence, touches, tasks, notes, callbacks, audits, geography guesses, and close-orchestration correlation rowsmemo
P1SsalesFix Sales local env safety so local or mesh DSNs cannot be overwritten by .env during Prisma CLI and seed commands, and add remote-DSN protection for local setupmemo
P2MsalesAdd Sales dispatcher proof for wired-now producer events and inbox consumers, including event row, fanout, dedup, and Sales-side mutation evidence tied to the same envelopememo
P2SsalesPublish Sales cron tick inventory and synthetic prerequisites for missed callbacks, intake follow-up, and stage 4 reminders, including each route's local mutation posturememo
P2SsalesDocument and verify Sales port 3002 bootstrap with migrations, seed command, readiness smoke, required local secrets, and registered-but-no-op or future-target path labelsmemo
P1SplatformAdd explicit tenant_id to Platform GET /api/bootstrap response for app consumers, preserving tenant_id versus organization_id semantics from ADR-0001.memo
P2SsalesStand up POST /api/quo-contacts in the Sales repo backed by the same Quo client and contact-intake service shape, then have Growth flip its route to a thin proxy for the two-week deprecation window before the Growth-side route deletesmemo
P1ScoachingCoaching patched `contracts/coach-availability/README.v2.md` to v2.1.4 with optional `person_id` and `participant_id`, owner-exception semantics, `protected_trial_followup`, and the rebook-intent dispatcher event familymemo
P1McoachingCoaching implemented local projection support for `delivery.rebook-intent.created`, `delivery.rebook-intent.cancelled`, and `delivery.rebook-intent.converted` as protected intervals with owner exemption in eligibility-by-descriptionmemo
P1ScoachingCoaching applied the `20260527110000_rebook_intent_protected_intervals` migration to the local mesh database and deployed the Coaching repo changes to Vercel productionmemo
P1ScoachingCoaching applied the `20260527110000_rebook_intent_protected_intervals` migration to the production database using the repo `.env` DSNsmemo
P1ScoachingCoaching patched the coach-availability v2 contract to accept optional `person_id` and `participant_id` on eligibility-by-description reads and document the owner exception semantics for active rebook intentsmemo
P1McoachingCoaching consumes active Delivery rebook intents as protected booking intervals and returns `protected_trial_followup` for non-owning customers now that Delivery's payload shape is contract-owned and Platform's dispatcher registry path is readymemo
P1SdeliveryDelivery has pinned `delivery.rebook-intent.created`, `delivery.rebook-intent.cancelled`, and `delivery.rebook-intent.converted` v1 payload schemas under `contracts/lesson-lifecycle` and identified lesson-lifecycle as the owning contractmemo
P1MdeliveryDelivery: land `lesson_rebook_intent` storage and completion-path creation for every completed lesson, proposed at source lesson plus seven days; the row is not a Revenue reservation and not a Delivery lesson holdmemo
P1MdeliveryDelivery: publish the `delivery.rebook-intent.*` event family after Platform registers payload schemas and republishes the dispatcher SDK bundle; until then Delivery persists rows and treats event publication as best-effortmemo
P1SplatformAmend the credit-reservation-lock contract and reservation-create sub-spec so participant_id is optional for Sales-originated reservation create and atomic multi-create, with person_id plus organization_id as the required pre-handoff human contextmemo
P1SplatformPlatform registered `delivery.rebook-intent.created`, `delivery.rebook-intent.cancelled`, and `delivery.rebook-intent.converted`, mirrored the registry into the dispatcher SDK bundle, and published @sguild/dispatcher 2.0.2 after Delivery provided contract-owned v1 payload schemas and confirmed lesson-lifecycle as the owning contractmemo
P1SplatformPlatform published @sguild/dispatcher 2.0.2 with `delivery.rebook-intent.created`, `delivery.rebook-intent.cancelled`, and `delivery.rebook-intent.converted` registered and bundled with the lesson-lifecycle v1.2.0 payload schemasmemo
P1MrevenueUpdate Revenue single reservation-create and atomic multi-create validation to accept absent participant_id, persist null when absent, and attach Delivery-returned Participant or Lesson context later through the hold-created or reconciliation pathmemo
P1SsalesSales will pass the accepted customer identity fields on every close-orchestration Coaching eligibility read, including conflict retry reads, once Coaching publishes the identity-bearing eligibility request shapememo
P2MplatformSteward a coordination ADR resolving per-discipline ownership-transfer signaling under ADR-0014, conditional on Delivery confirming a concrete per-discipline ownership-start gapmemo
P1MplatformPublished platform-geography-snapshot v0.2.0 (geography.market.superseded carrying new_market inline) and landed the Platform emitter plus a market-supersede operation, typecheck and tests greenmemo
P2MrevenueDraft the Revenue-owned Sales-facing ordering API contract (reservation-request backing over credit-reservation-lock; first payment via payment-flow; no ledger or table access); published as sales-ordering-surface v0.1.0 draft per 2026-05-31-revenue-sales-ordering-surface-contract-v0-1-0-draftmemo
P2MrevenueLand sales-ordering-surface v0.2.0 decoupling Lead-close from customer.handoff via optional originating_lead_id, per Sales' v0.1.0 review commit 3ef022amemo
P1SplatformAdd canonical handoff_* Sales mart metric IDs, keep first_lock_* as deprecated aliases during the deprecation window, and update mart browser and public API descriptions to state the Sales handed_off predicatememo
P1SplatformPublish the credit-reservation-lock v2.0.0 amendment that changes active Credit Account scope to Person plus Organization plus Platform Market, updates reservation-create, atomic-multi-create, service-recovery, and event scope notes, and links ADR-0031 after it acceptsmemo
P2MrevenueImplement the committed-close binding step in the Revenue app: after minting the reservation, bind it to the soft-held first lesson through Delivery's synchronous sales-scheduling-surface bind-reservation call before charging and locking, with clean-failure handling on a bind conflict and held-lock compensation if a post-bind step fails, plus the sales-ordering-surface §4.1 clarification that first_lesson_id is a soft-held lessonmemo
P1MrevenueSteward ADR-0033 through Platform, Sales, Delivery, and Portfolio ack checks, then land the accepted contract and implementation plan or file a superseding memo if the ack round changes the designmemo
P2MrevenueCo-author with Delivery the coordination ADR settling the lesson-create-versus-reserve ordering across sales-scheduling-surface, sales-ordering-surface, and credit-reservation-lock, defining the reservation-less soft hold and the close binding a freshly minted reservation to itmemo
P2MrevenueImplement the Revenue close binding step (resolve and mirror the soft-held lesson at reserve, mint the reservation bound to it, lock on the committed motion) plus the credit-reservation-lock and sales-ordering-surface §4.1 amendments naming first_lesson_id as a soft-held lessonmemo
P1MrevenueImplement OrgMarket-scoped active Credit Account resolution in Revenue: one active account per Person plus Organization plus Platform Market, market-resolved reservation-create and atomic-multi-create, first-booking zero-balance account creation in the resolved OrgMarket, and no spend from null-market or different-market accounts after the v2 cutovermemo
P1SrevenuePublish credit.reserved schema_version 2 from Revenue with platform_market_id and migrate producer emissions after credit-reservation-lock v2.0.0 landsmemo
P2SrevenueSupersede or refine Revenue's 2026-05-31 customer-role credit-account invariant memo so the active-account guarantee reads Person plus OrgMarket rather than Person plus Organizationmemo
P2MrevenueDraft a coordination ADR for the Revenue-owned hosted card-capture-and-vault step in the sales-ordering committed close (provider-hosted capture so the raw PAN never touches Sguild servers, vault to a card-on-file, then charge at close), defining the committed-close sequence, the PCI boundary, and the capture and vault failure modes, for Platform PCI and registry review and Sales close-UX reviewmemo
P2LrevenueLand the additive capture collection method on POST /api/v1/orders/credit-purchases and the shared capture-and-charge core (ensure-card-on-file vault then charge via the existing order-charge path) plus the optional customer-name snapshot on the sales-ordering-surface close so Delivery and Sales can build their capture consumers against a stable surfacememo
P1SsalesAdd or confirm a Sales handoff evidence marker that distinguishes normal lock or customer.handoff evidence from late paid-attended evidence for handed_off transitionsmemo
P1SdeliveryDerive the late-funded lesson pending outcome queue or projection label from existing lock and lesson facts and clear it through existing outcome and reschedule pathsmemo
P1MplatformSteward ADR-0035 through Revenue, Sales, Delivery, and Portfolio ack checks, then land the ADR-0033 partial supersession and credit-reservation-lock v2.2.0 contract amendment or file a superseding memo if the ack round changes the designmemo
P1SsalesAlign Sales Lead close and reporting evidence so late-funded reservations close from normal customer.handoff without waiting on Delivery outcomememo
P1SplatformAlign operator_lost_count, cadence_exhausted_count, and churn_pre_lock_count to Sales' confirmed close-reason vocabulary on lead_stage_history, history-grain, with registry and metrics contract notes updatedmemo
P1SplatformFlip the mart handoff predicate from to_stage = 'handed_off' to handoff_evidence IS NOT NULL across the mart sales and finance sections, the metric registry, and the metrics contract notesmemo
P1SplatformVerify the mart open-pipeline stage predicates against live sales.lead values and align them with the corrected live-value taxonomy from 2026-06-11-sales-pipeline-stage-predicate-correctionmemo
P2SsalesRun the ADR-0008 production backfill (restate handed_off rows to terminal, synthesize missing close history rows) as part of the next sales deploymemo