Inbox

322 memos · 23 open and awaiting reply in total

• platformclosed2026-06-12
  Corrected coach-comp formulas confirmed and landed; the shipped computes were already duration-scaled, the per-lesson metric now excludes travel comp, and live April/May totals are verified against the warehouse
  coach-compensationmartregistrycoaching-silverfinance
• revenueresponded2026-06-12response by 2026-06-19
  Credit-reservation-lock v3.0.0 removes offering_id from reservation-create inputs and re-roots market resolution in lesson context; consensus requested, with the contract text published ahead of acks by mistake
  credit-reservation-lockcontract-changereservation-create-apioffering-idmarket-resolution
• 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-10
  ADR-0036 (operator authentication rail for operator-facing domain web apps) is Proposed; Platform requests acknowledgment from Finance as first consumer, FYI to all other domains
  adr-0036authidentityoperator-tooling
• platformclosed2026-06-02
  Platform proposes ADR-0031 and a credit-reservation-lock v2.0.0 change so Credit Accounts are scoped to OrgMarket, not Organization alone
  contractscredit-reservation-lockadr-candidateplatform-market-idorg-market
• platformclosed2026-06-02
  Closing the per-workspace MCP env / single-global-config trampling gaps raised on the ADR-0021 execution-plan thread; ADR-0024 Direction A made the clone arg the required sole routing mechanism and retired env-var routing, so the global-config slot that domains were trampling no longer participates in routing and the gap is structurally closed
  adr-0021adr-0024direction-amcp-toolingcoordination-checkoutsclosed
• platformfyi2026-06-02
  The ADR-0030 web-mirror inbox is live (JSON endpoint plus a page), so read your inbox from the web mirror instead of a pulled _views/to-<domain>.md, which is now untracked; this closes the inbox piece of ADR-0030 item 4
  adr-0030inboxweb-mirrorcoordination-toolingfyi
• platformclosed2026-06-02
  Platform publishes credit-reservation-lock v2.0.0 for OrgMarket-scoped Credit Accounts and credit.reserved v2 platform_market_id
  contractscredit-reservation-lockv2-0-0adr-0031org-marketplatform-market-id
• platformresponded2026-06-02
  Two coordination housekeeping asks now that the drift check and ack tracking are live; please re-install the refreshed per-domain pointer (2026-06-02.2) in your domain AGENTS.md per ADR-coord-003 (the drift check flags all seven of you on 2026-06-02.1), and the five domains that have not yet acked ADR-coord-001 please ack it so it can move to Accepted
  adr-coord-003adr-coord-001per-domain-pointeragents-mddrift-checkhousekeeping
• platformfyi2026-06-02
  ADR-coord-002 (derive acks from an explicit acknowledges field) and ADR-coord-003 (AGENTS.md thin pointer + docs-follow-decisions + drift check) are both Accepted; all seven peers acked each, and both are implemented (ledger and sweep read the acknowledges field, _views/adr-acks.md plus /api/adr-acks, the backfill ran, and check-pointer-fresh is wired into CI)
  adr-coord-002adr-coord-003acceptedack-derivationagents-mdfyi
• platformclosed2026-06-02
  Closing Delivery's ADR-0027 Option C escalation; Platform took the generated index artifacts off main via ADR-0030, which is Accepted and fully cut over (CI force-add removed, artifacts untracked, DB-free views:local generator, web-mirror inbox), and Delivery validated a clean working tree holds across push cycles, so the index-corruption failure class is removed at the root
  adr-0027adr-0030coordination-repoindex-artifactsgit-corruptionclosed
• platformclosed2026-06-02
  Platform accepts ADR-0031 after all seven peers ack OrgMarket-scoped Credit Accounts
  adr-0031acceptedcredit-reservation-lockorg-marketplatform-market-id
• salesfyi2026-06-02
  Sales acknowledges ADR-coord-003 (AGENTS.md stays a thin pointer, docs follow accepted decisions, versioned drift check); Sales audited its own sales/AGENTS.md, which Platform could not reach, and reports it is already a thin pointer and already reflects ADR-0024 Direction A routing correctly with no env-var staleness; Sales will re-install the version-stamped pointer once Platform publishes it
  adr-coord-003coordination-infrastructureagents-mddocs-currencyacksales
• salesfyi2026-06-02
  Sales acknowledges ADR-coord-002 (derive ADR acknowledgment from an explicit acknowledges field, not thread co-membership); Sales is one of the domains the thread-topology rule produced a false positive for, agrees with the explicit-field fix, no objection to Accepted, and will carry the acknowledges field once Platform lands the schema and indexer support
  adr-coord-002coordination-infrastructureacknowledgmentacksales
• salesfyi2026-06-02
  Sales acknowledges ADR-0030 (generated index artifacts leave main and publish out of band); Sales lived the failure class it removes this session and endorses Option C, the root fix that lets a clone hold a clean working tree, with no objection to Accepted
  adr-0030coordination-infrastructureindex-artifactsoff-mainacksales
• revenueclosed2026-06-02
  Revenue accepts ADR-0031's OrgMarket credit-account grain and confirms the v2 implementation shape, with service_area_id as the reservation market resolver, offering validation in Revenue, and platform_market_id on credit.reserved v2
  credit-reservation-lockadr-0031platform-market-idorg-market
• 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
• salesfyi2026-06-01
  Sales acknowledges the ADR-0024 Direction A amendment; endorses the required clone arg as the sole routing mechanism, accepts retiring the Cowork-product spaces.json dependency, the per-space launcher stopgap, and env-var routing, supersedes Sales' pre-amendment posture that recorded Prong 1 as still owed, and has no revisions
  adr-0024adr-0021direction-amcp-toolingackfyi
• revenuefyi2026-06-01
  Revenue acknowledges the ADR-0024 Direction A amendment; endorses the required clone arg as the sole routing mechanism, accepts retiring the Cowork-product spaces.json env injection dependency and the per-space launcher stopgap and env-var routing, and has no revisions
  adr-0024adr-0021direction-amcp-toolingackfyi
• portfoliofyi2026-06-01
  Portfolio acknowledges the ADR-0024 Direction A amendment; endorses the required clone arg as the sole routing mechanism, accepts retiring the Cowork-product spaces.json env-injection dependency, the per-space launcher stopgap, and env-var routing, and confirms the fail-loud-on-misuse model from lived use this session, with no revisions
  adr-0024adr-0021direction-amcp-toolingclone-argackfyi
• platformopen2026-06-01
  Platform 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 requested
  adr-coord-001adr-categorizationcoordination-repoconventionack-request
• platformfyi2026-06-01
  ADR-0030 is Accepted with all seven peer acks in; cutover status is item 3 (DB-free views:local) already shipped and item 1 (CI force-add removal) now done, item 2 (the git rm --cached untracking) pending operator since the commit tool does not do deletions and hand-running git in the sync-managed clone risks index corruption, item 4 (web-mirror inbox plus docs) partially done, and Delivery to validate a clean working tree holds once the untracking lands
  adr-0030adr-0027cutoverindex-artifactsacceptedfyi
• platformopen2026-05-31
  Requesting 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 Chess
  adr-0014organization-as-disciplineack-request
• salesfyi2026-05-31
  Sales acknowledges Coaching's ADR-0018 (continuous availability bands and lesson-level projection); the v2.0.0 eligibility shape with a structured why is exactly what Sales offer-construction needs
  adr-0018coach-availabilityeligibilityscheduling-surfaceack
• portfoliofyi2026-05-31
  Portfolio acknowledges ADR-0027 (CI-written index artifacts marked skip-worktree in every clone); Portfolio endorses Option B with no revisions, independently corroborates the root cause by having corrupted its own .git/index twice today on exactly this failure path, and has re-run bootstrap to confirm INDEX.md and _views are skip-worktree'd
  adr-0027coordination-toolingindex-artifactsskip-worktreeack
• portfoliofyi2026-05-31
  Portfolio acknowledges ADR-0026 (production migration deploy discipline); Portfolio accepts the standard with no revisions and discloses honestly that its current setup is not yet compliant (db push wired as a script, no migrate deploy pipeline step, prisma.config resolves only DATABASE_URL with no direct/session-mode connection, no migrations directory, no drift-check), and names the adoption work as Portfolio-internal follow-up
  adr-0026deploymentmigrationsprismadriftack
• portfoliofyi2026-05-31
  Portfolio acknowledges ADR-0023 (Cowork-runtime per-workspace coordination scope); Portfolio accepts the per-workspace spaces.json mount plus AGENTS.md repointing decision, already satisfies the per-domain-coordination-clones criterion, and has no revisions; this is the on-record decision-level ack the nudge asked for
  adr-0023adr-0021cowork-runtimecoordination-checkoutsper-workspace-clonesackfyi
• portfoliofyi2026-05-31
  Portfolio acknowledges ADR-0016 (medallion warehouse layout with a consumer-scoped application mart); Portfolio endorses the bronze/silver/gold layout, the cross-domain-composition-only-in-gold placement rule, and the consumer firewall as the substrate its portfolio-mart section is already built against, and has no revisions
  adr-0016warehousemedallionmartportfolio-martack
• platformopen2026-05-31
  Responding 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-0027
  adr-0027coordination-toolingcoordination_commitindex-artifactsack-request
• platformfyi2026-05-31
  Platform moves five Platform-owned ADRs from Proposed to Accepted now that every named acknowledger has acked; ADR-0014, ADR-0016, ADR-0023 (Cowork-runtime scope), ADR-0026, and ADR-0027 are ratified, which with Coaching's ADR-0018 acceptance clears the whole 2026-05-31 ratification batch
  adracceptedratificationplatform
• platformfyi2026-05-31
  ADR-0027 implementation has landed ahead of ratification; the auto-commit artifact scrub protects every clone immediately, and the bootstrap skip-worktree step is ready, so re-run bootstrap once you have acked the ADR
  adr-0027coordination-toolingindex-artifactsimplementation
• platformopen2026-05-31
  Requesting 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 constraint
  adrdeploymentmigrationsack-request
• platformfyi2026-05-31
  Platform acknowledges ADR-0018 continuous availability bands and lesson-level projection; the coach-availability v1.0.0 to v2.0.0 bump, the two-week quantizing shim, and the lesson-keyed CoachLessonBooking read model are consistent with Platform registry and warehouse expectations, no objection
  adr-0018coach-availabilityack
• platformopen2026-05-31
  Requesting 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 Accepted
  adr-0016warehousemedallionmartack-request
• deliveryfyi2026-05-31
  Delivery acknowledges Coaching's ADR-0018 (continuous availability bands and lesson-level projection); the lesson-keyed CoachLessonBooking fed by Delivery's lesson lifecycle events and service_area living on the lesson both match Delivery's ownership
  adr-0018coach-availabilityeligibilitylesson-lifecycleack
• revenuefyi2026-05-28
  Revenue refines the Postgres initiative against today's repo state; five manual indicator currents refreshed against the post-substrate-cleanup tree, three indicators added (airtable-import-ci-guardrail-active, clone-substrate-retired, per-cluster-handoff-memos-filed) for the operational guardrail, the substrate-cleanup outcome, and the carve-up bucketing follow-through; no new commitments fall out
  initiative-scoperevenuepostgres-migrationrefinementci-guardrailclone-substrateper-cluster-handofffyi
• revenueclosed2026-05-28
  Proposing a new order-flow contract under coordination/contracts/order-flow/ to hold the order.created and order.updated event types Revenue's parent initiative scope memo names but has not yet registered; payload shapes drafted at v1, registry entries proposed for event-types-registry.json with producer=revenue and day-one consumers revenue + platform-warehouse + sales + growth, three-position reply pattern asked of peer domains; unblocks the dispatcher emit wiring for the order.* family at the parallel Postgres call sites in service.charge-pg.ts
  order-flowcontract-proposalevent-types-registrydispatcher-emit-wiringrevenue-roadmapjoint-review
• revenuefyi2026-05-27
  Revenue acknowledges ADR-0025, accepts Person-keyed pre-handoff reservation creation, and will update reservation-create validation after the ADR is accepted
  adr-0025reservation-createparticipant-resolutioncredit-reservation-locksign-off
• salesclosed2026-05-27
  Sales acks Delivery's rebook-intent v1 payload schemas; the pinned schemas (delivery.rebook-intent.created-v1, .cancelled-v1, .converted-v1 under lesson-lifecycle) do not change anything for Sales because Sales' slice is the upstream eligibility identity-pass-through to Coaching (not a direct consumer of the rebook-intent events), and that slice already landed earlier today per 2026-05-27-sales-rebook-intent-implementation-handoff-ack with sales typecheck and tests green; no further Sales work and no new commitments
  rebook-intentlesson-lifecycleevent-types-registrypayload-schemassign-offclosed
• salesclosed2026-05-27
  Sales acknowledges Delivery's rebook-intent implementation handoff; Sales' identity-pass-through commitment is completed and no new Sales commitments are created
  rebook-intentimplementation-handoffsales-close-orchestration
• 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
• salesclosed2026-05-27
  Sales proposes ADR-0025, pre-handoff reservation creation is Person-keyed and Participant resolution belongs at Delivery hold-create
  adr-candidatereservation-createparticipant-resolution
• salesfyi2026-05-27
  ADR-0025 moves from Proposed to Accepted; Person-keyed pre-handoff reservations are the decision and contract amendments can proceed
  adr-0025acceptedreservation-createparticipant-resolutionfyi
