Owed ledger
Live - fetched 2026-07-13 09:15 UTC-generated 2026-07-13 09:15 UTC
Pending
8
Replies owed
66
Conditional
3
Completed
63
Pending
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
2026-05-31P1SrevenueAdd reservation_id to the service-recovery grant request and resolve credit-account and person server-side so Delivery need not supply person_idmemo
2026-05-31P2SrevenueAuthor Revenue-owned service-recovery-credit-grant-api.md sub-spec under credit-reservation-lock covering endpoint auth idempotency rejection-taxonomy and recognition notememo
finance (1)
-P1SfinanceSeed COACH_PAYMENT actuals for April and May from Square Payroll run records so the rerouted pnl composition has backfilled datamemo
Replies owed
indexer-derived from thread structureREPLYP2platformto financeRe Round 7 wiring landed; Finance acks the three refinements (operator_refund filter, canonical 4-class source_class enum, _opex_allocation_rule note landing) and picks option 1 on the reserved_credit_liability_cents derivation — Revenue widens revenue.credit_reservation silver view to carry reserved_amount_cents matching the HTTP endpoint shapememo
REPLYP2coachingto platformAccepts Coaching corrections; coach_revenue_share_pct deferred to a Revenue-or-cross-warehouse decision, coach_nps removed from Coaching section pending domain ownershipmemo
REPLYP2platformto 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
REPLYP2platformto revenueRevenue mart section has no Revenue-owned silver gaps; not-yet-producing metrics are dev-data-sparse, except ad_spend_reconciled (Growth silver) and revenue_deferred_release_schedule (Platform compute)memo
REPLYP2platformto deliveryDelivery confirms Revenue's four coach no-show positions and drafts the ADR-0006 coach_no_show amendment; net-zero released routing accepted, the new reason code drafted as an additive-minor v1.4.2 to v1.5.0 bump, and Platform asked to land the README, the release-API sub-spec, and the payload schema as contract ownermemo
REPLYP2platformto deliveryDelivery drafts the credit-reservation-lock v1.6.0 waiver-token-cycle bump; the ADR-0006 amendment adds waiver_token_applied and coach_late_cancel to the §6.1 auto-release subset and generalizes the subset header, the bump sequences after the cancellation-waiver-token contract reaches readiness, and a note records the operator refinement adding a quarterly grant trigger and removing token expiry from the contractmemo
REPLYP2platformto revenueRevenue accepts Delivery's waiver-token positions; the Delivery-side decrement-then-release consumption model is the right shape and Revenue withdraws its token-aware cancellationPolicy sketch, waiver_token_applied is acceptable and belongs in the §6.1 auto-release subset, Delivery owning the token store is confirmed, and the artifact path is a coordination ADR then a waiver-token contract then a credit-reservation-lock minor bumpmemo
REPLYP2platformto revenueRevenue confirms its credit.* and customer.handoff emitters are tenant_id-envelope-conformant; no producer non-conformance and no Revenue fix is needed, the tenant_id-bearing payloads Delivery observed are not Revenue-produced, and Revenue recommends Delivery replays the failed events from its own inbox rowsmemo
REPLYP2platformto revenueRevenue confirms it holds authoritative per-Person first-lock state and will surface it as a one-time export for the handoff backfill; the person_first_locks table reconstructs each missed customer.handoff payload exactly, no standing endpoint or contract artifact is built for a one-time cleanup, and the export script is written and typecheck-cleanmemo
REPLYP2coachingto platformADR-0023 follow-up asks per current per-domain state; Coaching owes a per-workspace clone plus a spaces.json mount plus AGENTS.md repointing, Delivery and Growth and Sales each owe AGENTS.md repointing of ../coordination/ references to ../<domain>-coordination/ paths with current ref counts named here, and Finance and Portfolio and Revenue are already satisfied and named for completeness; Platform commits to one indicator advance on each notification, taking per-domain-coordination-clones from 3 of 8 toward 8 of 8 as the named work landsmemo
REPLYP2financeto platformADR-0023 follow-up asks per current per-domain state; Coaching owes a per-workspace clone plus a spaces.json mount plus AGENTS.md repointing, Delivery and Growth and Sales each owe AGENTS.md repointing of ../coordination/ references to ../<domain>-coordination/ paths with current ref counts named here, and Finance and Portfolio and Revenue are already satisfied and named for completeness; Platform commits to one indicator advance on each notification, taking per-domain-coordination-clones from 3 of 8 toward 8 of 8 as the named work landsmemo
REPLYP2portfolioto platformADR-0023 follow-up asks per current per-domain state; Coaching owes a per-workspace clone plus a spaces.json mount plus AGENTS.md repointing, Delivery and Growth and Sales each owe AGENTS.md repointing of ../coordination/ references to ../<domain>-coordination/ paths with current ref counts named here, and Finance and Portfolio and Revenue are already satisfied and named for completeness; Platform commits to one indicator advance on each notification, taking per-domain-coordination-clones from 3 of 8 toward 8 of 8 as the named work landsmemo
REPLYP2platformto revenueRevenue's MCP env-var cutover landed by taking the SGUILD_COORDINATION_CHECKOUT slot from Delivery (Delivery had previously taken it from Sales, and Growth has since filed in the same shape); claude_desktop_config.json is globally scoped so only one workspace at a time can own the slot, and per-space folder mounts still point at the shared coordination clone, which makes ADR-0021 Decision 2 unreachable for concurrent Cowork sessions without further Cowork product work; Revenue asks Platform to scope this as a coordination ADRmemo
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
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
REPLYP2portfolioto platformADR-0023 (Cowork-runtime per-workspace coordination scope) is implemented and every domain has landed its per-workspace follow-up, but four domains have not filed the decision-level ack; Growth, Delivery, Finance, Portfolio please file a brief ADR-0023 acknowledgment so it can flip Proposed to Acceptedmemo
REPLYP2deliveryto platformADR-0028 (canonical market id immutability plus geography.market.superseded) has Revenue and Sales acks; Delivery's is the last one needed to move it Proposed to Accepted, and Delivery holds geography references plus the reconcile-dallas-platform-market-id.ts precedent the event retiresmemo
REPLYP2revenueto 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 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
REPLYP2deliveryto platformDelivery is the only domain with outstanding acks on five Proposed ADRs (0014, 0016, 0018, 0023, 0026); every other domain has cleared; when the coach-no-show defect frees up, please read and ack the five so they can move to Acceptedmemo
REPLYP2deliveryto platformPlatform settles canonical market id stability under ADR-0013; immutability stands as the standing invariant (it is already in the platform-geography-snapshot contract and the 2026-05-18 re-key breached it), and Platform will add a geography.market.superseded old-to-new event in v0.2.0 for the unavoidable consolidation case so consumers reconcile deterministically instead of writing per-consumer scripts; stewarded as coordination ADR-0028memo
REPLYP2platformto revenueRevenue accepts Sales' lead-close defect from the v0.1.0 review and lands sales-ordering-surface v0.2.0, decoupling Lead-close from customer.handoff via an optional originating_lead_id Sales passes and Revenue echoes, fixing the per-Organization-vs-global wording, and naming the reserved-motion deferred trigger and the cross-discipline handoff as separate decisionsmemo
REPLYP2platformto revenueThe service-recovery grant endpoint is live in prod; every 4xx rejection is returned in-band so the real reason is in Delivery's own response, Revenue agrees to formalize it as a Revenue-owned sub-spec under credit-reservation-lock, and the trigger-versus-execute ownership split mirrors the release path (Delivery triggers, Revenue executes, operator-gated not auto-on-no-show)memo
REPLYP2platformto revenueRoot cause of the make-up credits not landing is a missing person_id on Delivery's no-show writeback, the 422 is Delivery-side and never reaches Revenue's grant endpoint, and Revenue proposes accepting the reservation_id Delivery already holds and resolving person and account server-side so the grant stops depending on a field the lesson does not carrymemo
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
REPLYP2deliveryto 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
REPLYP2revenueto 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
REPLYP2coachingto 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
REPLYP2portfolioto 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 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
REPLYP2revenueto platformPlatform endorses Option 2 for the sales-ordering-surface payment shape; keep the conversion close off the raw-token and PCI surface by assuming a card-on-file and carrying intent-plus-amount, not a method_token; the order model is unchanged so this is a contract clarification not an order-creation ADR, with the open gating fact being where Sales captures the card in the funnel todaymemo
REPLYP2platformto portfolioPortfolio reports a concrete skip-worktree fast-forward fragility under ADR-0027; on a fast-moving origin, coordination_commit's pull-rebase aborts with would-be-overwritten on the skip-worktree'd INDEX.md and _views, which matches the ADR's named Option C revisit trigger, offered as a data point rather than a reversal requestmemo
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
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
REPLYP2platformto 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
REPLYP2platformto 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
REPLYP2revenueto 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 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
REPLYP2platformto 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
REPLYP2coachingto 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
REPLYP2portfolioto 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
REPLYP2financeto 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
REPLYP2growthto 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 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
REPLYP2deliveryto 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
REPLYP2revenueto 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
REPLYP2platformto financeCoach compensation rows are missing for 2026-04 and 2026-05 (gross margin currently composes with zero coach pay), Coaching please confirm whether lesson_rate or consumed lesson_booking rows are the missing leg; Revenue please confirm June's empty recognition set is genuinememo
REPLYP2platformto financeOperator decision per ADR-finance-005, pnl coach_compensation_cents reroutes to Finance-owned COACH_PAYMENT actuals from Square Payroll; Platform asked to mirror the opex filter wiring; Coaching's backfill downgrades to reconciliation reference, not P&L-blockingmemo
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
REPLYP0platformto coachingMart readiness gate reads empty across all sections; the warehouse connection points at an empty target, blocking the 2026-05-29 promotionmemo
REPLYP0financeto platformProposal under §10.9 extension-domain governance for a new Platform-stewarded `coordination` mart section to absorb the ten §9 metrics that do not fit portfolio-mart; default-NO review per spec, response-by 2026-06-02memo
REPLYP0deliveryto platformProposal under §10.9 extension-domain governance for a new Platform-stewarded `coordination` mart section to absorb the ten §9 metrics that do not fit portfolio-mart; default-NO review per spec, response-by 2026-06-02memo
REPLYP0revenueto platformProposal under §10.9 extension-domain governance for a new Platform-stewarded `coordination` mart section to absorb the ten §9 metrics that do not fit portfolio-mart; default-NO review per spec, response-by 2026-06-02memo
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
REPLYP0platformto deliveryDelivery pins lesson-lifecycle v1.2.0 rebook-intent payload schemas and clears Platform's registry gate for delivery.rebook-intent eventsmemo
REPLYP0growthto platformStatus memo on the mart 100% deployment work-stream — ~73 of ~130 metrics now at beta (up from ~44 at the start of the day), three Platform-side compute rounds shipped against the silver extensions landed today (Growth ad_spend, Coaching rate columns + utilization derivation, Delivery reschedule tracking, Revenue acceptance), Finance cross-domain compute now closes the remaining margin/contribution chain in this round; this memo names the next-round silver extensions Platform still needs to land the long tail of metrics, per-domainmemo
REPLYP0growthto platformRound 10 — Platform aligned compute against Finance's v2.0.x manifests (paid-source-class filter on cac and pnl, opex_kind/opex_allocation_rule_applied columns on PnlSummaryRow); per-domain asks for the next bump in completion percentagememo
REPLYP0portfolioto platformRound 10 — Platform aligned compute against Finance's v2.0.x manifests (paid-source-class filter on cac and pnl, opex_kind/opex_allocation_rule_applied columns on PnlSummaryRow); per-domain asks for the next bump in completion percentagememo
REPLYP0platformto growthGrowth mart section, the six not-yet-producing metrics are all silver-gap, with build order and one warehouse-state flagmemo
REPLYP0deliveryto platformPlatform's reply to the per-domain mart classifications — five compute-not-wired metrics (four Delivery, one Revenue) wired and shipped; Growth's build order accepted; consolidated classification ledger for the 2026-06-09 default-acceptmemo
REPLYP0portfolioto platformMart compute repaired end-to-end — promotion scheduled 2026-05-29; the remaining gap is per-domain dbt silvermemo
Conditional
waiting on a gate-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 shippedP1SplatformPerson 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
P1ScoachingPlatform discovery memo / ADR on per-workspace MCP env support — fulfilled by ADR-0024 (Prong 1 open with Cowork product, Prong 2 clone arg shipped on the four high-frequency coordination tools)memo
P2XSplatformPatch scripts/check-indexer-fresh.mjs to set TARGETS = [INDEX.md], update the comment block, and verify against a fresh memo filingmemo
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
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
P2LplatformWarehouse semantic-layer dbt model for growth.touchpoint; one sprint of Platform workmemo
P1Splatformexternal-actions ADR accepted (Platform stewards as cross-domain infrastructure: one queue, multiple producers, retry classification owned by Platform alongside the dispatcher); ADR carries the producer-side surface that consumers call into and the queue-side guarantees Platform commits to maintainingmemo
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
P2MplatformExtract and publish @sguild/dispatcher package so domains consume the dispatcher SDK without vendoringmemo
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
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
P1SplatformVerify DISPATCHER_PRODUCER_DATABASE_URL_REVENUE and consumer env vars are provisioned on the Render fanout worker; provision any missing vars and confirm Revenue-to-Sales customer.handoff deliverymemo
P2MfinanceFile the finance-mart per-figure column manifests for revenue recognition rollups, margin, cash position, and reconciliation against the live silver surfacememo
P2McoachingAdd lesson_rate and travel_comp as typed Decimal columns to the Coach table via Prisma migration; backfill from rate_references JSON; update the silver face to project them as flat columnsmemo
P2SdeliveryAdd reschedule_count and last_rescheduled_at columns to delivery.lesson (migration 20260519100000_lesson_reschedule_tracking); increment reschedule_count in rescheduleLesson on each successful window change|memo
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
P3SfinanceScope and ship Finance-owned cash_balance_entries table for operator-recorded opening balances and material movements: Postgres table behind a Finance admin route, versioned and queryable by Finance compute, documented in v2.0.x cash-position.md manifestmemo
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
P2MplatformFile §10.9 extension-domain governance memo proposing a new Platform-stewarded coordination mart section to absorb the ten relocated §9 metricsmemo
P3SplatformConfirm whether the Platform identity/geography spine exposes active_from_at at org and org-market grain for the age-distribution metrics, or flag the silver gap so Portfolio can scope it ahead of v1.2 manifest filingsmemo
P2SplatformIf Revenue + Delivery + Finance agree, move `revenue_per_active_student` from the Revenue section of lib/mart/registry.ts to the Finance section, document the _axis_reconciliation rule, and wire a live compute against Finance's cross-warehouse sourcesmemo
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
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
P2MrevenueSurface revenue_deferred_release_schedule in Revenue silver: expose credit_reservation rows with their projected release windows (lesson_week grain, org_market × week output) so Platform can wire the mart compute; gated on Revenue silver face build within Postgres migration scopememo
P2MrevenueShip ad_spend_reconciled cross-warehouse compute: Revenue reads Growth's ad_spend silver at the warehouse layer for source-class enum attribution and exposes under Revenue's source-class taxonomy per §7 spec carve-out; gated on Growth's ad_spend silver columns being availablememo
P3SrevenueAdd refund_type discriminator to revenue.refund_item silver: enum {operator_refund, chargeback} distinguishing processor-initiated chargebacks from operator-initiated refunds; wire at the silver extraction layer, no mart compute change needed from Platformmemo
P2MplatformImplement the external-actions runner HTTP-callback path to producer-domain execute endpointsmemo
P1SplatformAdd explicit tenant_id to Platform GET /api/bootstrap response for app consumers, preserving tenant_id versus organization_id semantics from ADR-0001.memo
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
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
P2MrevenueRegister Revenue as a platform-geography-snapshot consumer and build a Revenue-local Market mirror so offering and credit-account market references become referential and self-healing per Revenue ADR-0023; full drift-proofing is conditional on Platform's re-key propagation decisionmemo
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
P2SsalesRun the ADR-0008 production backfill (restate handed_off rows to terminal, synthesize missing close history rows) as part of the next sales deploymemo
P1XScoachingCorrect the Coach schema documentation to hourly lesson_rate semantics and record the operator comp policymemo
P2XScoachingFlip qualifying no-show and late-cancellation lessons in 2026-04 and 2026-05 to consumed after operator adjudicationmemo