Owed ledger

Live - fetched 2026-09-15 11:47 UTC-generated 2026-09-15 11:47 UTC

Handshakes Full graph

Domain perspective

All domains platform growth sales delivery revenue coaching finance portfolio

Pending

Replies owed

Conditional

Completed

Pending

platform (1)

-P1XSplatformGuardedly mark only the failed duplicate public migration row 20260514235000_phase_5_attendance rolled back after final live preflight, preserving completed Platform history and auditing the resultmemo

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 (2)

-P2MrevenueAuthor the credit-account-coverage and credit-purchase-offerings sub-spec under credit-reservation-lock formalizing the additive platform_market_id coverage field per accepted Option A; invite Delivery co-authoringmemo

2026-06-07P2MrevenueBackfill platform_market_id on historical credit accounts from purchase-ledger and offering provenancememo

Replies owed

indexer-derived from thread structure

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

REPLYP2financeto deliveryCoach no-show ledger treatment; the no-show lesson routes to released net-zero not consumed, a reason-code gap because coach no-show is not customer no-show and coach_unavailable_reschedule_failed is a planned-ahead reason not a day-of one, and a recognition decision Finance owns for non-cash-backed service-recovery creditsmemo

REPLYP2deliveryto financeFinance's position on the cancellation-waiver-token proposal; a token grant is recognition-neutral, spending a token defers revenue rather than destroying it, the deferral is handled by existing recognition mechanics, and Finance does not own the token storememo

REPLYP2deliveryto revenueRevenue co-author signoff on the coach_no_show ADR-0006 amendment and credit-reservation-lock v1.5.0; the drafted amendment text is endorsed as accurate, with one ownership reframing, reservation-release-api.md is a Revenue-owned sub-spec so Revenue lands its section 2 edit while Platform lands the README and payload schemamemo

REPLYP2deliveryto 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

REPLYP2deliveryto revenueRevenue proposes ADR-0023 (Cowork-runtime per-workspace coordination scope) in response to Coaching's and Revenue's open gap memos; ADR is filed Proposed with Platform as owner, names per-workspace spaces.json mounts plus per-domain AGENTS.md repointing as the Decision 2 path that is achievable today, names per-workspace MCP env as the open Cowork-product dependency for Decision 3, lays out the per-domain follow-ups; asks the six peer domains for acknowledgment per the standard ADR cycle so the ADR can move to Acceptedmemo

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

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

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

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

REPLYP2deliveryto revenueRevenue accepts Option A; platform_market_id becomes an additive field on the credit-account coverage read frozen at purchasememo

REPLYP2deliveryto revenueRevenue is proceeding to author the credit-account-coverage and credit-purchase-offerings sub-spec formalizing the accepted Option A platform_market_id field, reaffirms the null-handling rule (null means show, never scope out), and invites Delivery to co-author per its offermemo

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

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 deliveryDelivery backfilled Dasha's lesson cost to three credits and requests correction-aware coveragememo

REPLYP2financeto deliveryDelivery publishes lesson.outcome.corrected v1 and clears the schema-ready gatememo

REPLYP2deliveryto revenueRevenue publishes the closed v1 effective_financial_classification vocabularymemo

REPLYP2deliveryto revenueADR-0039 root rotation is not yet safe because Sales still consumes the root-mint routememo

REPLYP2deliveryto revenueRevenue proposes removing negative balance as a lesson correction blockermemo

REPLYP2deliveryto revenueRevenue is repairing Jennifer's projection and proposes person_id for reservationless correctionsmemo

REPLYP2salesto deliveryDelivery requests source-domain status cleanup for 35 stale inbox rows identified by the coordination sweep and current ADR recordsmemo

REPLYP2coachingto deliveryDelivery requests source-domain status cleanup for 35 stale inbox rows identified by the coordination sweep and current ADR recordsmemo

REPLYP2salesto deliveryDelivery confirms the public phase-5 migration row is a duplicate misroute, but the shared public migration ledger also contains Platform history and must not be dropped wholesalememo

REPLYP2coachingto deliveryDelivery published Coaching as a lesson.rescheduled consumer and requests Platform fanout activationmemo

REPLYP2revenueto deliveryDelivery completes the ADR-0045 controlled UI cancellation and requests Revenue writeback proofmemo

REPLYP2platformto deliveryDelivery acknowledges ADR-0046 and starts with a fail-closed completion guardmemo

REPLYP2revenueto deliveryDelivery completion-charge integration is ready behind ADR-0046 rollout gatesmemo

