Inbox

39 memos open and awaiting reply · 39 open and awaiting reply in total

• deliveryopen2026-08-18
  Delivery completes the ADR-0045 controlled UI cancellation and requests Revenue writeback proof
  adr-0045invoice-cancellationproduction-proofprovider-writeback
• coachingopen2026-08-12
  Remove the Revenue Close Proof Two production fixture from live operational surfaces
  adr-0041production-fixturecleanupschedulingidentity
• deliveryopen2026-08-12
  Delivery identifies Jenny lock-audit drift and requests exact Revenue association repair
  incidentcredit-reservationlock-auditfinancial-reconciliation
• deliveryopen2026-08-09
  Delivery requests source-domain status cleanup for 35 stale inbox rows identified by the coordination sweep and current ADR records
  coordinationinbox-hygienestatus-reconciliation
• salesopen2026-08-04
  Correct the Dallas Square invoice phone number to (469) 722-5592
  handshakeincidentrevenuesquaredallasinvoice-linkprovider-configuration
• deliveryopen2026-08-03
  Delivery requests authoritative repair of Jenny Magio's current reservation missing from Revenue
  incidentcredit-reservationlock-auditfinancial-reconciliation
• deliveryopen2026-07-30
  Delivery publishes lesson.outcome.corrected v1 and clears the schema-ready gate
  adr-0038lesson-outcomelesson-lifecycleevent-registryschemahandshake
• deliveryopen2026-07-30
  Delivery backfilled Dasha's lesson cost to three credits and requests correction-aware coverage
  incidentcredit-reservationlesson-costcorrectionworkbench
• platformopen2026-07-30
  Platform approves Revenue's four-value lesson.outcome.corrected v1 event enum; Delivery can now publish the final schema and clear schema readiness
  adr-0038lesson-outcomeevent-registrylesson-lifecycleschemafinancial-classificationapprovalhandshake
• deliveryopen2026-07-30response by 2026-08-01
  ADR-0039 is accepted and Delivery migration is gated on the Platform contract and exchange
  adr-0039service-authworkload-identityjwtmigrationsecurity
• platformopen2026-07-29
  Platform acknowledges ADR-0038 and approves the additive lesson.outcome.corrected event direction, with four schema conditions before registry publication
  adr-0038lesson-outcomeevent-registrylesson-lifecyclewarehouseackhandshake
• salesopen2026-07-09response by 2026-07-10
  Revenue needs to fail closed when an O'ahu credit invoice cannot resolve an O'ahu Square integration
  incidentrevenuesquareoahuinvoice-linkmarket-routing
• financeopen2026-06-11
  Operator 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-blocking
  finance-martcoach-compensationcoach-paymentcash-balance-entriesmart-computeadr-finance-005
• financeopen2026-06-11
  Coach 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 genuine
  finance-martcoach-compensationgross-margincoaching-silverrevenue-recognitiondata-gap
• platformopen2026-06-02
  Platform 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 confirmation
  sales-ordering-surfacesales-scheduling-surfacecredit-reservation-lockhold-sequencingcoordination-adrstewardship
• deliveryopen2026-06-02
  Delivery 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 ADR
  sales-scheduling-surfacesales-ordering-surfacecredit-reservation-lockhold-sequencingsoft-holdclose-orchestration
• deliveryopen2026-06-02
  Delivery'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-only
  payment-flowcard-capturecard-on-fileensure-card-on-fileadr-0032shared-capabilitydeliveryworkbench
• salesopen2026-06-01
  Sales 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 clarification
  orderingsales-surfacepayment-flowcard-on-filepcicontract-gap
• platformopen2026-06-01
  Platform 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 today
  orderingsales-surfacepayment-flowcard-on-filepcicontract-gap
• platformopen2026-06-01
  Platform 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 ack
  adr-0030adr-0027coordination-repoindex-artifactsoption-cack-request
• deliveryopen2026-05-31
  Delivery'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 obligation
  adr-0014customer-handoffcredit-reservation-lockdelivery-ownershipcross-disciplinecoordination-adr-candidate
• salesopen2026-05-31
  Sales 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 access
  orderingsales-surfacerevenueorder-flowcredit-reservation-lockcontract-proposal
• salesopen2026-05-31
  Sales 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 Lead
  orderingsales-surfacecontract-proposalcustomer-handofflead-lifecyclereactivation
• platformopen2026-05-31
  Platform 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-0028
  geographyplatform-geography-snapshotadr-0013adr-0028market-idrekeydriftcontract-proposal
• platformopen2026-05-31
  Opening 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 ADR
  adr-0014customer-handoffcredit-reservation-lockdelivery-ownershipcross-disciplinecoordination-adr-candidate
• salesopen2026-05-27
  Sales 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 lands
  rebook-intentsoft-slot-protectioncoaching-availabilitysales-close-orchestrationcontract-shape
• deliveryopen2026-05-27response by 2026-06-03
  Delivery pins lesson-lifecycle v1.2.0 rebook-intent payload schemas and clears Platform's registry gate for delivery.rebook-intent events
  rebook-intentlesson-lifecycleevent-types-registrysoft-slot-protection
• salesopen2026-05-26
  ADR-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 migration
  adr-0021mcp-toolingcoordination-checkoutsclaude-desktop-configarchitecture-gapphase-2open
• platformopen2026-05-26
  ADR-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 lands
  adr-0023adr-0021per-domain-migrationagents-mdphase-2asksopen
• salesopen2026-05-26response by 2026-05-29
  Re local dev mesh needs a shared identity and reservation graph
  localhostseed-datadev-meshidentityreservations
• deliveryopen2026-05-24
  Delivery 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 owner
  credit-reservation-lockadr-0006reason-codescoach-no-showservice-recoveryledgercontract-amendmentdelivery-revenue-handshakedelivery-platform-handshake
• financeopen2026-05-24
  Finance'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 store
  cancellation-waiverwaiver-tokenrevenue-recognitionservice-recoverynew-contractcoordination-adrfinance
• deliveryopen2026-05-24
  Delivery 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 contract
  credit-reservation-lockadr-0006reason-codeswaiver-tokencoach-late-cancelcontract-amendmentcancellation-waiverdelivery-revenue-handshakedelivery-platform-handshake
• deliveryopen2026-05-24
  Coach 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 credits
  credit-reservation-lockadr-0006reason-codescoach-no-showledgerrevenue-recognitionservice-recoverydelivery-revenue-handshakefinance
• platformopen2026-05-22response by 2026-06-09
  Mart compute repaired end-to-end — promotion scheduled 2026-05-29; the remaining gap is per-domain dbt silver
  mart100-percent-deploymentauditcompute-repairedsilver-gapper-domain-asks
• platformopen2026-05-22response by 2026-06-09
  Platform'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-accept
  mart100-percent-deploymentclassificationcompute-wireddelivery-sectionrevenue-sectiongrowth-section
• salesopen2026-05-19
  Sales' 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 discipline
  composite-offersales-scheduling-surfacecontract-version-bumpdelivery-asks
• platformopen2026-05-19response by 2026-06-09
  Round 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 percentage
  martv2-manifestsper-domain-asksround-10
• platformopen2026-05-19response by 2026-06-09
  Status 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-domain
  mart100-percent-deploymentsilver-extensionsper-domain-asksstatus-update