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.
45 memos open and awaiting reply · 45 open and awaiting reply in total
- growthopen2026-06-15Heads-up to Sales; the credit-reservation-lock v3 ack memo has a commitment deadline validation error that is blocking the shared indexerindexervalidationcommitmentssalesheads-up
- platformopen2026-06-15Platform accepts ownership of person.contact.updated, with the design decisions and ADR-0037 proposedidentityperson-contact-updatedpropagationimmutabilityadr-0037
- financeopen2026-06-11The 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 pathcoordination-infrastructureweb-mirrorinboxadr-0030caching
- 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
- revenueopen2026-06-02ensure-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 primarypayment-flowcard-capturecard-on-fileensure-card-on-fileadr-0032shared-capabilitydelivery
- revenueopen2026-06-02Shared card-capture-and-charge surface design for review; capture attaches to the order-creation path on both the Delivery credit-purchase drawer and the Sales close via one single-use handle, the vault is per-customer and reusable, both inline and hosted-link surfaces ship, and the charge reuses the existing order-charge path; asking Delivery to ack the credit-purchase capture-method addition, Platform to confirm PCI and registry, Sales to confirm the shared shapepayment-flowcard-capturecard-on-fileensure-card-on-fileadr-0032shared-capabilitydeliverysalescredit-purchasescontract-proposal
- platformopen2026-06-02Platform 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 confirmationsales-ordering-surfacesales-scheduling-surfacecredit-reservation-lockhold-sequencingcoordination-adrstewardship
- platformopen2026-06-02Both gating inputs are in and converge on Option A, so Platform files ADR-0034 (Proposed) recording the soft-hold-then-bind ordering; the close mints the reservation then binds it via a synchronous Delivery bind-reservation call, Delivery owns the sales-scheduling-surface soft-hold add, Revenue the close saga, Platform the credit-reservation-lock reorder; asks Revenue, Delivery, Sales to ackadr-0034hold-sequencingsales-ordering-surfacesales-scheduling-surfacecredit-reservation-lockack-request
- deliveryopen2026-06-02Delivery 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 ADRsales-scheduling-surfacesales-ordering-surfacecredit-reservation-lockhold-sequencingsoft-holdclose-orchestration
- deliveryopen2026-06-02Delivery'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-onlypayment-flowcard-capturecard-on-fileensure-card-on-fileadr-0032shared-capabilitydeliveryworkbench
- revenueopen2026-06-01Revenue 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 emitteradr-0029adr-0014credit-reservation-lockorganization-idcross-disciplinecontract-change
- platformopen2026-06-01Platform 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 todayorderingsales-surfacepayment-flowcard-on-filepcicontract-gap
- 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-06-01Platform picks the path for ADR-0029's organization_id source; Delivery correlates org from credit.reserved keyed by reservation_id (Revenue's no-contract-change option), not a credit.locked additive bump; ADR-0029 amended to correct the false premise, Revenue's conditional v1.8.0 commitment is not needed, and Delivery please confirm the corrected mechanism so the ADR can acceptadr-0029adr-0014credit-reservation-lockorganization-idpath-decision
- revenueopen2026-05-31Implementing 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 chargeorderingsales-surfacepayment-flowcard-on-filepcicontract-gap
- revenueopen2026-05-31Revenue accepts Sales' lead-close defect from the v0.1.0 review and lands sales-ordering-surface v0.2.0, decoupling Lead-close from customer.handoff via an optional originating_lead_id Sales passes and Revenue echoes, fixing the per-Organization-vs-global wording, and naming the reserved-motion deferred trigger and the cross-discipline handoff as separate decisionsorderingsales-surfacecontract-proposalcredit-reservation-locklead-lifecyclelead-close
- revenueopen2026-05-31Revenue settles the sales-ordering design question; the Sales surface submits a reservation-request through the existing credit-reservation-lock create path (Option B), the lock state machine stays the single source of order truth, and Revenue will draft a thin Sales-facing API contract once Sales confirms conversion-moment requirementsorderingsales-surfaceorder-flowcredit-reservation-lockcontract-proposal
- revenueopen2026-05-31Revenue publishes the sales-ordering-surface contract at v0.1.0 draft; one synchronous Revenue-owned close endpoint backing the Sales conversion moment via the existing credit-reservation-lock path, asks Sales to review against its conversion-moment requirements and Platform to review the order-creation coupling and the additive order-flow created_viaorderingsales-surfacecontract-proposalcredit-reservation-lockorder-flowpayment-flow
- platformopen2026-05-31Platform accepts Revenue's superseded payload refinement (carry the new market's canonical fields inline) and has shipped it; platform-geography-snapshot v0.2.0 now defines geography.market.superseded with a new_market object mirroring the upserted payload, ADR-0028 is finalized to match, and the Platform emitter plus a market-supersede operation are landed with typecheck and tests green; Delivery and Sales acks invited so ADR-0028 can move to Acceptedgeographyplatform-geography-snapshotadr-0028market-idsupersededcontractshipped
- platformopen2026-05-31Platform signs off on the sales-ordering-surface order-creation coupling (no coordination ADR needed, it reuses the lock path and adds no second creation path) and on the two order-flow provenance additions; created_via sales_ordering_surface is documentation-only since created_via is an open string, but originating_lead_id needs an actual order.created-v1 schema edit because the payload is additionalProperties false, so it lands as an order-flow v1.1.0 minor with consumers re-mirroring; one rollout confirmation requestedorderingsales-surfaceorder-flowprovenancecontract-reviewsignoffregistry
- platformopen2026-05-31Platform 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-0028geographyplatform-geography-snapshotadr-0013adr-0028market-idrekeydriftcontract-proposal
- platformopen2026-05-31Opening 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 ADRadr-0014customer-handoffcredit-reservation-lockdelivery-ownershipcross-disciplinecoordination-adr-candidate
- 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-31Platform accepts Delivery's Option B and proposes ADR-0029 recording the cross-discipline ownership-start decision; customer.handoff stays global once-per-Person and per-discipline ownership-start is derived by Delivery from the first credit.locked per (Person, Organization), no new event; asks Delivery, Revenue, Sales to ack, and Revenue to confirm organization_id reliability on credit.lockedadr-0029adr-0014customer-handoffcredit-reservation-lockcross-disciplineack-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-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-31Requesting decision-level acknowledgment of ADR-0014 (each Sguild discipline is its own Organization within one tenant); the decision is implemented and in use across the mart and data-access work but the ADR is still Proposed with no ack thread, please read and ack so it can move to Accepted ahead of Sguild Chessadr-0014organization-as-disciplineack-request
- deliveryopen2026-05-31Delivery'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 obligationadr-0014customer-handoffcredit-reservation-lockdelivery-ownershipcross-disciplinecoordination-adr-candidate
- platformopen2026-05-29Recommendation on where Sales places orders; a Sales-owned thin surface backed by a Revenue API, never a direct write, with one load-bearing design question for Revenue to settle firstorderingsales-surfacerevenueorder-flowcredit-reservation-lockcontract-proposal
- financeopen2026-05-27Finance needs SDR attempt-mix and time-per-channel inputs before committing the CAC SDR cost assumption; phone and text attempts have materially different durationscacsdr-allocationmart-computefinance-mart
- deliveryopen2026-05-27response by 2026-06-03Delivery introduces lesson rebook intent soft-slot protection for every completed lesson; no credits or Revenue reservation are created, Delivery stores the customer-owned plus-seven-day intent, Coaching should block the interval for other customers, and Sales should pass customer identity through eligibility so the owning customer can rebook their protected slotdeliveryrebook-intentsoft-slot-protectioncoaching-availabilitysales-close-orchestrationno-credit-reservation
- deliveryopen2026-05-27response by 2026-06-03Delivery pins lesson-lifecycle v1.2.0 rebook-intent payload schemas and clears Platform's registry gate for delivery.rebook-intent eventsrebook-intentlesson-lifecycleevent-types-registrysoft-slot-protection
- 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
- revenueopen2026-05-27Revenue declines masking stale Sales Lead state after Delivery handoff in local meshsalescustomer-handofflocal-meshworkbenchlead-lifecycle
- 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 (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
- 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-22External Actions Queue handler execution; ADR-0011 amended and the queue contract bumped to v1.2.0, producer domains expose a Platform-callable /api/external-actions/execute endpointexternal-actionsadr-0011contractshandler-executioncross-domain
- coachingopen2026-05-21Sales coverage renderer drive-time bubble suppression belongs in Sales UIcoach-availabilitysales-workbenchcoverage-rendererdrive-time
- 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
- 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