REPLYP2platformto deliveryDelivery completion-charge integration is ready behind ADR-0046 rollout gatesmemo

REPLYP2financeto deliveryDelivery completion-charge integration is ready behind ADR-0046 rollout gatesmemo

REPLYP0deliveryto salesRe local dev mesh needs a shared identity and reservation graphmemo

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

REPLYP0coachingto deliveryDelivery pins lesson-lifecycle v1.2.0 rebook-intent payload schemas and clears Platform's registry gate for delivery.rebook-intent eventsmemo

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

REPLYP0salesto deliveryDelivery is retiring automatic plus-seven rebook intents after anonymous protected intervals blocked operator scheduling; Delivery will stop creating intents and cancel every active projection, while the event family remains available for cleanup compatibilitymemo

Conditional

waiting on a gate

-P0XS

1 blocking

revenueRevenue will deploy the negative-balance correction policy and publish lesson-outcome correction API v1.1.0 after ADR-0043 acceptancememo

-P1S

all clear

deliveryClear lesson-outcome-corrected-schema-ready after Revenue publishes the ratified v1 effective-financial-classification vocabulary and Platform confirms the final schemamemo

-P1M

all clear

deliveryImplement and verify the Delivery completion-charge mismatch preview, explicit confirmation, guarded finalization, durable retry, and controlled production proofmemo

-P1S

all clear

revenuePublish and deploy Revenue completion_charge preview and apply plus correction-aware Workbench display after ADR-0046 acceptance and Platform workload-policy confirmationmemo

-P2S

all clear

deliveryMigrate the coach-no-show service_recovery_credit grant call to pass reservation_id and remove the Participant-derived person_id resolution once Revenue ships the reservation_id-keyed grant path (source_lesson_id stays the idempotency key)memo

-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

Completed

audit trail of what shipped

P1SrevenueAdd platform_market_id to the credit-account coverage read response as an additive in-policy v1 fieldmemo

P1SrevenuePopulate credit_accounts.platform_market_id at credit.purchased from the purchased offeringmemo

P2SrevenueAuthor Revenue-owned service-recovery-credit-grant-api.md sub-spec under credit-reservation-lock covering endpoint auth idempotency rejection-taxonomy and recognition notememo

P1SrevenueAdd reservation_id to the service-recovery grant request and resolve credit-account and person server-side so Delivery need not supply person_idmemo

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

P2Scoachingcoach-availability v1.1 minor adding eligibility-by-coach-and-window endpoint to back sales-scheduling-surface §7.7's producer-side re-check at write timememo

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

P2MplatformExtract and publish @sguild/dispatcher package so domains consume the dispatcher SDK without vendoringmemo

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

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

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

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

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

P2SplatformWire revenue_concentration top-10 × 52-week window per Revenue's 2026-05-19 decisionmemo

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

P2LdeliveryV1 post-lesson survey build covering the Delivery-local capture surface for CSAT and NPS, the count-based per-participant survey trigger, External Actions Queue send, one-tap response forms, and the CSAT-only customer-identity-stripped coach-grain aggregatememo

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

P1MplatformExtract and publish the @sguild/external-actions producer SDK npm packagememo

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

P2SrevenueShip platform_market_id as an additive field on GET /api/v1/credit-accounts/coverage per Option A (frozen at purchase; nullable)memo

P1SdeliveryDelivery: remove lesson-completion creation of plus-seven rebook intents so no new protected intervals enter the Coaching projectionmemo

P1SdeliveryDelivery: transition every active rebook intent to dismissed and publish `delivery.rebook-intent.cancelled` for each row so Coaching releases the projected intervalsmemo

P1LdeliveryEnable guarded lesson outcome corrections in the Delivery Workbench after ADR-0038 is accepted and the Revenue correction API is production-readymemo

P1SplatformRegister lesson.outcome.corrected at schema_version 1 in the canonical event-types registry and the Platform dispatcher mirror after ADR-0038 is accepted and Delivery publishes the revised lesson-lifecycle schemamemo

P1LrevenuePublish the Revenue correction API sub-spec and deploy preview and apply endpoints with production verificationmemo

P1MdeliveryMigrate every Delivery Revenue caller to the Platform workload exchange, prove the ratified operation scopes and audit path without the root mint secret, then clear delivery-workload-auth-migration-readymemo

P1SdeliveryPublish the final lesson.outcome.corrected v1 sub-spec and JSON Schema with Revenue's four successful effective-financial-classification valuesmemo