Initiatives
What each team is shipping, tracked by indicators rather than dates. An initiative is done when every indicator reaches its target and holds steady — no calendar commitments. Click Read full memo on any card for the operator-level scope.
Live - fetched 2026-07-13 09:18 UTC-generated 2026-07-13 09:18 UTC
Total
3
In flight
2
Complete
1
Retired
0
In flight
active initiatives; readiness read off the indicator dashboard, not a dateADR-0021 migration initiative scope and execution plan
In flightIn progress
Coordination tools context awarePhase 1 verified complete 2026-05-25: sguild-tools/server.mjs resolves the coordination checkout from SGUILD_COORDINATION_CHECKOUT (commit f16241ce), node --check and module-load clean, non-breaking; per-workspace activation follows as MCP configs adopt the variable in phase 2→coordination_commit, coordination_run_indexer, and coordination_freshness_check in sguild-tools resolve the target checkout from the calling workspace context
Phase 1, ADR-0021 action items 1 and 2: the single-MCP-server tool surface made checkout-aware so it can serve per-domain coordination clones
CI index generation livePhase 1 verified complete 2026-05-25: .github/workflows/ci.yml commits regenerated INDEX.md and _views/ back on default-branch push (commit f16241ce); the workflow run is green after the install-step Prisma-env fix (commit 55bca5d4)→CI regenerates INDEX.md and _views/ on every push to the coordination repo and fails on stale or malformed state
Phase 1, ADR-0021 action item 4 (CI part): CI established as a working writer of the generated artifacts before they are untracked
PER domain coordination clones8 of 8 complete 2026-05-26 under the ADR-0023 satisfaction criterion (per-workspace clone exists on disk, the workspace's spaces.json entry mounts it, and the domain's AGENTS.md references resolve under that mount), with Platform satisfied under the shared-steward shape ADR-0023 names: finance, portfolio, revenue, coaching, growth, sales, delivery (delivery joined 2026-05-26 per 2026-05-26-delivery-adr-0023-agents-md-repoint-complete), plus platform-as-steward closing the 8th slot. Phase 3 is OPEN as of 2026-05-26 per the execution plan; see 2026-05-26-platform-adr-0021-phase-3-open on this thread for the Phase 3 scoping (retire the standalone coordination MCP, retire the *_remove_git_lock tools, sequence the ADR-0023 platform-tools rename, and ship the ADR-0024 prong 2 clone-arg work)→8 of 8 domains on an isolated per-workspace coordination clone with MCP client config pointing at sguild-tools only
Phase 2, ADR-0021 action item 5: each domain workspace holds its own coordination clone, no two agents sharing one .git
Generated artifacts ci ownedPhase 2 Platform slice complete 2026-05-25: INDEX.md and _views/ added to coordination .gitignore and removed from the index with git rm --cached, .github/workflows/ci.yml force-adds and commits them as the sole writer, scripts/auto-commit.mjs no longer runs the indexer with the coordination_auto_commit tool description updated to match, and coordination/AGENTS.md plus platform/AGENTS.md are updated off the standalone coordination MCP; see 2026-05-25-platform-adr-0021-phase-2-platform-slice→INDEX.md and _views/ untracked from domain clones via .gitignore plus git rm --cached, and coordination_auto_commit no longer runs the indexer
Phase 2, ADR-0021 action item 4 (remainder): CI is the sole writer of the generated artifacts once it is confirmed working
Standalone coordination mcp retiredretired 2026-05-26 in commit d68258bf: coordination/mcp/README.md and coordination/mcp/server.mjs deleted (1386 lines removed), and the mcp npm script dropped from coordination/package.json; sguild-tools is now the sole MCP surface for coordination operations per ADR-0021 Decision 1. The precondition ADR-0023 named (.git isolation via per-workspace clones, 8 of 8 on per-domain-coordination-clones) is satisfied. Operators still running an MCP session against the pre-retirement server.mjs must restart for the standalone MCP tools to disappear from their client; the standalone MCP's binary is now gone from the repo so any client config pointing at coordination/mcp/server.mjs will fail to spawn→the standalone coordination MCP is retired and sguild-tools is the sole MCP server for coordination operations
Phase 3, ADR-0021 action item 1 (final part): retired once all domains are on isolated clones and off the standalone MCP
Remove git lock tools retiredretired 2026-05-26 in commit 8d5ffa26: the six per-domain *_remove_git_lock entries from PER_DOMAIN_COMMANDS and coordination_remove_git_lock from DOMAIN_SPECIFIC_COMMANDS are removed from sguild-tools/server.mjs; with per-workspace clones in place (per-domain-coordination-clones indicator at 8 of 8) the cross-process contention class those tools mitigated is gone by construction, and the coordination-clone-scoped tools' inline .git/index.lock clearing in their runner scripts (step 2 of coord-surgical-commit.mjs and peer) covers the remaining single-workspace edge case; the host-side scripts/remove-git-lock.mjs runner stays as the operator recovery utility, invoked directly with `node scripts/remove-git-lock.mjs [<clone>]`. Operators still running an MCP session against the pre-retirement server.mjs must restart for the tools to disappear from the surface→the *_remove_git_lock tools are retired
Phase 3, ADR-0021 action item 3: retired only after the shared checkout is gone, since index contention is real while any shared checkout with concurrent writers exists
Platform data access model initiative scope
In flightNot started
Consumer cutovernot started: growth-warehouse-api reads source-side today; Platform has filed the cutover ask (2026-05-18-platform-growth-mart-consumer-cutover-ask)→known warehouse consumers re-pointed onto their gold section, with growth-warehouse-api migrated to read the gold growth section on a bumped contract version
Migration of warehouse consumers off the flat warehouse onto consumer-scoped gold sections
Source to silver driftnot started: no silver tier to check yet→per-warehouse source-to-silver drift below threshold across all five faces
Ongoing-correctness signal; the warehouse:check-style drift check between bronze and silver per warehouse
In progress
Consumer firewall enforcedlive: lib/mart/auth.ts requireMartAuth enforces MART_API_KEY_<SECTION> bearer auth on every section route using constant-time comparison; each section key is independent so a compromised credential does not expose other sections; health/schema/changelog/corrections use MART_API_KEY_HEALTH→per-section access scoping enforced so each of the 7 consumers reads only its own section
Structural consumer isolation; the API-tagging firewall that keeps a decoupled domain from being biased by data outside its domain
Blocked
Gold mart section coverage7 of 7 sections live: growth, sales, delivery, coaching, revenue (operational); finance, portfolio (cross-domain aggregate; groupings return null:upstream_unavailable until derived store ships); all sections gated on section-scoped MART_API_KEY_<SECTION> bearer auth→7 of 7 gold mart sections live over silver (5 operational sections re-tiered from existing models, finance and portfolio built across silver)
Coverage of the gold application-service-layer mart sections
Done
Silver conform coverage5 of 5 silver faces live as dbt views (warehouse-silver v1.1.0): growth.touchpoint, sales.lead, delivery.lesson+attendance, coaching.coach+lesson_booking, revenue.recognition+credit_ledger+order+credit_reservation; all production-scoped, person_id resolved per domain→5 of 5 silver conforming faces live as dbt views over bronze, each resolving grain to canonical person_id and passing conform checks, stable observation window
Coverage of the silver conforming tier across the five per-domain warehouses (growth, sales, delivery, coaching, revenue)
Identity geography spine livelive: zip_service_area populated (Oahu + Dallas lesson sites), OrgMarket seeded for active (org, market) pairs, PersonTenancy market_id backfill complete, GET /api/org-markets live; spine tables are the join surface for gold section attribution→conformed identity and geography spine live in silver (Person dimension plus the Org to Market to Service Area to Lesson Site hierarchy), every silver face joining to it for the key
The shared conformed reference dimension sourced from Platform's identity database that silver faces join to for person_id and gold sections join to for Person and geography attributes
Complete
every indicator at target for a stable observation windowPlatform initiative scope under the no-rocks no-dates shift
CompleteDone
CL-PLT-0002 cutover coveragecompleted: Revenue confirms migration complete per 2026-05-16-revenue-per-cluster-handoff-consolidated (all ten Revenue module repos on Prisma after 2026-05-15 Airtable cutover; charge-resolution.pg.ts reads client_external_identity_bridges per ADR-0010; card-externals identity reads flipped through Identity v1.1). Platform foundation (89 Persons, 23 PersonTenancies, 23 Square PersonExternal rows, 3 active Guardians) plus Sales, Growth, Delivery, and Revenue all observed downstream→100% of legacy Clients/Students/Client Profiles/Student Profiles migrated to canonical Person + Guardian + Tenancy Junction with shim layer retired, stable observation windowstable 58drefreshed 58d ago
CL-PLT-0002 cutover progress; canonical Person stack populated from legacy backings, downstream consumers (Sales' X-1 reads, Revenue's consumer-side re-points, Growth's lead_intake.person_id resolution path) all flipped to canonical reads
trend:Platform-owned four-table import landed from the operator's 2026-05-07 exports: 32 Client/Student rows resolve to Persons, 23 Client Profile tenancies upserted, 3 active Guardian relationships retained, 9 Student Profiles inventoried; downstream consumer flips and stable observation still open→observation harness added in Platform commit 43b53cc; npm run cl-plt:observe reports Platform foundation complete (93 Persons, 23 PersonTenancies, 3 active Guardians), Sales observed (IDENTITY_DEV_STUB=false, 48 Person-attached Leads), Growth observed (17 intake.captured v2 events, 15 personId-backfilled lead_intake rows), Delivery and Revenue not yet observed in their own schemas; indicator remains in progress→in progress: Platform foundation now includes 89 Persons, 23 PersonTenancies, 23 Square PersonExternal rows, and 3 active Guardians; Sales and Growth are observed, Delivery participant backfill auditability is at target, and Platform supplied Revenue's full Client Profile plus Client External bridge map on 2026-05-14; remaining signal is downstream stable observation after Revenue consumes the bridge map→completed: Revenue confirms migration complete per 2026-05-16-revenue-per-cluster-handoff-consolidated (all ten Revenue module repos on Prisma after 2026-05-15 Airtable cutover; charge-resolution.pg.ts reads client_external_identity_bridges per ADR-0010; card-externals identity reads flipped through Identity v1.1). Platform foundation (89 Persons, 23 PersonTenancies, 23 Square PersonExternal rows, 3 active Guardians) plus Sales, Growth, Delivery, and Revenue all observed downstream
Growth touchpoint dbt model livecompleted: growth.touchpoint relation exists with 136 rows; intake.captured v2 events=16; visitor_id rows=10; confidence direct=16, visitor_id_stitch=1, cross_device_stitch=0, unattributed=119; natural same-visitor stitching observed, cross-device natural test deferred to 2026-05-07-platform-growth-cross-device-stitch-natural-test-deferred→model live in warehouse with v2 traffic flowing and confidence-tagged stitching working (direct, visitor_id_stitch, cross_device_stitch, unattributed)refreshed 67d ago
Warehouse semantic-layer dbt model for growth.touchpoint per 2026-05-01-platform-growth-attribution-stitching-shape; closes Platform's conditional commitment to Growth
trend:worker runbook and smoke check added; npm run growth-intakes:smoke verifies Growth intake.captured v2, Platform intake.matched, and Growth personId backfill agree after a web-form submission→rollback fixture npm run warehouse:test:visitor-stitch proves the live growth.touchpoint model can classify a same-visitor unmatched touchpoint as visitor_id_stitch; initiative remains in progress until naturally observed visitor_id_stitch traffic appears→cross-device stitch rule added using Growth subscriber bridge evidence; rollback fixture npm run warehouse:test:cross-device-stitch proves the live growth.touchpoint model can classify a bridged different-visitor touchpoint as cross_device_stitch; initiative remains in progress until naturally observed visitor_id_stitch and cross_device_stitch traffic appear→completed: natural same-visitor stitch observed in growth.touchpoint (visitor_id_stitch_rows=1) with web-form v2 traffic and Platform intake matcher working; natural cross-device stitch testing deferred to open memo 2026-05-07-platform-growth-cross-device-stitch-natural-test-deferred because subscriber bridge traffic is not currently present
Intake captured v2 schema registeredcompleted: contracts/identity/schema/payloads/intake.captured-v2.json registered in event-types-registry→v2 payload schema entry in event-types-registry, available for Growth's producer to validate againststable 67drefreshed 67d ago
intake.captured v2 schema registry entry per 2026-05-01-platform-growth-subscriber-promotion-confirmed; few hours of Platform work, naturally lands just before Growth's v2 producer flip
Dispatcher sdk phase 3completed: Platform commit bb46b0a adds dispatcher observability hooks, Phase 3 metrics docs, Coaching cutover guide, and Revenue/Coaching reference implementations→docs published, observability hooks live (per-event-type publish-count, per-(consumer, event_type) consume-count, dedup-hit-rate, dead-letter-rate, end-to-end-latency), Coaching cut-over migration guide written, reference implementations for Revenue lock-state-machine emit and Coaching availability-projection subscriberstable 67drefreshed 67d ago
Dispatcher SDK Phase 3 deliverables; Phase 2 transport already live, Phase 3 is the ergonomics layer (docs and observability) plus migration guide
Auth consumer surface readycompleted: AUTH_DEV_STUB flipped off in Sales; auth consumer SDK returning operator-tenant-roles from a real session against the production-facing path→production-ready consumer SDK path that returns operator-tenant-roles from a real session, Sales' AUTH_DEV_STUB flipped off and stablestable 58drefreshed 58d ago
Auth consumer surface readiness check; Sales' initiative has the corresponding AUTH_DEV_STUB-off indicator, this is the Platform-side mirror of the same handshake
trend:completed: AUTH_DEV_STUB=false in Sales and Sales auth bootstrap smoke passed with a real signed-in session→completed: AUTH_DEV_STUB=false in Sales production path and Sales auth bootstrap smoke passed with a real signed-in session; local .env values are not authoritative for this production-facing indicator→in progress: AUTH_DEV_STUB=true in ../sales/.env→completed: AUTH_DEV_STUB flipped off in Sales; auth consumer SDK returning operator-tenant-roles from a real session against the production-facing path
Markets ownership decisionfiled: 2026-05-23-platform-markets-ownership-position→position filed on the Markets-ownership thread; Delivery's Service-Area-routing-chain piece unblockedstable 71drefreshed 58d ago
Markets-ownership decision filed; Delivery's chain piece is unblocked by Platform's position memo.