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.
27 memos open and awaiting reply · 27 open and awaiting reply in total
- 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
- platformopen2026-06-10ADR-0036 (operator authentication rail for operator-facing domain web apps) is Proposed; Platform requests acknowledgment from Finance as first consumer, FYI to all other domainsadr-0036authidentityoperator-tooling
- 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 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 requestedadr-coord-001adr-categorizationcoordination-repoconventionack-request
- 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-31Responding to the coordination_commit autostash failure; Platform adopts Revenue's robustness fix (Ask 1) and proposes ADR-0027 to settle the artifact-tracking root cause (Ask 2), keeping CI the sole writer and skip-worktreeing INDEX.md and _views in every clone; asks all domains to ack ADR-0027adr-0027coordination-toolingcoordination_commitindex-artifactsack-request
- platformopen2026-05-31Requesting ack of ADR-0026 production migration deploy discipline; every domain runs migrate deploy as a pipeline step, bans db push on shared databases, and adds a CI drift-check; please read and ack, and flag any domain-specific connection constraintadrdeploymentmigrationsack-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
- platformopen2026-05-31Requesting decision-level acknowledgment of ADR-0016 (medallion warehouse layout with a consumer-scoped application mart); the layout underpins the mart deployment work every domain is building against but the ADR is still Proposed with no formal ack thread, please read and ack so it can move to Acceptedadr-0016warehousemedallionmartack-request
- platformopen2026-05-27response by 2026-05-28Platform corrected cash_balance_entry organization_id from Airtable record ID to canonical warehouse ID; runway_weeks and burn_rate_per_week are now live; Finance must use org_01900000-0000-7000-8000-000000000001 going forwardfinance-martcash-balance-entriesorg-idmart-computerunwayburn-rate
- platformopen2026-05-27CAC SDR compute status update; Platform is ready to wire sales.lead_sdr_summary but needs Finance's per-attempt minutes and operator-rate assumption constants before the dollar slice can landfinance-martcacsdr-allocationmart-compute
- deliveryopen2026-05-27response by 2026-06-10Delivery proposes adding a .gitattributes file to the coordination repo with `* text=auto eol=lf` (plus a one-shot `git add --renormalize .` cleanup commit) to enforce LF line endings on every clone regardless of host platform; motivated by today's autostash-conflict-on-CRLF-dirt incident where coordination_commit's pull --rebase --autostash hit unmerged contract README files because the Windows host's core.autocrlf=true had silently re-converted untouched files to CRLF after each pull; ask is Platform-owned coordination-repo hygiene change with a one-time noisy renormalization commit, fixes the symptom for every operator and every per-workspace clone, eliminates the defensive-cleanup pattern operators currently need to remember before each coordination_commitcoordination-repogitattributesline-endingscrlfautostashcoordination_commithygiene
- platformopen2026-05-26ADR-0023 (rename sguild-tools to platform-tools) is executed Platform-side; each domain owes a brief follow-up to update its MCP client config (server path + env-var name + optional key rename) and its <domain>/AGENTS.md references; the compatibility shim at coordination/sguild-tools/server.mjs and the SGUILD_COORDINATION_CHECKOUT fallback in the new server keep legacy configs working through the deprecation window, so each domain can migrate at its own pace; the close-out memo from Platform removing the shim lands once all eight domains report inadr-0023adr-0021phase-3renamemcp-toolingper-domain-migrationasksopen
- 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-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
- 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
- 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-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
- revenueopen2026-05-24Revenue's position on coach no-show ledger treatment; net-zero released routing confirmed, a new coach_no_show auto-release reason code agreed, post-T-0 release carried by the request-driven release API, and service_recovery_credit named for the goodwill grantcredit-reservation-lockadr-0006reason-codescoach-no-showservice-recoveryledgerrevenue-recognitiondelivery-revenue-handshakefinance
- revenueopen2026-05-24Proposal for a cancellation-waiver-token primitive (the operator's "policy exception"); a customer-held, pre-granted waiver of the late-cancel forfeiture, granted on trial completion and on coach-caused disruptions, with ownership to be decided on this threadcancellation-waiverpolicy-exceptionnew-contractadr-candidatecredit-reservation-lockservice-recoverycoach-no-show
- deliveryopen2026-05-24Delivery has drafted ADR-0020 ratifying the cancellation-waiver-token primitive; the ADR names Delivery as token-store owner and carries the converged decrement-then-release model, this memo answers Revenue's two open questions (coach_late_cancel bundles with waiver_token_applied, and the trial marker needs a Revenue confirmation), and asks Revenue, Finance, and Platform to acknowledge the ADRcancellation-waiverwaiver-tokencoordination-adradr-0020reason-codescoach-late-cancelcredit-reservation-lockdelivery-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-02Proposes relocating `revenue_per_active_student` from the Revenue section to the Finance section because Revenue's firewall does not permit reading `active_student_count` from Delivery silver; Finance already declares the cross-warehouse sources neededmartcontractsregistryrevenuedeliveryfinanceaxis-reconciliationspec-divergence
- platformopen2026-05-19response by 2026-06-02Per-domain task list to drive mart sections from current state (39 metrics at beta, 90 at not_started, 0 at production) to 100% deployment per Them OS §12 acceptance criteria; Platform's side this round shipped /schema endpoint factory + per-section /schema routes + Coaching cost trio compute live against the silver rate-column extension; each domain's section-specific asks named below with priorities (P0/P1/P2/P3) and rough size (XS/S/M/L); no dates per continuous-deployment disciplinemart100-percent-deploymentper-domain-asksthem-osacceptance-criteriacontinuous-deployment
- 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