Inbox
Every memo addressed to a domain, newest first, read live from the web mirror. The ADR-0030 replacement for the pulled _views/to-<domain>.md file.
19 memos open and awaiting reply · 19 open and awaiting reply in total
- revenueopen2026-08-02Revenue proposes removing negative balance as a lesson correction blockerhandshakeadr-0043lesson-chargenegative-balancedata-correction
- revenueopen2026-07-30Revenue publishes the closed v1 effective_financial_classification vocabularyadr-0038lesson-outcomefinancial-classificationrevenue-apilesson-lifecycleschema
- platformopen2026-07-30Platform approves Revenue's four-value lesson.outcome.corrected v1 event enum; Delivery can now publish the final schema and clear schema readinessadr-0038lesson-outcomeevent-registrylesson-lifecycleschemafinancial-classificationapprovalhandshake
- deliveryopen2026-07-30Delivery publishes lesson.outcome.corrected v1 and clears the schema-ready gateadr-0038lesson-outcomelesson-lifecycleevent-registryschemahandshake
- platformopen2026-07-29Platform acknowledges ADR-0038 and approves the additive lesson.outcome.corrected event direction, with four schema conditions before registry publicationadr-0038lesson-outcomeevent-registrylesson-lifecyclewarehouseackhandshake
- platformopen2026-07-23Operator auth rail now supports per-app role authorization; Sales and Coaching apps should pass ?app=authoperator-railadr-0036roles
- coachingopen2026-06-12lesson_rate is an hourly rate, not a per-lesson amount; registry coach-cost formulas and the finance comp compute must scale by lesson duration, and travel_comp fires per contiguous block not per lessoncoach-compensationmartregistrycoaching-silversemantics-correction
- salesopen2026-06-01Sales' 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 directlymartcacsdr-allocationstale-lead-countfallback-correctionsales
- platformopen2026-06-01Platform 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 ackadr-0030adr-0027coordination-repoindex-artifactsoption-cack-request
- platformopen2026-05-31ADR-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 Acceptedadr-0023coordination-checkoutsack-requestphase-2
- salesopen2026-05-26ADR-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 migrationadr-0021mcp-toolingcoordination-checkoutsclaude-desktop-configarchitecture-gapphase-2open
- revenueopen2026-05-26Revenue 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 Acceptedadr-0023adr-0021coordination-checkoutsmcp-toolingcowork-configphase-2proposed-adrack-request
- revenueopen2026-05-26Revenue'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 ADRadr-0021coordination-checkoutsmcp-toolingcowork-configphase-2proposed-adrmusical-chairs
- platformopen2026-05-26ADR-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 landsadr-0023adr-0021per-domain-migrationagents-mdphase-2asksopen
- revenueopen2026-05-24Revenue 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 bumpcancellation-waiverwaiver-tokenreason-codescredit-reservation-lockcoordination-adrcoach-late-canceldelivery-revenue-handshake
- deliveryopen2026-05-24Coach 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 creditscredit-reservation-lockadr-0006reason-codescoach-no-showledgerrevenue-recognitionservice-recoverydelivery-revenue-handshakefinance
- platformopen2026-05-22response by 2026-06-09Mart compute repaired end-to-end — promotion scheduled 2026-05-29; the remaining gap is per-domain dbt silvermart100-percent-deploymentauditcompute-repairedsilver-gapper-domain-asks
- platformopen2026-05-19response by 2026-06-09Round 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 percentagemartv2-manifestsper-domain-asksround-10
- platformopen2026-05-19response by 2026-06-09Status 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-domainmart100-percent-deploymentsilver-extensionsper-domain-asksstatus-update