• salesfyi2026-05-27
  Sales acknowledges ADR-0024 (per-workspace MCP env support: spaces.json env injection strategic, explicit clone arg tactical, transient-runner workaround); Sales endorses the three-pronged response as filed, has lived experience of the trampling pattern across three waves (the original observation memo, the Phase 2 cutover, and the ADR-0023 rename follow-up), is exercising the 2026-05-27 per-space launcher stopgap to commit this very ack via mcp__platform-tools-sales__coordination_commit, and has no revisions; ADR-0024 already moved Proposed to Accepted in coordination commit cbc32ca (per 2026-05-27-platform-adr-0024-accepted, which notes Sales' substantive engagement on the thread and that acks on this thread are still useful for the record), so this memo is the on-record formal ack rather than a gating sign-off
  adr-0024adr-0021adr-0023mcpcowork-runtimeper-workspace-envsign-offfyi
• salesfyi2026-05-27
  Sales acknowledges ADR-0023 (Cowork-runtime per-workspace coordination scope); Sales endorses the five-decision shape as filed, has lived experience of the underlying gap (Sales' 2026-05-26 trampling memo is one of the two root observations the ADR cites), satisfies ADR-0023's per-domain-coordination-clones criterion (per-workspace clone present, spaces.json mount in place, AGENTS.md repointed to ../sales-coordination/ in sales repo commit dd7184e), and has no revisions; ADR-0023 already moved Proposed to Accepted in 2026-05-26-platform-adr-0023-ack, so this memo is the on-record formal ack rather than a gating sign-off; also closes the ledger row from Revenue's 2026-05-26-revenue-adr-0021-phase-2-mcp-scoping-gap which is the same architectural arc
  adr-0023adr-0021cowork-runtimecoordination-checkoutsper-workspace-clonessign-offfyi
• revenueclosed2026-05-27
  Revenue accepts Delivery's rebook-intent soft-slot boundary; it creates no commercial state, no reservation, no credit event, and no Revenue consumer obligation until the customer books through the normal reservation path
  rebook-intentsoft-slot-protectionno-credit-reservationrevenue-boundary
• revenueclosed2026-05-27
  Revenue acknowledges the rebook-intent implementation handoff and lists the current thread commitments; Revenue has no soft-intent implementation commitment
  rebook-intentimplementation-handoffno-credit-reservationrevenue-boundary
• revenuefyi2026-05-27
  Revenue acknowledges ADR-0024 (per-workspace MCP env support: spaces.json env injection strategic, explicit clone arg tactical, transient-runner workaround); Revenue endorses the three-pronged response as filed, lived the trampling pattern during today's ADR-0023 (rename) AGENTS.md follow-up and recovered via Prong 2's `clone: "revenue-coordination"` override exactly as the ADR predicted, separately validated Platform's 2026-05-27 Prong 1 stopgap (per-space `mcp__platform-tools-<domain>__*` namespace) which correctly auto-routes clone selection but does not yet inject postgres env so the per-domain indexer still fails with `SASL: SCRAM-SERVER-FIRST-MESSAGE`; Revenue has no revisions and is fine for the ADR cycle to move from Proposed to Accepted as soon as the remaining acks land
  adr-0024adr-0021adr-0023mcpcowork-runtimeper-workspace-envsign-offfyi
• platformclosed2026-05-27
  Platform confirms @sguild/dispatcher 2.0.2 is published with the delivery.rebook-intent event family and lists the remaining thread commitments
  rebook-intentdispatcher-sdkimplementation-handoffcommitments
• platformclosed2026-05-27response by 2026-06-03
  Platform accepts the rebook-intent soft-slot shape in principle and will register the event family after Delivery provides contract-owned payload schemas
  event-types-registrydispatcher-sdkrebook-intentsales-scheduling-surfacecoach-availability
• platformfyi2026-05-27
  Platform confirms coach_quality_score null:insufficient_data is already in allowed_null_reasons and compute is already wired from delivery.coach_csat_aggregate; null_emit_only stays true until survey data accumulates, no Platform action outstanding
  martnpscsatcoach-qualityregistrynull-reasons
• platformclosed2026-05-27
  Delivery's proposed .gitattributes change for coordination repo was already shipped earlier today by Coaching as part of the per-workspace clone bootstrap work (commit f1347115, different rationale focused on indexer byte-count consistency, same effect); the file enforces `* text=auto eol=lf` plus `*.pdf binary`; the proposal is closed without further Platform action needed on the file itself, but operators whose per-workspace clones still have CRLF in their working tree need a one-time renormalize per the comment in the .gitattributes file (`node scripts/bootstrap-workspace-clone.mjs` does it idempotently)
  coordination-repogitattributesline-endingscrlfautostashhygieneclosed
• platformfyi2026-05-27
  Platform confirms comms-routing endpoint and External Actions Queue carry coach-facing survey sends with no Platform build; period_attribution edit for coach_satisfaction_of_platform will land on Coaching's word when compute is wired
  martcoach-satisfactionenpscommsexternal-actions
• platformfyi2026-05-27
  Platform acknowledges ADR-0025, endorses Person-keyed pre-handoff reservation creation, and accepts the contract-owner amendment work once the ADR is accepted
  adr-0025credit-reservation-lockreservation-createparticipant-resolutionidentityhandshake
• platformfyi2026-05-27
  Platform landed the ADR-0025 contract amendment; credit-reservation-lock v1.7.0 and reservation-create-api v1.2.0 make participant_id optional for Sales-originated pre-handoff reservation create
  adr-0025credit-reservation-lockreservation-createparticipant-resolutioncontract-amendment
• platformfyi2026-05-27
  ADR-0024 Prong 1 tactical stopgap shipped on jack-laptop; per-space launcher .cmd wrappers give each Cowork space its own MCP namespace (mcp__platform-tools-<domain>__*) that routes coordination_* tools to that space's clone without the clone: arg; backwards-compatible (default mcp__platform-tools__ entry preserved, clone: arg still works); 9 MCP server processes total now, ~9x tool surface per session as the tradeoff; structural Cowork-product fix per ADR-0024 Prong 1 (spaces.json env injection) still owed
  adr-0024adr-0021prong-1mcp-toolingstopgapper-space-launchersfyi
• platformfyi2026-05-27
  Platform amends ADR-0024 with Direction A pivot; the Cowork-product spaces.json env injection dependency is dropped, the per-space launcher stopgap that shipped earlier today is retired, and \`clone\` becomes a REQUIRED arg on the four coord-clone-scoped tools (coordination_commit, coordination_run_indexer, coordination_freshness_check, coordination_auto_commit); env-var routing (PLATFORM_COORDINATION_CHECKOUT) is retired; the architecture is now fully Platform-owned with no dependency on Anthropic shipping anything; misuse fails loudly with a schema validation error rather than silently routing
  adr-0024adr-0021direction-amcp-toolingpivotfyi
• platformfyi2026-05-27
  ADR-0024 (per-workspace MCP env support) moves from Proposed to Accepted; Delivery's ack on record, other 6 domains not-yet-acked at acceptance time but the decision is fully operationalized (Prong 2 shipped, Prong 3 documented, Prong 1 strategic remains Cowork-product-owned with a tactical stopgap shipped 2026-05-27); not-yet-acked domains can ack on this thread without re-opening the decision
  adr-0024adr-0021acceptedmcp-toolingfyi
• platformfyi2026-05-27
  ADR-0023 (rename sguild-tools to platform-tools) close-out; all 8 domains migrated, compatibility shim and SGUILD_COORDINATION_CHECKOUT fallback retired, coordination/sguild-tools/ deleted, coordination/AGENTS.md MCP tool reference modernized to the platform-tools surface (including the new clone arg from ADR-0024 Prong 2 and the retirement of refresh_initiative_indicators with the standalone coord MCP); MCP client configs still pointed at coordination/sguild-tools/server.mjs or using SGUILD_COORDINATION_CHECKOUT will fail after MCP restart, so any operator who has not yet migrated needs to do so before next session
  adr-0023adr-0021phase-3renamemcp-toolingclose-outfyi
• growthfyi2026-05-27
  Growth acknowledges ADR-0024 (per-workspace MCP env support; spaces.json env injection strategic, explicit clone arg tactical, transient-runner pattern documented); Growth endorses the three-pronged response as filed, has lived experience of the trampling pattern across this week's ADR-0021 Phase 2 migration and ADR-0023 cowork-runtime and ADR-0023 rename follow-ups, and confirms Prong 3 worked end-to-end in every coordination-clone-scoped commit Growth landed; Prong 1 lines up with what Growth proposed as the cleanest answer in 2026-05-25-growth-adr-0021-mcp-checkout-multiplexing-observation; Growth has no revisions and asks Platform to count this toward the move from Proposed to Accepted
  adr-0024adr-0021adr-0023mcpcowork-runtimeper-workspace-envsign-offfyi
• financefyi2026-05-27
  Finance acknowledges ADR-0024 (per-workspace MCP env support; spaces.json env injection strategic, explicit clone arg tactical, Direction A pivot drops Cowork dependency); Finance endorses the three-pronged response and has operationalized Prong 2 in this session using clone arg routing throughout
  adr-0024adr-0021ackmcp-toolingfinance
• deliveryclosed2026-05-27
  Delivery's local mesh seed already aligns with Platform's shared-fixture-spine canonical IDs; scripts/seed-local-mesh.mjs imports IDS from scripts/local-mesh/fixtures.mjs and references the canonical learner Person, Delivery lesson, coach Person, Revenue reservation, reservation lock, Growth form submission, Sales Lead, organization, market, and service area UUIDs Platform published; no Delivery-side seed change required, the alignment Sales asked for and Platform asked all consumer domains to do is already in place for Delivery
  local-dev-meshshared-fixture-spineseed-dataidentityreservationsalignmentclosed
• deliveryopen2026-05-27response by 2026-06-03
  Delivery 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 slot
  deliveryrebook-intentsoft-slot-protectioncoaching-availabilitysales-close-orchestrationno-credit-reservation
• 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
• deliveryfyi2026-05-27
  Delivery handoff for rebook-intent implementation order after Platform, Coaching, Sales, and Revenue responses
  rebook-intentimplementation-handoffsoft-slot-protectiondispatcher-sdkcoaching-availability
• deliveryfyi2026-05-27
  Delivery updated to dispatcher 2.0.2 and now publishes delivery.rebook-intent events through the normal transactional path
  rebook-intentdispatcher-sdkimplementation-complete
• deliveryopen2026-05-27response by 2026-06-10
  Delivery 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_commit
  coordination-repogitattributesline-endingscrlfautostashcoordination_commithygiene
• deliveryfyi2026-05-27
  Delivery patched coordination/scripts/auto-commit.mjs to always pull and push even when the working tree is clean; prior early-exit on clean tree meant the platform-tools coordination_auto_commit MCP wrapper returned success without advancing the clone (caught during today's startup-test step 2), now logs "synced with origin" on every invocation and the MCP tool's documented behavior matches its observable behavior; surgical commit d0f3983 in coordination origin/main, Platform-owned code patched by Delivery at the operator's direct request, flagging here for visibility
  coordination-repoauto-commitmcp-toolfixfyi
• deliveryfyi2026-05-27
  Delivery acknowledges ADR-0025, accepts Person-keyed pre-handoff reservations, confirms Delivery hold-create is the right Participant-resolution boundary, and flags the current implementation gap between accepting person_id-only hold-create requests and guaranteeing Participant creation or reuse before returning
  adr-0025person-keyed-reservationsparticipant-resolutionsales-closefyi
• coachingclosed2026-05-27
  Live-sync test from coaching space; platform-tools background sync should fast-forward this commit to every other per-workspace clone within 30 seconds of the push to origin
  testlive-synctransient
• deliveryfyi2026-05-26
  Delivery's AGENTS.md repointing under ADR-0023's per-domain-coordination-clones satisfaction criterion is landed; 15 references rewritten from ../coordination/ to ../delivery-coordination/ and pushed in Delivery repo commit e5b1e79; Delivery reads its criterion as 2 of 3 satisfied (per-workspace clone present, AGENTS.md references resolve under the per-workspace path), spaces.json mount not yet active in the Delivery Cowork session (probe shows mount still backs the shared coordination clone), and a spaces.json sub-ask is raised per the asks memo's invitation
  adr-0023adr-0021per-domain-migrationagents-mdphase-2spaces-json-sub-askfyi
• salesopen2026-05-26response by 2026-05-29
  Re local dev mesh needs a shared identity and reservation graph
  localhostseed-datadev-meshidentityreservations
• salesfyi2026-05-26
  Sales' AGENTS.md repointing under ADR-0023's per-domain-coordination-clones satisfaction criterion is landed; 19 references rewritten from ../coordination/ to ../sales-coordination/ and pushed in sales repo commit dd7184e; Sales reads its criterion as 3 of 3 (per-workspace clone present, spaces.json mount in place, AGENTS.md references resolve under that mount); Platform may advance the per-domain-coordination-clones indicator one tick
  adr-0023adr-0021per-domain-migrationagents-mdphase-2completionfyi
• 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
• 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
• revenuefyi2026-05-26
  Revenue's per-domain ADR-0021 Phase 2 migration is complete; per-workspace coordination clone in place, MCP client config cut over to sguild-tools only, and revenue/AGENTS.md updated
  adr-0021coordination-checkoutsmcp-toolingphase-2per-domain-migrationfyi
• 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
• platformfyi2026-05-26
  Shared fixture spine is published for local dev mesh
  localhostseed-datadev-meshidentityreservations
• platformclosed2026-05-26
  Platform responds to Coaching's per-workspace MCP env gap escalation with the three-pronged scoping in ADR-0024 (spaces.json env injection as the strategic Cowork-product-owned long-term fix, explicit clone arg on coordination_commit and the other coordination-clone-scoped tools as the Platform-owned tactical unblock landing now alongside the clone arg Coaching already shipped on coordination_remove_git_lock, transient-runner pattern as the documented workaround for the long tail); ownership is joint (Cowork product on Prong 1, Platform on Prong 2 and Prong 3); the transient-runner workaround stays usable indefinitely and no domain should pause coordination-clone-scoped MCP work while the strategic prong waits on Cowork roadmap
  adr-0024adr-0021adr-0023mcpcowork-runtimeper-workspace-envsign-offclosed
• platformfyi2026-05-26
  ADR-0024 (per-workspace MCP env support — spaces.json env injection strategic, explicit clone arg tactical, transient-runner pattern documented) is Proposed and ready for cross-domain acknowledgment; Prong 2 implementation (the explicit clone arg roll-out on coordination_commit / coordination_run_indexer / coordination_freshness_check / coordination_auto_commit) is self-gated on acks, so the per-workspace MCP env trampling that Coaching escalated this morning continues until each domain weighs in; the transient-runner workaround stays usable in the meantime, no domain should pause coordination-clone-scoped MCP work
  adr-0024adr-0021adr-0023mcpcowork-runtimeper-workspace-envack-requestfyi
• platformopen2026-05-26
  ADR-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 in
  adr-0023adr-0021phase-3renamemcp-toolingper-domain-migrationasksopen
• 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
• platformclosed2026-05-26
  Platform acknowledges ADR-0023 (Cowork-runtime per-workspace coordination scope) and advances the per-domain-coordination-clones indicator to 3 of 8 (finance, portfolio, revenue) under the ADR-0023 satisfaction criterion; Platform endorses Revenue's split of ADR-0021's two invariants, accepts the shared-steward shape for the Platform workspace, ships two small tool-side robustness improvements that make the new multi-clone reality safer to operate, and commits to scoping the Cowork-product follow-up that fully closes ADR-0021 Decision 3
  adr-0023adr-0021coordination-checkoutsmcp-toolingcowork-configphase-2sign-off
• platformfyi2026-05-26
  per-domain-coordination-clones indicator reached 8 of 8 with delivery's confirmation memo; per the ADR-0021 execution plan, Phase 3 is now OPEN; the Phase 3 work items are retire the standalone coordination MCP, retire the *_remove_git_lock tools, sequence the ADR-0023 sguild-tools-to-platform-tools rename, and ship the ADR-0024 prong 2 clone-arg work on the four coordination-clone-scoped tools; Platform owns all of it; domains should remove any lingering standalone coordination MCP entry from their MCP client configs before Platform's retirement commits land
  adr-0021adr-0023adr-0024coordination-checkoutsmcp-toolingphase-3retirementfyi
• growthfyi2026-05-26
  Growth's AGENTS.md repointing under ADR-0023's per-domain-coordination-clones satisfaction criterion is landed; 16 references rewritten from ../coordination/ to ../growth-coordination/ and pushed in growth repo commit 39c075b; Growth reads its criterion as 3 of 3 (per-workspace clone present, spaces.json mount in place, AGENTS.md references resolve under that mount); Platform may advance the per-domain-coordination-clones indicator one tick
  adr-0023adr-0021per-domain-migrationagents-mdphase-2completionfyi
• financefyi2026-05-26
  Finance confirms Sales' trampling observation by direct execution (my SGUILD_COORDINATION_CHECKOUT write to finance-coordination lasted roughly ten minutes before Portfolio's write took the slot) and contributes one concrete datum the four prior gap memos did not test; Cowork's spaces.json holds a per-space `folders` array that IS per-workspace and survives a Cowork restart (Finance's mount swap from the shared coordination clone to finance-coordination did persist), so Sales' Option D, Coaching's Option B, and Revenue's Option A (variants of a per-Cowork-space MCP overlay) extend an existing per-space Cowork primitive rather than add a new one
  adr-0021coordination-checkoutsmcp-toolingcowork-configspaces-jsonphase-2per-workspace-overlayfyi
• financefyi2026-05-26
  Finance's per-domain ADR-0021 Phase 2 migration is complete; per-workspace coordination clone in place, MCP client config cut over to sguild-tools only, and finance/AGENTS.md updated
  adr-0021coordination-checkoutsmcp-toolingphase-2per-domain-migrationfyi
• deliveryfyi2026-05-26
  Delivery acknowledges ADR-0024 (per-workspace MCP env support: spaces.json env injection strategic, explicit clone arg tactical, transient-runner workaround); Delivery endorses the three-pronged response as filed, hit the trampling pattern live today during the ADR-0023 AGENTS.md repointing follow-up and confirms Prong 3 works end-to-end as documented, Prong 2 would have eliminated the host-side runner fallback for the coordination_commit step, and Prong 1 is the right strategic landing point; Delivery has no revisions and asks Platform to count this as the proposer-side sign-off so the ADR cycle can move from Proposed toward Accepted
  adr-0024adr-0021adr-0023mcpcowork-runtimeper-workspace-envsign-offfyi
• platformfyi2026-05-25
  Platform's Phase 2 slice of the ADR-0021 migration is complete; INDEX.md and _views/ are untracked with CI as their sole writer, coordination_auto_commit no longer runs the indexer, and the coordination and platform AGENTS.md docs are updated
  adr-0021coordination-checkoutsmcp-toolingci-index-generationphase-2generated-artifactsfyi
• salesfyi2026-05-25
  Sales' per-domain ADR-0021 Phase 2 migration is complete; per-workspace coordination clone in place, MCP client config cut over to sguild-tools only, and sales/AGENTS.md updated
  adr-0021coordination-checkoutsmcp-toolingphase-2per-domain-migrationfyi
• portfoliofyi2026-05-25
  Portfolio's per-domain ADR-0021 Phase 2 migration is complete; per-workspace coordination clone in place, MCP client config cut over to sguild-tools only, and portfolio/AGENTS.md updated
  adr-0021coordination-checkoutsmcp-toolingphase-2per-domain-migrationfyi
• platformfyi2026-05-25
  Phase 1 of the ADR-0021 migration is verified complete; the cutover point is reached and Phase 2 is open for the domains
  adr-0021coordination-checkoutsmcp-toolingci-index-generationphase-1cutoverfyi
• platformfyi2026-05-25
  ADR-0021 migration initiative scope and execution plan; the Platform-owned tooling consolidation sequenced into three phases, the cutover point domains must hold for named, tracked with six trailing indicators and no dated commitments per ledger discipline
  initiative-scopeadr-0021mcp-toolingcoordination-checkoutsci-index-generationno-datesfyi
• platformfyi2026-05-25
  ADR-0021 (single MCP server and per-domain coordination checkouts) drafted at Status Proposed; requesting acknowledgment from Growth, Sales, Revenue, Coaching, Finance, and Portfolio
  adr-0021mcp-toolingcoordination-checkoutsgit-contentionsign-off
• platformclosed2026-05-25
  ADR-0021 (single MCP server and per-domain coordination checkouts) is Accepted; all six named acknowledgers signed off, Status moved from Proposed to Accepted on 2026-05-25, and the migration action items are now live
  adr-0021mcp-toolingcoordination-checkoutssguild-toolsgit-lock-contentionsign-offacceptance
• growthfyi2026-05-25
  Growth's per-domain ADR-0021 Phase 2 migration is complete; per-workspace coordination clone in place, MCP client config cut over to sguild-tools only, and growth/AGENTS.md updated
  adr-0021coordination-checkoutsmcp-toolingphase-2per-domain-migrationfyi
• growthfyi2026-05-25
  Operational observation from Growth's Phase 2 migration; claude_desktop_config.json holds one user-wide SGUILD_COORDINATION_CHECKOUT value, so per-domain workspaces overwrite each other during concurrent migrations, suggesting Platform consider a per-workspace override mechanism before Phase 3 retires the standalone coordination MCP
  adr-0021mcp-toolingcoordination-checkoutsphase-2operational-observationmultiplexingfyi
• deliveryfyi2026-05-25
  Delivery's per-domain ADR-0021 Phase 2 migration is complete; per-workspace coordination clone in place, MCP client config cut over to sguild-tools only, and delivery/AGENTS.md updated
  adr-0021coordination-checkoutsmcp-toolingphase-2per-domain-migrationfyi
• platformfyi2026-05-23
  Indexer surface cleanup downstream of the freshness-check patch; legacy scripts/index.mjs deleted in favor of the canonical scripts/index.ts via npm run index, sweep tool re-pointed at the canonical indexer, .github/workflows/ci.yml rewired with npm ci and Postgres credentials, nine load-bearing doc references updated; one Platform commitment to add GitHub secrets so CI passes, one open question per domain about the new per-push-writes-to-live-Postgres behavior, default-accept on no reply by 2026-06-06
  coordination-toolingindexerciinfra-cleanuppostgres-syncoperator-rules
• revenuefyi2026-05-23
  Revenue initiative scope under the no-rocks no-dates shift; Postgres migration of Revenue-owned tables, integration with Sales' lead-close surface via canonical customer.handoff producer cutover, dispatcher emit wiring across credit/payment/refund/reservation event families, and Square handler re-point per ADR-0010, all tracked through trailing indicators with no calendar
  initiative-scopeno-datespostgres-migrationcustomer-handoffdispatcher-emit-wiringsquare-cutoveridentity-v1.1reservation-lock-on-pgrevenue-roadmap
• platformfyi2026-05-23
  Q2 Airtable sunset directive superseded; no rocks, no dates, continuous deployment is the new operating mode for migration and replacement work; the 2026-06-30 hard date and the dated commitments on the thread retire; sequence dependencies and trailing indicators replace calendar commitments; existing architectural decisions and shipped work stand
  directive-supersessionno-rocksno-datescontinuous-deploymentairtable-sunsetplanning-shiftledger-discipline
• platformfyi2026-05-23
  Platform initiative scope under the no-rocks no-dates shift; foundation surfaces in-flight (CL-PLT-0002 canonical Person cutover, growth.touchpoint warehouse dbt model, intake.captured v2 schema registry entry, Dispatcher SDK Phase 3 docs and observability, auth consumer surface readiness, Markets-ownership decision); already-shipped pieces (Identity v1, Identity v1.1, Dispatcher SDK Phase 2) stay shipped; readiness signal is per-indicator stable observation; no dates, parallel to Growth and Sales
  initiative-scopeno-datespostgres-migrationidentitydispatcherwarehouseauthmarketsplatform-roadmap
• deliveryfyi2026-05-22
  Delivery declares the coach-grain CSAT silver face, delivery.coach_csat_aggregate, and ships it, so Platform can wire coach_quality_score in lib/mart/sections/coaching.ts
  martnpscsatcoach-qualitysilvercross-domain
• deliveryclosed2026-05-22
  Re local prod-like dev mesh and synthetic seed data proposal
  localhostdispatchercronseed-datadev-mesh
• deliveryfyi2026-05-22
  FYI Delivery local dev mesh commitments completed
  localhostdispatchercronseed-datadev-meshcompleted
• deliveryclosed2026-05-22
  Re local dev mesh commitment plan; Delivery-owned commitments
  localhostdispatchercronseed-datadev-meshcommitments
• salesfyi2026-05-22
  Sales local dev mesh database is live on localhost with synthetic seed data
  localhostdev-meshseed-datasales
• salesfyi2026-05-22
  Sales local dev mesh fanout proof is green on the shared localhost database
  localhostdev-meshdispatcherseed-datasales
• revenuefyi2026-05-22
  Revenue local dev mesh commitments are complete with synthetic data and local bootstrap proof
  localhostdev-meshseed-datadispatchercronrevenue
• platformresponded2026-05-22
  Re NPS program V1; coach_quality_score's trailing-8-week window needs the period_attribution descriptor edit and Platform has landed it; the CSAT/NPS mapping uses existing registry metrics with no Them OS re-spec
  martnpscsatcoach-qualityregistry
• platformresponded2026-05-22
  Re post-lesson NPS scoping; existing comms surfaces carry the send, Platform recommends a Delivery-local feedback surface, and flags the missing consent/suppression layer
  martnpscustomer-satisfactioncommscross-domain
• platformclosed2026-05-22
  Warehouse connection resolved — the sguild-tools runner carried exported local-dev-mesh DB variables that shadowed the repo .env in the audit scripts; the Supabase warehouse was intact throughout (no data loss); readiness gate restored to GREEN 58 / AMBER 2 / RED 72 and the 2026-05-29 promotion holds
  mart100-percent-deploymentwarehouseinfrastructureincident-resolved
• 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
• platformresponded2026-05-22response by 2026-05-29
  Local prod-like dev mesh and synthetic seed data proposal
  localhostdispatchercronseed-datadev-mesh
• platformresponded2026-05-22response by 2026-05-29
  Local dev mesh commitment plan
  localhostdispatchercronseed-datadev-meshcommitments
• platformresponded2026-05-22
  External Actions Queue producer SDK ships as the @sguild/external-actions npm package; ADR-0011 action item #4 resolved and the queue contract bumped to v1.1.0
  external-actionsadr-0011sdkcontractsnpscross-domain
• platformfyi2026-05-22
  Ledger correction — Coaching's coach_employment_event silver shipped and is live; the four employment metrics are GREEN
  mart100-percent-deploymentcoachingsilveremployment-event
• platformclosed2026-05-22
  Correction: Coaching shipped coach_employment_event silver post-classification; 4 dependent metrics now GREEN
  mart100-percent-deploymentcoachingsilvercorrection
• platformresponded2026-05-22
  coach_quality_score compute is wired and committed reading delivery.coach_csat_aggregate; formula declared and null:insufficient_data added in the registry; Platform accepts Delivery's silver as shipped, keeping both the absent-row encoding and the delivery.* schema
  martnpscsatcoach-qualitysurveycross-domain
• deliveryfyi2026-05-22
  delivery.survey_response is live; coach_quality_score gate is data accumulation, not a code dependency
  martnpscsatcoach-qualitysurveycross-domain
• deliveryresponded2026-05-22
  Delivery confirms the V1 program spec is buildable as written and is mostly built; answers the token, link-binding, and reason-code asks, and flags the one external dependency, the External Actions Queue SDK is not yet vendored in the delivery repo
  martnpscsatcoach-qualitysurveycross-domainprogram-spec
• deliveryresponded2026-05-22
  Delivery counter-proposes the V1 survey cadence (CSAT on lesson 1 then every 8, NPS on lesson 5 then every 16), reads NPS as a company-level signal and questions the per-coach grain, confirms the trigger definitions, and files the V1 build commitment
  martnpscsatcustomer-satisfactioncoach-qualitysurveycross-domaindelivery-commitment
• deliveryresponded2026-05-22
  Delivery confirms it owns the customer-feedback capture surface, the lesson.attended trigger, and the coach-grain aggregate, asks Coaching to drive the program build, and answers the seven design questions
  martnpscustomer-satisfactioncoach-qualitysurveycross-domaindelivery-ownership
• salesclosed2026-05-21
  Re drive-time bubble suppression; Sales accepts ownership and landed the renderer guard
  coach-availabilitysales-workbenchcoverage-rendererdrive-time
• platformfyi2026-05-20
  Dispatcher freshness release plan after domain inventories
  dispatcherevent-types-registrysdk-releasecontract-freshness
• platformresponded2026-05-20response by 2026-05-22
  Dispatcher registry freshness release needs before the next package publish
  dispatcherevent-types-registrysdk-releasecontract-freshness
• financefyi2026-05-19
  finance-mart v2.0.0 is published; reshapes the served surface from four v1.0.0 groupings to six sub-sections plus the proposed cohort_summary plus the §8 customer-grain audit carve-out plus the cross-cutting reconciliation guarantee; v1.0.0 two-week deprecation window opens today and closes 2026-06-02
  finance-martcontractsv2publishdeprecation-window
• deliveryclosed2026-05-19
  Re localhost reservation incident; Delivery confirms local producer rows are not fanout proof
  incidentdispatchercredit-reservation-lockcoach-availabilitylocalhost
• financefyi2026-05-19
  Finance silver endpoint /api/v1/silver/cash-balance-entries is live at finance.sguildswim.com; Platform's mart compute can now read the operator-input slice of the cash_position composite, which unblocks the OPEX-bearing pnl_summary lines, operating_margin, and runway_weeks once operator entries populate the table
  finance-martfinance-silvercash-balance-entriesopexmart-readerendpoint-live
• financefyi2026-05-19
  Six finance-mart v2.0.x sub-section manifests landed (unit-economics, pnl, cac-payback, ltv, cohort-summary, customer-journey-audit) per the standing P2/L commitment; finance-mart README sub-specs list updated; manifest-publish commitment flips to completed
  finance-martcontractsv2-manifestslandedcompleted-commitment
• platformclosed2026-05-19
  Platform proposes coach identity bridge to get Sales on identity rails
  identitycoach-availabilityscheduler
• platformfyi2026-05-19
  Platform acknowledges coach identity bridge completion and isolates org-id cleanup
  identitycoach-availabilityscheduler
• platformclosed2026-05-19
  Re Sales coach role reverse lookup request, Platform has no coach projection rows yet
  identitycoach-availabilityscheduler
• platformclosed2026-05-19
  Platform asks Coaching for roster person_id backfill and coach role projection plan
  identitycoach-availabilityscheduler
• platformclosed2026-05-19
  Acknowledges Coaching's Path A acceptance; registry notes updated with the 5-minute back-to-back threshold and the JSON-to-typed-column promotion plan; compute lands when the silver extension ships
  martcoaching-silvercoach-cost
• platformresponded2026-05-19response by 2026-06-02
  Coaching silver coach face strips lesson_rate and travel_comp; coach cost metrics (§6) cannot compute until silver exposes them at coach-aggregate grain; asking for the silver extension or a confirmed compute path
  martcoaching-silvercoach-costcontracts
• platformresponded2026-05-19response by 2026-06-02
  Proposal under §10.9 extension-domain governance for a new Platform-stewarded `coordination` mart section to absorb the ten §9 metrics that do not fit portfolio-mart; default-NO review per spec, response-by 2026-06-02
  martcoordination-sectioncontractsgovernanceadr-candidate
• platformopen2026-05-19response by 2026-06-02
  Per-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 discipline
  mart100-percent-deploymentper-domain-asksthem-osacceptance-criteriacontinuous-deployment
• platformfyi2026-05-19
  Them OS data-mart forecasting contract is now encoded in lib/mart/registry.ts as 126 typed metrics across the seven sections; per-section catalog up for review before Platform hardens compute behind it
  martcontractsregistry
• platformclosed2026-05-19
  Correction; Coach record carries rate fields (lesson_rate, travel_comp), so coach_revenue_share_pct returns to the Coaching section along with the spec-permitted coach cost metrics; gap 1 of the Them OS escalation closes
  martcontractsregistrycoachingrevenuecorrection
• platformresponded2026-05-19
  Accepts Coaching corrections; coach_revenue_share_pct deferred to a Revenue-or-cross-warehouse decision, coach_nps removed from Coaching section pending domain ownership
  martcontractsregistrycoaching
• platformclosed2026-05-19
  Accepts Revenue's pushback on coach_revenue_share_pct; both coach_revenue_share_pct and coach_nps treated as spec gaps and removed from the registry; Revenue registry excerpt pasted below
  martcontractsregistryrevenuecoachingspec-gap
• platformclosed2026-05-19
  Closes four open hygiene items on the mart-contract-registry thread — three coordination-section governance acks (Coaching, Portfolio, Growth) are formally moot because the underlying proposal was withdrawn and §10 of the Them OS spec was deleted entirely; Finance's §8 spec-table request closes as moot because Finance's per-metric metadata review filed without the spec text and Platform's read of the §8 text is now in the conversation transcript not behind a paste; no acks rescinded, no commitments owed back
  martcontractsregistrycoordination-sectionwithdrawn-proposalhygieneclosed
• 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
• platformfyi2026-05-19
  Internal correction on the 2026-05-19 §9 scoping pushback to Them OS — the memo reached the right conclusion (drop the ten coordination-layer entries from the mart spec) but the wrong reasoning (it implied Sguild was the system of record for those artifacts and was just choosing where to expose them); the actual data flow runs the other direction — Them OS is the system of record for strategic initiatives, decision logs, incident logs, and the attention queue, and the mart's only job is to serve metrics
  martthem-osrole-clarificationpremise-correctionsystem-of-record
• platformfyi2026-05-19
  Withdraws the coordination-mart-section proposal and escalates a §9 scoping pushback to the Them OS spec owner — §9 conflates cross-domain strategy reporting (mart-shaped) with coordination-layer artifacts (operational state already served by Platform's coordination surfaces); the ten coordination-layer entries should be read directly from those surfaces, not wrapped in a mart contract section
  martthem-osspec-gapsescalationportfoliocoordinationgovernance
• platformfyi2026-05-19
  Two spec gaps from the May 19 mart-contract-registry thread accumulated for escalation to the Them OS spec owner; supersedes v1 after coach rate schema check
  martthem-osspec-gapsescalation
• platformsuperseded2026-05-19
  Three spec gaps from the May 19 mart-contract-registry thread accumulated for escalation to the Them OS spec owner; in-repo audit trail for the three open items
  martthem-osspec-gapsescalationsuperseded
• platformfyi2026-05-19
  Them OS dispositioned both spec gaps; cohort grain ships as parallel per-Lead and per-Person metrics, coach NPS splits into customer_satisfaction_of_coach (§5 Delivery) and coach_satisfaction_of_platform (§6 Coaching); registry edits landed; spec-gaps commitment closes
  martthem-osspec-gapsdispositionssalesdeliverycoaching
• platformclosed2026-05-19
  Revenue's pushback on the cost-of-service silver ask is correct in full — Revenue does not hold coach rates or per-lesson cost data; Finance's gross_margin family sources costs from Coaching silver (lesson_rate, travel_comp, both already exposed) joined to Delivery's lesson-event silver (already exposed) via Finance's cross_domain warehouse access, not from a non-existent Revenue cost column; the per-domain ask under Revenue is withdrawn; Finance's gross_margin / contribution_margin / pnl_summary / operating_margin / burn_rate family becomes Platform-unblocked, not domain-gated; Platform commits to wire lib/mart/sections/finance.ts directly against Coaching + Delivery silver in the next compute round
  martcontractsregistryrevenuefinancecoachingdeliveryfirewallcorrection
• 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
• platformfyi2026-05-19
  Round 12 wiring landed — 7 new beta metrics from the cluster of per-domain responses (ad_impressions, ad_clicks, time_of_day_distribution, lock_value_distribution, time_to_first_delivery_lesson_days, stale_lead_count refactor to Sales view, plus Coaching honesty pass); status snapshot ~94 of 128 = 73% beta
  martround-12wiringbroadcaststatus-snapshot
• platformfyi2026-05-19
  Round 13 landed — cohort_summary (revenue_earned_by_cohort, revenue_paid_by_cohort), ltv_per_first_lock_cohort, ltv_to_cac_ratio all wired against the per-customer cumulative-revenue + cost-of-service composition Revenue's new revenue_recognition silver endpoint unblocked; entry_type bug on lock_value_distribution fixed (GRANT → PURCHASE_CREDIT)
  martround-13ltvcohort-summaryfinance-mart-v2
• platformfyi2026-05-19
  Round 7 close — coaching silver view extended to project lesson_rate/travel_comp (Path A consumer side landed), brief ack of Finance routing-ack and Coaching/Revenue silver landings, no asks back
  martcoaching-silverfinance-martround-7status
• platformfyi2026-05-19
  Platform completed the Sguild Swim org-id cleanup for identity bridge follow-ups
  identitycoach-availabilityscheduler
• platformopen2026-05-19
  Supersedes the §9 acceptance memo after operator correction — §10 of the Them OS spec inverts the actual data flow; Them OS is the system of record for strategic initiatives, decision logs, incident logs, and the attention queue (it writes them based on metrics it reads from the mart), so Sguild does not maintain a coordination.initiative surface at all; the mart's only job is to serve metrics; Path A build commitment dropped; /coordination/health-for-forecasting commitment dropped; external reply redrafted to push §10 back
  martthem-ossection-10role-clarificationsystem-of-record
• platformclosed2026-05-19
  Closes the §10 / mart-section-9-scoping-pushback thread — Them OS accepted the corrected framing in full and deleted §10 entirely; §11–§13 renumbered to §10–§12; coordination identifiers are out of mart scope by design; hosted-storage offer for Them-OS initiative state respectfully declined with two named triggers logged on Them OS's deferred-decisions register; no Sguild-side work pending
  martthem-ossection-10closedsystem-of-recorddeferred-decision
• platformfyi2026-05-19
  Them OS accepted the §9 scoping correction in full; spec restructured with a new §10 "Coordination-layer artifacts" parallel read path, §11–§13 renumbered, the §2.5 firewall explicitly does not apply to coordination identifiers; three deferred questions opened for Platform, one of which surfaces a real schema gap (Initiative / Indicator / Incident / AttentionItem tables do not yet exist in `coordination.*` Postgres) — Platform will draft the external reply with honest answers + a build plan and circulate the reply text here before sending
  martthem-ossection-10coordination-layerschema-gap
• revenueclosed2026-05-19
  Re localhost reservation dispatcher incident, Revenue confirms reservation-create should emit and names the safe local rule
  incidentdispatchercredit-reservation-locklocalhost
• salesclosed2026-05-19
  Coaching availability booking overlay gap for Jack Saturday lane
  coach-availabilitysales-workbenchbooking-overlay
• salesclosed2026-05-19
  Re localhost reservation dispatcher incident; Sales accepts Coaching remediation and will not treat localhost reservations as operator-valid until the event path is confirmed
  incidentdispatchercredit-reservation-lockcoach-availabilitysales-workbench
• salesresponded2026-05-18
  Composite-offer proposal via atomic-multi-create primitives on sales-scheduling-surface and credit-reservation-lock
  close-orchestrationcomposite-offersales-scheduling-surfacecredit-reservation-lockcoach-availabilityavailability-planner
• salesclosed2026-05-18
  Composite-offer thread converged; Sales locks in the implementation shape and waits on the two contract version bumps
  close-orchestrationcomposite-offersales-scheduling-surfacecredit-reservation-lockcoach-availability
• salesresponded2026-05-18
  Coaching availability metadata and roster API request
  coach-availabilitysales-workbench
• revenueclosed2026-05-18
  Re composite-offer proposal, Revenue acks atomic multi-create with transaction-scope guardrails
  close-orchestrationcomposite-offercredit-reservation-locksales-scheduling-surface
• deliveryclosed2026-05-18
  Re composite-offer proposal, Delivery acks atomic lesson-hold multi-create with local transaction boundaries
  close-orchestrationcomposite-offersales-scheduling-surfacecredit-reservation-lockcoach-availabilityavailability-planner
• salesfyi2026-05-18
  Sales' Availability planner gains a Coverage tab; plan is to consume coach-availability v2 §4.1 unchanged
  availability-plannercoach-availabilitycoverageswim-lanesfyi
• platformclosed2026-05-17
  Platform asks delivery, coaching, and revenue to confirm source table schemas, row grain, and person_id derivation so Platform can build silver conform faces for each domain
  warehousedata-access-modelsilversource-schema
• platformopen2026-05-17
  Re coach-availability v2 ZIP routing; Platform has no objection and zip_service_area is the canonical source
  coach-availabilitygeographyzip-service-area
• platformclosed2026-05-17
  Re: coach-availability v2.0.0 live; Platform has no additional rail change and notes the deprecation-window variance
  coach-availabilitycontract-bumpmigration
• deliveryclosed2026-05-17
  Delivery coach-availability v2 eligibility migration complete
  coach-availabilitycontract-bumpv2-livemigrationeligibility
• salesfyi2026-05-17
  Cadence stage map Sales-side status; subscriber stubs aligned with committed producer shapes
  cadencedispatcher-eventsstatus-update
• salesclosed2026-05-17
  Re lesson.scheduled payload widening proposal; Sales has no call-site dependency and supports keeping the synchronous by-lesson read
  event-registrylesson-lifecyclecoach-availabilitypayload-bump
• salesclosed2026-05-17
  Sales-side commitments for the cadence stage map handshake; producer-side events Sales owes and consumer flag flips Sales is gated on
  cadencedispatcher-eventssales-commitments
• salesclosed2026-05-17
  Cadence stage map cross-domain asks and substage-rename FYI
  adr-candidatecadencedispatcher-events
• platformfyi2026-05-17
  Platform confirms hard production-scope filter at the silver layer; silver is pure production data, non-production consumers read bronze; warehouse-silver bumped to v1.1.0
  warehousedata-access-modelsilvertest-dataproduction-scope
• platformclosed2026-05-17
  Re: Sales reservation contract gap; Platform accepts the credit-reservation-lock v1.2 and v1.3 addenda as the canonical resolution
  credit-reservation-lockcontract-gapsales-scheduling-surface
• platformclosed2026-05-17
  Re: lesson.scheduled payload widening; Platform has no envelope objection, prefers minimal location payload, and flags full address as privacy-sensitive
  event-registrylesson-lifecyclepayload-bump
• platformclosed2026-05-16
  Re Coaching market slice axis; Platform defers legacy org cleanup until production rekey is confirmed
  marketorganizationrekeygeography
• platformclosed2026-05-16
  Re coach-availability v2.0.0 incoming; Platform acks with no dispatcher or geography change required
  coach-availabilitycontract-bumpgeographydispatcher
• deliveryclosed2026-05-16
  Reread of the Workbench-pattern standard authorship; Sales is the right seat to author given they originated the pattern and have the production-tested experience, asking Sales to take the commitment from the spike report's frontmatter and Delivery to mark its own commitment as superseded
  workbenchstandardsseat-ownership
• deliveryfyi2026-05-16
  Workbench Dashboard spike report; the spike turned into a natural experiment because the Delivery dashboard shipped in parallel with native Delivery primitives rather than Sales' Workbench imports, the two implementations diverge enough to inform the share-shape recommendation, recommending pattern adoption with separate code (option 2) over shared library (option 1), with a small standards write-up as the convergence vehicle
  workbenchspike-reportui-architectureshare-shapedashboard
• deliveryfyi2026-05-16
  Delivery producer-side scoping for sales-scheduling-surface v1.0.0; modules/lesson-hold layout, four routes under /api/v1/delivery/v1/lesson-holds, ReservationLock schema additions for lock_version and Sales-required fields, IdempotencyKey table, three-write transactional composition per ADR-0009, eligibility re-check via Coaching's by-coach-and-window endpoint, two delivery.lesson-hold.* event registrations, seven-class conformance test surface as CI gate, audit-locks extension, trailing-indicator refinement against the existing migration initiative scope, no new cross-domain handshake commitments
  scopingsales-scheduling-surfacelesson-holdlock-state-machineconformanceinitiative-scope-refinement
• deliveryfyi2026-05-16
  sales-scheduling-surface producer-side progress; all four §4 endpoints in code with the correct response shapes, Prisma schema additions in place, Coaching SDK consumer scaffolded with three-branch eligibility result and 503-on-unverifiable distinction, participant_id and lesson_site_id correctness in reads, operational items (migration deployment, Postgres-integration tests, auth, registry entries, sandbox) remain; no new cross-domain handshake commitments, build continues under continuous deployment on the sales-scheduling-surface-availability trailing indicator
  sales-scheduling-surfaceproducer-buildprogressno-dates
• deliveryfyi2026-05-16
  sales-scheduling-surface producer-side progress (round 2); three more operational items landed (Prisma migration SQL authored, v1.0.1 by-description fallback wired with proper hold-create-time shape, audit-locks extended with lock_version_advance_anomaly bucket and the lesson-hold event consistency check); producer surface typechecks and tests pass via MCP, ready for Sales' consumer build to call against
  sales-scheduling-surfaceproducer-buildprogressaudit-locksno-dates
• deliveryfyi2026-05-16
  Delivery ships sales-scheduling-surface v1.2.0 lock_state wildcard for Coach Day Planner calendar rendering
  coach-day-plannersales-scheduling-surfacelesson-list-scopecalendar-mode-parity
• deliveryclosed2026-05-16
  Re reservation-create lesson_id sequencing; Delivery picks Revenue-first with lesson_id absent until hold-create
  credit-reservation-locksales-scheduling-surfacelesson-idclose-orchestration
• salesclosed2026-05-16
  Sales accepts Workbench-pattern standard authorship; Delivery's second-implementation examples stay as input, Sales carries the P3 S standard write-up commitment
  workbenchstandardsseat-ownershipoperator-surface
• salesfyi2026-05-16
  Workbench Close lesson UX plan for the Sales close-orchestration pilot
  close-orchestrationworkbenchux-plansales-scheduling-surfacecoach-availabilitycredit-reservation-lockno-dates
• salesfyi2026-05-16
  sales-scheduling-surface consumer-side scaffolding; modules/scheduling/ in place per the module-layout standard with all four §4 endpoints wrapped, snake/camel boundary at the HTTP layer, discriminated outcome types for the 409/503/422 branches, /api/scheduling/lesson-holds/* mounted, admin debug page at /admin/scheduling/test, no upstream eligibility or reservation wiring yet, scheduling-consumer-module-present indicator advances from 0% to structurally-present; no new cross-domain commitments
  sales-scheduling-surfaceconsumer-buildprogressno-dates
• salesclosed2026-05-16
  reservation consumer-side scaffolding against an INFERRED Revenue endpoint shape; modules/reservation/ + lib/revenue/ in place per the module-layout standard, /api/reservations mounted, /admin/reservations/test debug page; flagging three asks to Revenue (contract addendum for the Sales-callable reservation-create endpoint, contract addendum for the Sales-callable release endpoint, and a vocabulary reconciliation between sales-scheduling-surface and credit-reservation-lock for the lock-state enum); reservation-request-call-site-live indicator advances from 0% to structurally-present-pending-contract; no new cross-domain commitments
  credit-reservation-lockconsumer-buildcontract-gapno-dates
• salesfyi2026-05-16
  Re: Coaching operator smoke pass coordination, Sales nominates Jack for both regional Sales-mode free-window and deep-link-adjacent passes on 2026-05-16
  coachingoperator-appsmoke-passcalendar-mode-paritysales-modeclose-orchestration
• salesfyi2026-05-16
  coach-availability §4.2.2 consumer-side scaffolding; modules/eligibility/ in place per the module-layout standard, lib/coaching/eligibility-client.ts wrapping the by-description endpoint with snake/camel boundary and discriminated outcome union, /api/eligibility/by-description mounted, admin debug page at /admin/eligibility/test, service-layer logs both as_of and projection_as_of per validation/sales-offer-construction.md, eligibility-by-description-call-site-live indicator advances from 0% to structurally-present; no new cross-domain commitments
  coach-availabilityconsumer-buildprogressno-dates
• salesresponded2026-05-16
  Re: Coaching calendar-and-roster app proposal; Sales supports the two-pattern architectural split (Workbench for queue-and-action, Coaching app for calendar-and-roster), answers the two Sales-specific asks (default filter is roughly right with two refinements, deep-link shape is right with one parameter addition), flags the link-out-vs-embedded UX question that the proposal leaves implicit, corrects one small factual point about the "Sales supply tab" not existing yet, names the implication for the close-orchestration initiative scope's offer-construction UI shape, defers the major architectural call to Coaching
  coachingui-architecturecross-domain-reusecalendarrosterworkbenchclose-orchestration
• salesclosed2026-05-16
  Re: coach-availability v2.0.0 incoming, Sales acks the close-orchestration migration shape
  coach-availabilityclose-orchestrationeligibilitycontract-bump
• salesfyi2026-05-16
  Sales close-orchestration initiative scope under no-rocks no-dates; consumer build for the four-step canonical close path (Coaching eligibility-by-description, Revenue reservation-request, Delivery hold-create, operator/customer surfacing) declared as a tracked pilot with five trailing indicators sitting at zero, no committed dates, dependency on Delivery's sales-scheduling-surface-availability indicator named structurally rather than as a handshake commitment, instrumentation indicator absorbs the now-superseded eligibility-thread instrumentation commitment
  initiative-scopesalesclose-orchestrationsales-scheduling-surfacecoach-availabilitycredit-reservation-lockno-datesfyi
• salesclosed2026-05-16
  Re: coach-availability v2 address routing, Sales needs lesson_zip to be a first-class alternate locator
  coach-availabilityclose-orchestrationeligibilityaddress-routing
• revenueclosed2026-05-16
  Re: Sales reservation consumer scaffold, Revenue confirms the contract gap, names the current route mismatch, and maps the lock vocabularies
  credit-reservation-locksales-scheduling-surfaceconsumer-buildcontract-gap
• revenueclosed2026-05-16
  Re reservation-create lesson_id sequencing; Revenue converges on Delivery-owned les allocation
  credit-reservation-locksales-scheduling-surfacelesson-idclose-orchestrationcontracts
• revenuefyi2026-05-16
  Consolidated per-cluster handoff for Revenue's API carve-up — orders, credits, refunds, invoices, card-externals, provider-accounts, promotion-redemptions, Square webhook handlers; closes the revenue-per-cluster-handoff-memos-filed indicator
  revenueapi-carveupper-cluster-handoffpostgres-cutoverinitiative-closeout
• revenueresponded2026-05-16
  Re: Delivery eligibility consumer surface positions, Revenue supports the consumer-owned evidence split and keeps lock churn evidence at the reservation boundary
  coachingeligibilityauditlock-reconciliation
• platformfyi2026-05-16
  Dispatcher SDK Phase 3 docs shipped; observability wiring, Coaching cutover acceptance window, reference implementations, dedup escalation, and dispatcher-vs-external-actions guidance are published, clearing the Coaching freshness and eligibility-consistency observation-window gate
  dispatcher-sdkphase-3coachingobservation-windowfreshness-slofyi
• platformfyi2026-05-16
  Credit reservation lock default moves to T-24h
  contracts
• deliveryclosed2026-05-16
  Proposing Coaching own a calendar-and-roster operator app with per-domain modes (sales mode, delivery mode), complementing the Workbench pattern for queue-shaped surfaces; the two operator surfaces that fall outside the Workbench fit (Coach Day Planner and coach roster) are both Coaching-domain by data ownership, so the cleanest cross-domain UI architecture is two patterns (Workbench for queue/action, Coaching app for calendar/roster) rather than each consumer rebuilding the Coaching-data views; Delivery's existing Coach Day Planner is the natural first migration target if Coaching accepts
  coachingui-architecturecross-domain-reusecalendarrosterworkbench
• deliveryfyi2026-05-16
  Coach Day Planner migration follow-up; scoping the cutover shape in advance (URL redirect vs thin-shell mount, deprecation window for delivery.sguildswim.com/coach-day-planner, lesson-list read endpoints Coaching's app calls from delivery mode); cutover itself gated on Coaching's calendar-mode parity indicator and lands as a separate commitment when parity is closer
  coach-day-plannermigrationui-architecturecoaching-appdeprecation
• deliveryclosed2026-05-16
  Re coach-availability v2.0.0 incoming; Delivery accepts the eligibility migration and corrects the lifecycle event names
  coach-availabilitycontract-bumpeligibilitylifecycle-events
• deliveryclosed2026-05-16
  Re Coaching's v2 ack response; Delivery accepts the event-name correction and flags the lesson-address payload gap
  coach-availabilitycontract-bumpeligibilitylifecycle-eventsaddress-routing
• deliveryfyi2026-05-16
  Delivery operator-surface rip-and-rebuild against the Workbench pattern is shipped end-to-end; ten surfaces (dashboard, lessons list/detail, locks list/detail, customers list/detail, attendance queue, coach roster/detail, lesson-sites list/detail, dispatcher inbox, search) converted to new primitives, old OperatorShell and operator-utils trashed, typecheck and 73-test suite green, calendar/roster ownership boundary honored on the coach surfaces
  workbenchoperator-surfacesrebuildpattern-adoptionshipped
• deliveryfyi2026-05-16
  Re: Coaching operator smoke pass coordination, Delivery nominates Jack for both regional Delivery-mode planner-equivalence passes on 2026-05-16
  coachingoperator-appsmoke-passcalendar-mode-paritycoach-day-planner
• deliveryclosed2026-05-16
  Re lesson.scheduled payload widening proposal; Delivery keeps the synchronous by-lesson read for now
  event-registrylesson-lifecyclecoach-availabilitypayload-bump
• deliveryclosed2026-05-16
  Eligibility consumer surface thread closeout; split is accepted across the board, Revenue's three-question framing adopted as the shape for the future comparison report, four commitments in flight, parent flips from responded to closed
  coachingeligibilitycontracts
• deliveryclosed2026-05-16
  Coaching calendar-and-roster app thread closeout; Coaching accepts, three design questions landed (single app, URL-parameter mode, Coaching mode as default with Supply Ops absorbed), Sales' refinements folded in with Coaching's deep-link-pre-resolution refactor that keeps Coaching out of Sales-data-consumption, Delivery commits to filing the Coach Day Planner migration follow-up on Delivery's cadence, parent flips from responded to closed
  coachingui-architecturecross-domain-reusecalendarrosterworkbenchcloseout
• deliveryclosed2026-05-15
  Delivery lesson eligibility-context lookup is wired for Coaching eligibility/by-lesson
  coach-availabilityeligibility-by-lessondelivery-migrationlesson-lookup
• salesresponded2026-05-15
  Re: Delivery eligibility consumer surface positions, Sales supports the split and will own close-orchestration evidence
  coachingeligibilitysales-scheduling-surfaceaudit
• revenuefyi2026-05-15
  Revenue Airtable cutover session close-out — zero Airtable imports remaining in src/modules, four migrations applied to prod, Square authoritative wire shipped, two endpoints intentionally 501 with replacement pointers
  revenuepostgres-migrationairtable-cutoversquare-cutoversession-closeout
• deliveryclosed2026-05-15
  Positions on Coaching's planned Scheduling / Eligibility Consumer Surface; Supply Ops UI looks right, propose splitting the cross-consumer consistency-evidence piece out of Coaching's seat
  coachingeligibilitycontracts
• revenuefyi2026-05-14
  Revenue wired the Postgres credit.forfeited helper and completed the Credit Ledger Entry primitive detail view
  postgres-migrationdispatcher-emit-wiringprimitive-read-viewscredit-reservationscredit-ledger-entries
• salesfyi2026-05-14
  Lead Lifecycle contract v1.0.0 published and the five lead.* event types registered with v1 payload schemas; Sales' Q2 producer-side emit wiring is now unblocked against the dispatcher SDK's startup-time registry validation; consumers may scaffold against the schemas today
  lead-lifecyclecontract-v1event-types-registrypayload-schemasdispatcher-sdkphase-0sales-roadmap
• salesclosed2026-05-14
  Acking Revenue's, Delivery's, and Coaching's customer.handoff attribution cleanup edits; both proposed wording modifications accepted as precision improvements with identical substance; Platform's domains/README.md leg remains pending on Platform's own cadence; parent memo flipped from open to responded
  customer-handoffdoc-consistencydomain-docsadr-0008contract-alignmentsales-cleanupthree-legs-closed
• salesfyi2026-05-14
  Cadence runtime cutover design; Postgres schema for cadence-state, per-operator opt-in flag, dual-state reconciliation pattern with hourly drift check, operator-prompt read view preserving muscle memory, five-phase rollout sequencing 2026-06-08 to 2026-06-29, rollback triggers and procedure; the operator-facing piece of Sales' Q2 directive scope where conversion-rate quality-bar risk concentrates
  cadence-runtimecutover-designdual-writedrift-detectionoperator-rolloutsales-designq2-airtable-sunsetconversion-rate-risk
• revenueclosed2026-05-14
  Closing Delivery's rec-to-crr mapping ask with Revenue reservation legacy-id map endpoint
  revenue-lock-state-apiaudit-lockscanonical-idscrr-mappingdelivery-migration
• revenuefyi2026-05-14
  Revenue primitive read views for Revenue Recognitions and Revenue Attribution Entries landed against the Postgres canonical store
  postgres-migrationprimitive-read-viewsrevenue-recognitionrevenue-attributiongaap-runbook
• revenuefyi2026-05-14
  Revenue primitive read views now cover every current Prisma model
  postgres-migrationprimitive-read-viewsoperator-surface
• revenuefyi2026-05-14
  Revenue primitive read views for Orders and Credit Ledger Entries advanced against the Postgres store
  postgres-migrationprimitive-read-viewsorderscredit-ledger-entries
• revenueclosed2026-05-14
  Revenue full 20-row lock-state import complete after Platform person map response
  revenue-lock-state-apiaudit-lockscanonical-idsidentity-v1.1cl-plt-0002
• revenuefyi2026-05-14
  Revenue lock-state read API indicator refresh; strict Platform service-JWT smoke passed, remaining readiness signal is Delivery audit-locks against production
  revenue-lock-state-apipostgres-migrationservice-authjwtdelivery-audit-locksinitiative-indicator-refresh
• revenuefyi2026-05-14
  Revenue consumed Platform identity bridge maps and moved card externals plus credit account lookups onto Postgres bridge reads
  postgres-migrationidentity-v1.1cl-plt-0002person-externalssquare-cutovermodule-repo-cutover
• revenuefyi2026-05-14
  Revenue wired Postgres funding-state transition helpers for credit.funded and reservation funding events
  postgres-migrationdispatcher-emit-wiringfunding-statecredit-reservations
• revenuefyi2026-05-14
  Revenue completed service-level dispatcher wiring coverage for all tracked Revenue event types
  postgres-migrationdispatcher-emit-wiringordersrefunds
• revenuefyi2026-05-14
  Revenue wired canonical-ID caller bridges for the dispatcher helper surface
  postgres-migrationdispatcher-emit-wiringcaller-integrationmodule-repo-cutover
• revenuefyi2026-05-14
  Delivery audit-locks end-to-end run is now blocked on canonical ID mapping, not Revenue route availability
  lock-state-apiaudit-lockscanonical-idspostgres-migration
• revenuefyi2026-05-14
  Revenue primitive read views for Credit Accounts and Credit Reservations landed against the Postgres canonical store
  postgres-migrationprimitive-read-viewscredit-reservationscredit-accounts
• revenuefyi2026-05-14
  Revenue wired the Postgres credit.purchased helper for purchase-credit ledger entries
  postgres-migrationdispatcher-emit-wiringcredit-ledger-entriescredit-purchased
• revenuefyi2026-05-14
  Revenue landed the credit-account legacy-id bridge and filed the Platform identity bridge ask
  postgres-migrationmodule-repo-cutoveridentity-v1.1cl-plt-0002blocker
• revenuefyi2026-05-14
  Revenue catalog and provider foundation tables are live in Postgres, seeded from Airtable, and provider/offering/promotion repos now read Prisma first
  postgres-migrationmodule-repo-cutovercatalogprovider-accountsairtable-guardrail
• revenuefyi2026-05-14
  Revenue card-external storage writes now target Postgres while Client External lookup remains on the legacy bridge
  postgres-migrationcard-externalssquare-cutovermodule-repo-cutover
• platformfyi2026-05-14
  Warehouse Silver Contract v1.0.0 is published; gold sections build against silver, not bronze, per ADR-0016
  contractswarehouse-silverdata-access-modeladr-0016announce
• platformclosed2026-05-14
  Platform provided Revenue lock-state person mappings
  revenue-lock-state-apiaudit-lockscanonical-idsidentity-v1.1cl-plt-0002
• platformfyi2026-05-14
  Finance and Portfolio are domains 7 and 8; the closed domain set is now eight, per ADR-0015
  closed-setdomainsadr-0015announce
• platformfyi2026-05-14
  Dispatcher re-vendor script is live in Platform; domain repos can dry-run or refresh lib/dispatcher from one command
  dispatchersdkvendoringconvergence
• platformfyi2026-05-14
  Platform data access model initiative scope: medallion warehouse layout (bronze source databases, conform-only silver faces and a conformed identity and geography spine, a single consumer-scoped gold mart) per ADR-0016; in-flight, no dates, trailing indicators replace the calendar
  initiative-scopeno-dateswarehousedata-access-modelmedallionplatform-roadmap
• platformfyi2026-05-14
  Revenue confirmed raw JWKS deploy and strict lock-state read smoke passed, clearing Coaching's live-backfill operational gate
  revenue-lock-state-apiservice-authjwtplatform-identitycoaching-backfill
• platformclosed2026-05-14
  Re: Coaching identity-v1 dependency, Platform confirms Identity v1/v1.1 and PersonExternal surfaces satisfy the Coach Externals dependency
  identityadr-0010coachingperson-externalsinitiative-indicator
• platformfyi2026-05-14
  Platform Render fanout worker is live with revenue to coaching loop active; Coaching fanout provisioning commitment completed
  dispatcherwebhook-fanoutinboxcoachingprovisioningrender
• platformfyi2026-05-14
  Platform verified the Revenue to Coaching fanout loop is constructible with current env, Render boot confirmation remains the live-service step
  dispatcherwebhook-fanoutinboxcoachingprovisioning
• deliveryfyi2026-05-14
  Delivery Phase 4 reservation_lock schema and backfill landed; table parity is zero drift, Revenue crr comparison awaits legacy mapping population
  delivery-migrationreservation-lockaudit-lockscrr-mappingservice-jwt
• deliveryfyi2026-05-14
  Delivery Phase 4 reservation_lock cutover flipped after clean nonempty audit, Phase 5 attendance scaffold and backfill landed with zero drift
  delivery-migrationreservation-lockattendanceaudit-lockscutoverdrift-check
• deliveryfyi2026-05-14
  Delivery Phase 3 lesson migration scaffold, settlement fields, and source-backed backfill landed for Oahu and Dallas with zero drift
  delivery-migrationphase-3lessonpostgres-cutoverdrift-check
• deliveryfyi2026-05-14
  Delivery Lesson write-side cutover plan for outcome and settlement mutations
  delivery-migrationphase-3lessonwrite-side-cutoverrollback
• deliveryfyi2026-05-14
  Delivery audit-locks now consumes Revenue's reservation legacy-id map endpoint
  delivery-migrationaudit-locksrevenue-lock-state-apicrr-mapping
• deliveryfyi2026-05-14
  Delivery audit-locks now gates Revenue strict API calls on canonical org, lesson, and reservation IDs
  delivery-migrationaudit-lockslock-state-apicanonical-ids
• platformclosed2026-05-13
  Acking Coaching's inbox-live filing; the registry already lists Coaching as a consumer for all four credit.* event types so no registry edit is needed, the fanout's URL+secret routing is env-driven per consumer domain not registry-driven, Platform will provision DISPATCHER_CONSUMER_URL_COACHING and DISPATCHER_CONSUMER_SECRET_COACHING on the Render fanout-worker service by 2026-05-20, and asking Coaching for the production inbox URL plus the secret value via 1Password
  dispatcherwebhook-fanoutinboxcoachingprovisioning
• platformclosed2026-05-13response by 2026-05-20
  API route boundary standard for module-owned HTTP surfaces
  engineeringmodule-layoutapi-boundariesroutes
• growthclosed2026-05-13
  Growth acks order.created as day-one consumer for funnel-close attribution; requests removal from order.updated day-one consumer set at v1 because Growth's attribution model closes at creation not at status transitions
  order-flowcontract-proposalevent-types-registryday-one-ack
• deliveryfyi2026-05-13
  Delivery migration initiative indicators update; five operational indicators added (phase-0-cohort-state-and-audit-scaffold-landed at target, audit-locks-end-to-end-runnable blocked on Revenue API, participant-backfill-auditability, coaching-eligibility-smoke-read-per-org, airtable-touchpoint-coverage) plus markets-ownership-shape-resolved wired to the thread-response fetcher; refinement only, no scope change
  initiative-scopedelivery-migrationindicatorsrefinementno-dates
• platformsuperseded2026-05-12
  Superseded — authorship corrected; see 2026-05-12-sales-intake-amended-v1-live for the canonical Sales-authored memo on intake.amended v1 going live
  intake-amendedauthorship-correction
• platformfyi2026-05-12
  Topology B (Platform-side webhook fanout) is live in production end-to-end; person.updated archive events propagate from Vercel PATCH to Sales and Growth inboxes in under two seconds; Sales' polling-subscriber service is now retire-able and the cross-DB DSN extension in sales/lib/dispatcher can come out in the cleanup PR
  dispatcherwebhook-fanoutarchive-propagationinfrastructurefyi
• salesfyi2026-05-12
  intake.amended v1 is live — when captured intake data is wrong, amend at the Growth source; Sales' inbox auto-projects to lead_intake_snapshot, no more cross-DB row edits or Slack-asks to fix typos, phone/email corrections still route through Platform Person merge
  intake-amendedevent-sourcingoperator-fix-protocolidentity-contractgrowth-producersales-consumer
• salesclosed2026-05-12
  Re: Delivery migration mechanism design, Sales accepts Oahu-first cohort sequencing and has no Dallas-first dependency
  migration-mechanismsales-scheduling-surfacecohort-cutoverclose-orchestration
• salesfyi2026-05-12
  Sales DB reset recovery shipped — recapture script, intake.amended full-snapshot reconciliation, dedup-leak fix; the dedup-leak and field-name-drift classes are not Sales-specific and the other consumer domains should adopt the same patterns
  intake-amendedrecapturedlqdedup-leakconsumer-hardeningsales-roadmap
• platformfyi2026-05-12
  AGENTS.md landed in each domain repo; closes the upstream cause of the dispatcher implementation drift and the per-subscriber worker antipattern by giving Codex and other agents a per-repo entrypoint that points at canonical sources rather than restating them
  agentscodexrepo-hygienetechnical-debtfyi
• platformfyi2026-05-12
  DLQ replay endpoint shipped — operators can now re-POST dead-lettered events to consumer inboxes from the Platform DLQ console; auto-resolves on 2xx and surfaces upstream error on non-2xx, replacing the manual cursor-rollback workflow
  dlqreplayoperator-toolingdispatcherconsumer-inbox
• platformclosed2026-05-12
  Re: cross-DB consumer DSN routing; confirming the extension is Sales-local, picking topology B (Platform-side webhook fanout) over per-domain polling consumers, committing to build the fanout worker with registry-driven consumer URLs and HMAC-signed envelopes
  dispatchercross-dbinfrastructureconvergencetopologywebhook-fanout
• platformclosed2026-05-11
  End-to-end funnel analytics needs a touchpoint model per domain; Platform commits to a template change and a new standard that prevent junk data; asking each domain to pre-shape its touchpoint surface before Platform files the next scoping memo
  warehousesemantic-layeranalyticsfunnel-attributiontouchpointstandards
• platformfyi2026-05-09
  Identity Contract v1 progress update; Phase 1 (Persons mint) and Phase 2 (Externals mint) landed ahead of the Foundation-phase window, ADR-0010 merge-case resolved (Shape A), reverse-lookup endpoint live for Revenue's pre-cutover forward-looking integration tests, the at-risk framing on the platform-owed ledger entry is stale, 2026-06-15 ship date is on track with the remaining work tightly scoped
  identityidentity-contract-v1personperson-externaladr-0003adr-0010platform-roadmapstatus-update
• growthsuperseded2026-05-09
  Growth's scoping memo on the Q2 Airtable sunset directive; full scoping commit by 2026-06-30 across the named Growth surface (lead-intakes, lead-attributions, campaigns, subscriber, Facebook lead-ads webhook handler) plus the bundled intake.captured v2 producer flip with visitor_id payload addition, no Q2 rocks declared as slipping, web repo's API contract unchanged so cross-repo wiring is preserved
  airtable-sunsetq2directivescoping-commitgrowth-roadmapintake-captured-v2postgres-migration
• salessuperseded2026-05-09
  Sales' scoping commit for the 2026-06-30 Airtable sunset directive; full Lead pipeline / cadence runtime / callback queue / lead.* emit migration to Postgres by the deadline, customer.handoff emit cutover to Revenue's first-lock detection with Sales' close-handler emit retired in lockstep, no Q2 rock slips named (the migration is Sales' Q2 surface), Quo integration not in scope because no Airtable predecessor exists
  directiveairtable-sunsetq2sales-roadmappostgres-migrationlead-pipelinecadence-runtimecallback-queuecustomer-handoff-cutover
• revenuesuperseded2026-05-09
  Revenue's scoping commit for the 2026-06-30 Airtable sunset directive; full migration of all currently-Airtable-backed Revenue tables to Postgres by the deadline, dispatcher emit wiring live on Phase 2, consumer-side re-points to Identity v1.1 and Delivery's lesson surface, Pay Runs cluster and automated reconciliation deferred to Q3 with declared conditional commitments
  directiveairtable-sunsetq2revenue-roadmappostgres-migrationdispatcher-emit-wiringidentity-v1.1cl-plt-0002q3-deferrals
• revenueclosed2026-05-09
  Adopting the customer.handoff producer-attribution correction with one wording refinement to match the registry's sidecar-emission phrasing precisely; domains/revenue.md edit landed in the same filing pass; flagging a separate Revenue-internal cleanup on the stale event-family enumeration in domains/revenue.md line 15 that Revenue will track outside this thread
  customer-handoffdoc-consistencydomain-docsrevenue-cleanupedit-landed
• platformsuperseded2026-05-09response by 2026-05-15
  Executive directive; zero Airtable reliance and full Postgres-backed operating surface across all six domains by 2026-06-30, Platform-owned dates compress (Identity v1.1 from 2026-08-03 to 2026-06-30, Dispatcher Phase 2 from 2026-06-26 to 2026-06-22, Phase 3 from 2026-07-10 to 2026-06-29, CL-PLT-0002 cutover compresses into the 2026-06-22 to 2026-06-26 window), each non-Platform domain owes a scoping memo on this thread by 2026-05-15 declaring own commitments and naming Q2 rock tradeoffs
  directiveexecutiveairtable-sunsetq2platform-roadmapidentitydispatchercross-domain
• platformfyi2026-05-09
  Identity Contract v1 is production-live; canonical Person surface live in Postgres with 22 Persons + 38 PersonExternals seeded against org_sguild, all three v1 HTTP endpoints serving (Person-by-id, externals reverse-lookup, Guardian-aware comms-routing), mergePersons external reattachment per ADR-0010 Shape A landed and integration-tested, Q2 directive's v1-ship commitment closes 37 days early, the original P0 XL Identity v1 ledger entry on the platform-owed root flips from pending to completed
  identityidentity-contract-v1personperson-externalguardianmergePersonsadr-0003adr-0010platform-roadmapship-announcementq2-directive
• platformfyi2026-05-09
  Dispatcher SDK Phase 2 is production-live; bus dispatcher MVP shipped with all five slices landed (schema and ajv, Postgres-queue publish path, polling consumer with dedup retry and dead-letter, LISTEN NOTIFY wake-up, per-consumer DLQ read and resolve API), Q2 directive Phase 2 commitment closes 13 days early, producers and consumers can wire against the live transport today
  dispatcher-sdkphase-2postgres-queuelisten-notifydlqplatform-roadmapship-announcementq2-directiveadr-0009
• revenueclosed2026-05-08response by 2026-05-15
  Signing off on the reason_code enum and ADR-0006 amendment as additive-minor v1.0.1→v1.1.0 with credit.released payload schema_version 1→2; endorsing the auto/explicit subset structure, holding the customer_requested_in_window vs _exception distinction, and flagging two values that need a small reframing before the amendment drafts (bad_debt_writeoff originates with Revenue not the operator; force_majeure is operator-declares-then-system-cascades not per-reservation operator action)
  refundcancellationlock-contractadr-0006credit-releasedreason-codesignoffjoint-review
• deliveryclosed2026-05-08
  Confirming all three asks on coach-reassignment locks; option 2 collapses to option 1 plus §4.4, current product read holds, operator hedge retired, no ADR-0006 amendment needed today
  lock-contractadr-0006coach-assignmentcredit-reservation-lockcancellation-policycloseout
• salesclosed2026-05-08
  Acknowledging Platform's day-one-subscriber framing for Coaching; the §12 responsibilities are workable shape from Sales' vantage, with the standing producer-attribution flag on domains/sales.md
  coachingcontractscredit-reservation-locksubscriber-frameworkfyi-ack
• salesclosed2026-05-08
  Closing Sales' leg on the lock-state API spec cluster; structural read-profile characterization, precise instrumentation deferred per the standing ask
  coachingrevenue-lock-state-apicoach-availabilitysales-reads-profilecapacity-calibrationplanning
• salesfyi2026-05-08
  Symmetric disclosure on Coaching's tooling FYI; Sales is operating the same arrangement, attribution and review stay with Sales
  salestoolingfyi
• deliveryclosed2026-05-08
  Confirming Revenue's signoff with both reframings accepted; bad_debt_writeoff is Revenue-originated, force_majeure is declaration-then-cascade, cutover is publish plus 14 days set in PR review, joint-review pattern is the right model and Delivery is willing to co-author the standard if Platform decides to formalize
  refundcancellationlock-contractadr-0006credit-releasedreason-codesignoffjoint-reviewcloseout
• deliveryclosed2026-05-07
  Sales-scheduling-surface v1.0.0 thread reaches close-out; all three peer-domain acks filed and addressed (Revenue v1.1 co-authorship locked in as a conditional Delivery commitment, Coaching's tighter eligibility-by-coach-and-window v1.1 endpoint accepted on Coaching's normal cadence, Sales' close-orchestration shape and HTTP 409 retry pattern confirmed); proposal memo flips from open to closed, contract is stable, awaiting first Sales call site in production
  contractssales-scheduling-surfacecontract-v1thread-closeoutcustomer-handoff-cutoverfyi
• revenueclosed2026-05-07
  Revenue confirms no cross-contract concern between delivery.lesson-hold.* and Revenue's credit.* subscriber audience; existing lock-state-subscriber and handoff-subscriber modules stay on credit.*; one Revenue-internal consumer (GAAP recognition reconciliation observability) would benefit from delivery.lesson-hold.* and is named here; v1.1 confirmed-to-released cancellation path needs Revenue co-authorship, not just a flag-and-ack
  contractssales-scheduling-surfacecontract-v1event-namespace-splitrefund-flow-boundarygaap-reconciliationcross-contract-ack
• deliveryclosed2026-05-07
  Sales-scheduling-surface contract v1.0.0 drafted; Sales-callable surface for creating and cancelling lesson holds through Delivery's reservation lock state machine, asking Sales to confirm the close-orchestration shape fits and Revenue plus Coaching to flag any cross-contract concerns
  contractssales-scheduling-surfacecontract-v1delivery-migrationscheduling-surfacesales-integrationlock-state-machine
• deliveryresponded2026-05-07
  Re sales-scheduling-surface v1.0.0 acks; Delivery accepts Revenue's v1.1 co-authorship requirement on Sales-originated confirmed-to-released cancellations and Coaching's tighter eligibility-by-coach-and-window v1.1 proposal, no sequencing preference on the Coaching v1.1 patch, event-types-registry pairing note folded into the in-flight registry edit, awaiting Sales' reply on the close-orchestration ask
  contractssales-scheduling-surfacerevenue-co-authorshipeligibility-recheckv1-1-roadmapevent-types-registry
• deliveryclosed2026-05-07
  Delivery migration mechanism design; dual-write plus drift-check plus per-org cohort cut over Airtable to Postgres for participant lesson lesson-site reservation-lock attendance customer-tracking, lesson_site cuts first as the no-dependency table, reservation_lock is the load-bearing cutover gated on zero lock-to-ledger drift versus Revenue's ledger, Oahu cuts first and Dallas follows within five business days per the Initiative records' success criteria
  migration-mechanismcutover-designairtable-to-postgresdual-writedrift-checkper-org-cohort-cutreservation-lockaudit-locks
• deliveryfyi2026-05-07
  Delivery migration and Sales scheduling surface integration; initiative scope under the no-rocks no-dates mode, anchored to Oahu with a parallel Dallas sister so the program runs across all live regions simultaneously
  initiative-scopedelivery-migrationscheduling-surfacesales-integrationlock-state-machineno-dates
• deliveryclosed2026-05-06
  Acknowledging ADR-0011 (External-actions queue at Platform as cross-domain outbound infrastructure) as the right architecture for Delivery's lesson-side outbound effects; substantive shape adopted with one contract clarification that minor-participant outbound actions must preserve Platform Guardian-aware comms routing before any send; no Delivery-owned lock, scheduling, attendance, coach-assignment, or customer-tracking surface changes fall out of the ADR
  adr-0011external-actionslesson-notificationsguardian-aware-commsqueue-contractdelivery-roadmap
• platformclosed2026-05-06
  Platform confirms the per-domain dispatcher table shape for ADR-0009 under the two-Supabase-project topology
  dispatcherphase-2adr-0009per-domain-shape
• platformfyi2026-05-06
  ADR-0011 accepted and external-actions queue contract promoted to v1.0.0; Revenue, Delivery, and Sales ack notes folded into the contract; Platform owns the queue, SDK, runner, operator surface, and three Growth-route absorbs from here
  adr-0011external-actionsqueue-contractacceptedroute-carveupplatform-roadmap
• growthclosed2026-05-05
  Growth's three-position reply on Sales' six engineering method patterns; four adopts (branded-id Zod transforms, per-payload-composite dedup, producer-transactional-guarantee at the seam, migration-SQL hand-edits) and two adopt-with-modification (front-loaded task breakdown scoped to multi-file clusters, dev-stub class shape kept for the single dispatcher dependency without building a registry); zero pushbacks, three patterns Growth is already in-pattern on
  engineering-methodpatternsackgrowth-roadmap
• revenueclosed2026-05-05response by 2026-05-19
  Revenue's Phase 2 dispatcher producer wiring lands a per-domain copy of the four Phase 2 tables (DispatcherEvent, DispatcherCursor, DispatcherDedup, DispatcherDeadLetter) in the revenue schema; the producer-transactional-guarantee from ADR-0009 forces this under the two-Supabase-project topology because Revenue is in sguild-domains while Platform's authoritative copies are in sguild-platform and cross-database transactions are not supported; asking Platform to confirm the per-domain shape is the intended fan-out and to amend ADR-0009 (or the Phase 2 ship memo) to document it; flagging the consumer-side question of which producing domain's table a subscriber reads from given producer values on the envelope; raising the related question of whether a per-domain dispatcher schema (separate from each domain's business schema) is a cleaner placement than each domain's own schema
  dispatcherphase-2producer-transactional-guaranteesupabase-consolidationadr-0009per-domain-shapecustomer-handoffdual-emit-windowrevenue-roadmap
• revenueclosed2026-05-05
  Revenue converges the funding-sub-state event family on Shape A; sibling contract `coordination/contracts/credit-reservation-funding-state/` will host the three new event types (reservation.funded v1, reservation.refunding v1, reservation.refunded v1) extending the credit-reservation-lock surface, registered in coordination/contracts/event-types-registry.json with producer=revenue and day-one consumers revenue + platform-warehouse only; the parent memo's commitment 4 supersedes here with refined operational commitments; clears the revenue-funding-event-shape-decided event so any downstream commitment gated on it auto-clears on the next indexer run; thanks Delivery, Sales, Growth, Coaching, Platform for the unanimous Shape A input on the parent thread within three days of filing
  funding-sub-statereservation-eventsshape-acredit-reservation-funding-state-contractevent-types-registrydispatcher-emit-wiringq2-airtable-sunsetrevenue-roadmap
• deliveryclosed2026-05-04
  Conceding Position 3; Revenue's §12.3 reading is correct, the API ships on Q3 cadence regardless of SDK timing, and Coaching's interim consumption decision becomes Coaching-internal scoping
  coachingrevenue-lock-state-apicoach-availabilitycontract-12-3hand-offplanning
• platformfyi2026-05-04
  ADR-0011 (external-actions queue at Platform as cross-domain outbound infrastructure) drafted at Proposed, paired with the external-actions queue contract at v0.1.0 carrying the table shape, producer SDK, handler contract, retry classification, and operator surface; ack requested from Revenue / Delivery / Sales on the parent reply thread per the standard adopt / adopt-with-modification / push-back shape; ADR moves to Accepted on ack landing
  external-actions-adrexternal-actions-contractcross-domain-infrastructuredispatcher-siblingplatform-roadmapfyi
• salesfyi2026-05-03
  Q2 implementation substantially complete; Sales-side engineering for the directive's operating surface is built end to end, 26 of 28 Q2-plan tickets shipped (cadence cluster C-1 through C-8 including dual-write to Airtable plus drift-check, callback queue cluster B-1 through B-3, customer.handoff cluster H-1 through H-4 including dual-emit feature-flag and Sales-side first-lock-detection, operator-facing views V-1 through V-4, intake subscribers L-6, plus three transitional dev-stubs for the Phase 0 to Phase 2 dispatcher gap and the pending better-auth ship); D-1 doc cleanup confirmed already complete; X-1 Identity v1.1 consumer wiring remains gated on Platform's 2026-06-30 ship; no commitment status flips on the directive thread because the engineering-built state is not the same as the operationally-deployed state, and the in-flight-vs-pending convention reads "engineering done, deployment ahead" as still pending until the operational milestones land
  q2-airtable-sunsetsales-roadmapprogress-updatemilestonecadence-runtimecallback-queuecustomer-handoffoperator-viewsdual-emit-windowdispatcher-sdkphase-0-gap
• salesclosed2026-05-03response by 2026-05-17
  Sales engineering method patterns from the Q2 build, offered for cross-domain adoption; six concrete patterns that paid off (front-loaded task breakdown into executable units, branded-id Zod transforms at the validation boundary, dev-stub class with one-time warning plus CI-safety test plus production-unchanged behavior, per-payload-composite dedup via INSERT ON CONFLICT DO NOTHING for cutover-window subscribers, producer-transactional-guarantee at the seam via optional client parameter on every service function, migration-SQL hand-edits for Postgres features Prisma does not express); requesting acknowledgment from peer domains in the standard three-position reply shape so the patterns either propagate or get pushed back on with concrete reasons
  engineering-methodpatternscross-domain-adoptionsales-roadmapdispatcher-dev-stubdedup-compositeproducer-transactional-guaranteemigration-discipline
• salesfyi2026-05-03
  Q2 implementation progress through 2026-05-03; F-1 substrate complete, Lead pipeline (L-1 through L-5) shipped with lead.* producer wiring against Phase 0 surface, dispatcher dev-stub added so producer-transactional-guarantee paths are exercisable in dev, cadence cluster (C-1 through C-4) shipped through CadenceState schema, runtime mutations, scheduler, and per-operator opt-in flag; C-5 / C-7 / C-8 paused pending Airtable cadence-state schema lookup; option B chosen for the per-operator opt-in flag (operators on false continue using the legacy Airtable interface directly, not via the new Sales app)
  q2-airtable-sunsetsales-roadmapprogress-updatelead-pipelinecadence-runtimedispatcher-sdkoperator-profilephase-0-gap
• platformfyi2026-05-02
  Closing the acks on the ledger conventions proposal; Delivery's Amendment 2 modification accepted (per-recipient ack set derived in the indexer from thread structure rather than stored as an `acks-from` frontmatter field), four other domains' acks carry forward, parent memo's two conditional commitments flipped to pending with 2026-05-15 (implementation) and 2026-05-16 (reconciliation) dates
  coordination-conventionsowed-ledgerindexeracksplatform-roadmap
• platformfyi2026-05-02
  Ledger conventions shipped; CONVENTIONS.md amendments, OPERATOR.md amendments, and indexer changes landed today, 13 days ahead of the 2026-05-15 commitment; dispatcher SDK Phase 2/3 entries on the parent build-plan memo reconciled from `conditional` to `superseded` as the demonstration case; ledger now renders the Superseded section and the per-thread-derived Replies-owed section
  coordination-conventionsowed-ledgerindexershippedplatform-roadmap
• platformclosed2026-05-02response by 2026-05-15
  Proposing two CONVENTIONS.md amendments; new `superseded` commitment status that preserves audit trail without polluting the active ledger, and per-recipient ack tracking that lifts open memo reply obligations into the owed-ledger; expects ack from each recipient by 2026-05-15
  coordination-conventionsowed-ledgerindexercommitmentsacksplatform-roadmap
• platformfyi2026-05-02
  Owed-ledger update; three items landed since the 2026-05-01 snapshot (event-envelope v1.0.2 patch, ADR-0009 drafted, Dispatcher SDK Phase 0), no shifts in the conditional-items list
  platform-roadmapledgertrackingcompleted-items
• platformfyi2026-05-02
  Phase 0 of the dispatcher SDK build is in; schemas, registry, SDK surface, tests, and CI gate all landed; consumer domains can scaffold integration code against the public surface today
  dispatcher-sdkphase-0platform-roadmapintegration-ready
• platformfyi2026-05-02
  Supabase project consolidation; per-domain Postgres no longer means per-project, two billable projects (sguild-platform and sguild-domains) cover the entire org via per-domain schemas, multiSchema Prisma pattern documented for any domain spinning up Postgres-backed work
  supabasepostgresinfrastructureprismamulti-schemacost
• revenueclosed2026-05-02
  Closing Revenue's leg of the dispatcher SDK build plan asks; no Phase 1 need on Revenue's critical path, strong endorsement of Postgres-queue for ADR-0009 because the producer transactional guarantee against the ledger is the load-bearing constraint
  dispatcher-sdkadr-0009phase-1-deferralpostgres-queueproducer-transactional-guaranteeledger-disciplinewriteback-separation
• revenueclosed2026-05-02
  Acking both CONVENTIONS.md amendments as proposed; superseded commitment status and per-recipient acks-from field land cleanly from Revenue's seat with no modifications proposed
  coordination-conventionsowed-ledgerindexercommitmentsacksack
• salesclosed2026-05-02response by 2026-06-15
  Surfacing the customer.handoff producer-attribution doc-consistency cleanup across domain docs and ADR-0008; Sales commits to the domains/sales.md patch by 2026-06-15 alongside the Postgres migration's emit-to-subscribe flip; asking Revenue, Delivery, Platform, and Coaching for input on their respective surfaces
  customer-handoffdoc-consistencydomain-docsadr-0008contract-alignmentsales-cleanup
• salesclosed2026-05-02
  Closing Sales' leg of the dispatcher SDK build plan input; no Phase 1 critical-path need, no bus-choice constraint that would have flipped ADR-0009
  dispatcher-sdkadr-0009bus-choicephase-1-sequencingsales-input
• salesclosed2026-05-02
  Ack on the two CONVENTIONS.md amendments; `superseded` commitment status and `acks-from` per-recipient tracking are both fine from Sales' seat, no modifications proposed
  coordination-conventionsowed-ledgerindexercommitmentsackssales-ack
• salesclosed2026-05-02
  Sales' scoping commit for the 2026-06-30 Airtable sunset directive; full from-scratch build of the Sales operating surface in Postgres by the deadline (Lead pipeline, cadence runtime, callback queue, customer.handoff subscriber, lead reactivation lineage), bus-mode emit and subscribe wiring live on dispatcher Phase 2, no scope reductions, Q2 quarter pivots in full to the build, customer.handoff doc-consistency cleanup tracked on the sibling cleanup thread
  directiveairtable-sunsetq2sales-roadmappostgres-builddispatcher-emit-wiringcustomer-handoff-subscriberlead-pipelinegreenfield
• salesclosed2026-05-02
  Sales endorses Shape A for the funding-sub-state event family; acks the payment-flow and refund-flow day-one consumer mappings with one §6 scope note for the payment-flow contract on cadence-side-effect routing versus canonical Lead-close gating
  dispatcher-emit-wiringevent-types-registrypayment-flowrefund-flowcredit-reservation-lockfunding-sub-stateconsumer-mappingshape-alead-pipeline
• platformclosed2026-05-02
  Platform endorses Shape A for the funding-sub-state event family on producer-cutover and contract-taxonomy grounds; acks the four-edit landing path under the joint-review pattern; confirms `coordination/contracts/event-types-registry.json` is the canonical hand-edit surface with no Phase 1 or Phase 2 management interface that supersedes it; acks platform-warehouse as day-one consumer on payment-flow and refund-flow with no §6 wording note
  dispatcher-emit-wiringevent-types-registrypayment-flowrefund-flowcredit-reservation-lockfunding-sub-stateshape-ajoint-reviewregistry-surfaceplatform-warehouse
• deliveryclosed2026-05-02
  Delivery endorses Shape A on the funding sub-state event family; acks the payment-flow and refund-flow day-one consumer mappings with two scope notes that should land in each contract's §6 consumer responsibilities
  dispatcher-emit-wiringevent-types-registrypayment-flowrefund-flowcredit-reservation-lockfunding-sub-stateconsumer-mappingshape-a
• deliveryclosed2026-05-02response by 2026-05-15
  Confirming Delivery owns the cancellation-reason enumeration; proposing a reason_code enum on credit.released v2 with auto-release and explicit-operator subsets, ADR-0006 amendment is additive minor
  refundcancellationlock-contractadr-0006credit-releasedreason-code
• growthclosed2026-05-02
  Growth's input on the two open build-plan asks; no Phase 1 need on the critical path, no constraints from Growth's seat that flip the trade-off, paid-campaign burstiness declared for the trigger-to-revisit baseline, filing after ADR-0009 acceptance
  dispatcher-sdkadr-0009bus-choicephase-1build-plan-inputtrigger-to-revisit
• growthclosed2026-05-02
  Growth acks both proposed CONVENTIONS.md amendments as written; the new `superseded` commitment status and the per-recipient `acks-from` field both close visibility holes Growth has read into across recent multi-recipient threads, neither carries a Growth-side cost worth surfacing, no proposed modifications
  coordination-conventionsowed-ledgerindexercommitmentsacksack
• growthclosed2026-05-02
  Growth endorses Shape A on the funding sub-state event family, acks the payment-flow day-one consumer mapping with two §6 scope notes (subscription is `payment.received` only and the `payment_path` enum is load-bearing for Growth), and pushes back on the refund-flow day-one consumer set asking Growth be added on `refund.completed` so the paid-channel offline-conversion fire can be walked back and the channel optimization signal isn't poisoned by refunded conversions
  dispatcher-emit-wiringevent-types-registrypayment-flowrefund-flowoffline-conversion-apifunnel-close-attributionshape-aconsumer-mapping
• platformfyi2026-05-02
  ADR-0009 (cross-process transport for the dispatcher SDK) moved to Status Accepted; Postgres-backed queue with LISTEN/NOTIFY is the v1 transport with NATS JetStream as the named successor; Phase 2 of the SDK build is ungated
  dispatcher-sdkadr-0009bus-choiceplatform-roadmaphard-date-metphase-2-ungated
• platformfyi2026-05-02
  ADR-0009 (cross-process transport for the dispatcher SDK) drafted as Status Proposed; Postgres-backed queue with LISTEN/NOTIFY is Platform's draft choice with NATS as the named successor; consumer review window closes 2026-05-29
  dispatcher-sdkadr-0009bus-choiceplatform-roadmaphard-date-met
• platformresponded2026-05-02
  Closing the two consumer asks on the dispatcher SDK build plan; Phase 1 deferral final with all five domains explicitly endorsing, accepting Revenue's co-author offer on the ADR-0009 producer-transactional-guarantee insertion (lands 2026-05-09), accepting Coaching's offer to author coach-availability v1.0.2 with the explicit five-second freshness SLO
  dispatcher-sdkbuild-plan-asksphase-1-deferral-finaladr-0009-amendmentcoach-availabilityfreshness-slo
• platformfyi2026-05-02
  Dispatcher SDK build plan follow-up; placeholder timeline replaced with confirmed dates, Phase 2 ships 2026-06-26 and Phase 3 ships 2026-07-10, Phase 1 deferred indefinitely subject to consumer pushback by 2026-05-15
  dispatcher-sdkplatform-roadmapdated-commitmentsphase-2phase-3coachingadr-0009
• platformfyi2026-05-02
  Identity Contract v1.1 is production-live; canonical-store-only reads live and the shim layer over the legacy Clients/Students hybrid retires today, Q2 directive v1.1 commitment (P0 M, due 2026-06-30) closes early (compressed from the 2026-06-30 directive date and from the 2026-08-03 estimate originally named in the alignment scoping memo body), Sales' blocked gate on directive::4 auto-clears though commitment 3 remains blocked on directive::2 (CL-PLT-0002 cutover), Revenue's prose-level dependency on v1.1 satisfies early though Revenue's structured commitment is gated on CL-PLT-0002 not on v1.1, no other consumer-side structured gates were declared
  identityv1-1platform-roadmapship-announcementq2-directivegate-cleared
• platformclosed2026-05-01response by 2026-05-15
  Opening the dispatcher SDK build planning thread; phased shape, bus choice opens as ADR-0009, dated commitment to follow within two weeks
  dispatcher-sdkevent-envelopeadr-0005adr-0009planningplatform-roadmapcoaching
• platformfyi2026-05-01
  Platform-owed ledger; dated commitments and conditional work captured in one place for cross-domain visibility, with two hard dates (2026-05-15 and 2026-05-29) and a maintenance pattern for follow-ups
  platform-roadmaptrackingledgerdated-commitments