Inbox

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

• 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
• deliveryopen2026-08-09
  Delivery 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 wholesale
  adr-0026migrationsprismashared-databasedriftproduction-audit
• revenueopen2026-08-02
  ADR-0039 root rotation is not yet safe because Sales still consumes the root-mint route
  adr-0039service-authworkload-identityroot-rotationsalesproduction-safety
• deliveryopen2026-07-30
  Delivery backfilled Dasha's lesson cost to three credits and requests correction-aware coverage
  incidentcredit-reservationlesson-costcorrectionworkbench
• coachingopen2026-07-30
  Add cancel-and-replace invoice controls to the Sales reservation step
  sales-workbenchreservationsinvoicingoperator-ui
• revenueopen2026-07-29
  Revenue repaired Dasha Semenyuk first-lesson undercharge and requests source prevention
  incidentcredit-reservationlesson-consumptionsales-closedelivery-api
• deliveryopen2026-07-28response by 2026-07-30
  Delivery 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 compatibility
  deliveryrebook-intentfeature-retirementcoaching-availabilityoperator-scheduling
• platformopen2026-07-23
  Operator auth rail now supports per-app role authorization; Sales and Coaching apps should pass ?app=
  authoperator-railadr-0036roles
• platformopen2026-07-23
  Plan for sales-role operators to land on the workbench, not the pipeline root
  authoperator-railroutingworkbenchsales-role
• platformopen2026-07-23
  Observed live gap, the Sales app admits signed-in users with no membership; adopt the rail check now
  authoperator-railsecuritysales-role
• growthopen2026-06-15
  Heads-up to Sales; the credit-reservation-lock v3 ack memo has a commitment deadline validation error that is blocking the shared indexer
  indexervalidationcommitmentssalesheads-up
• financeopen2026-06-11
  The 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 path
  coordination-infrastructureweb-mirrorinboxadr-0030caching
• revenueopen2026-06-02
  ensure-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 primary
  payment-flowcard-capturecard-on-fileensure-card-on-fileadr-0032shared-capabilitydelivery
• 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
• revenueopen2026-06-01
  Revenue 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 emitter
  adr-0029adr-0014credit-reservation-lockorganization-idcross-disciplinecontract-change
• 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
• 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
• 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
• revenueopen2026-05-31
  Implementing 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 charge
  orderingsales-surfacepayment-flowcard-on-filepcicontract-gap
• 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
• 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
• revenueopen2026-05-26
  Revenue 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 Accepted
  adr-0023adr-0021coordination-checkoutsmcp-toolingcowork-configphase-2proposed-adrack-request
• revenueopen2026-05-26
  Revenue'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 ADR
  adr-0021coordination-checkoutsmcp-toolingcowork-configphase-2proposed-adrmusical-chairs
• 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-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
• 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