POWER PACK

Assignment flow

Matching demand to supply — trips to providers/drivers under constraints. Assignment context frame, events, offer/assign commands, the assignment-api service.

44 cards 31 events 8 commands 2 contexts 2 services 1 teams

assignment-header

assignment-frame

assignment-team

assignment-consume-availability-changed-event

assignment-consume-cep-accommodations-updated-event

assignment-consume-credential-expired-event

assignment-consume-driver-verified-event

assignment-consume-provider-suspended-event

assignment-consume-provider-verified-event

assignment-consume-route-optimized-event

assignment-consume-service-provider-activated-event

assignment-consume-service-provider-terminated-event

assignment-consume-trip-priced-event

assignment-consume-vehicle-assigned-to-driver-event

assignment-consume-vehicle-capacity-updated-event

assignment-consume-vehicle-decommissioned-event

assignment-consume-vehicle-registered-event

assignment-emit-assignment-cancelled-event

assignment-emit-assignment-completed-event

assignment-emit-assignment-confirmed-event

assignment-emit-assignment-dispatched-event

assignment-emit-assignment-overridden-event

assignment-emit-assignment-reassigned-event

assignment-emit-assignment-rejected-event

assignment-emit-assignments-swapped-event

assignment-emit-batch-assignment-completed-event

assignment-emit-batch-confirmation-completed-event

assignment-emit-daily-assignment-batch-completed-event

assignment-emit-trip-assigned-event

communications-consume-trip-assigned-event

trip-operations-consume-trip-assigned-event

trip-operations

trip-operations-consume-trip-assigned-to-run-event

trip-operations

trip-operations-consume-trip-unassigned-event

trip-operations

trip-operations-emit-trips-reassigned-event

trip-operations

assignment-assign-trip-command

assignment-batch-assign-trips-command

identity-access-unassign-user-from-dispatch-area-command

identity-access

provider-network-unassign-driver-from-vehicle-command

provider-network

provider-network-unassign-provider-from-dispatch-area-command

provider-network

trip-operations-accept-offer-command

trip-operations

trip-operations-reassign-trips-command

trip-operations

trip-operations-unassign-monitor-from-vr-command

trip-operations

assignment-application

Other power packs

TRF intake & approval

Follow a Transportation Request Form from district submission through Catalyst approval. Events, commands, the intake seam, and the owning context frame.

Passenger Trip lifecycle

The end-to-end journey of one passenger trip: PassengerTripCreated → pickup → board → dropoff. The aggregate + every Pt-prefixed event + the key commands.

Vehicle Run lifecycle

Run-planning → dispatch → on-road execution → completion. VehicleRun aggregate + every Vr-prefixed event + the commands that drive state transitions.

Rescue orchestration

When a live run fails, recovery flows take over. Rescue-Orchestration context + Sgr (Scheduled Generation Run) events + recovery workflows + the owning team.

Safety & incidents

Incident lifecycle — intake, investigation, corrective actions. Context frame + any incident/at-risk event, entity, or command across the architecture.

Migration roadmap

Every strangler-fig seam in one view — which slice of Rhapsody each Catalyst service replaces, and what phase (shadow / canary / planned / live / retired) it's in.

Shared-platform essentials

The load-bearing common substrate: all 6 shared packages plus the 8 most-referenced Infrastructure subsystems (Messaging, Outbox, Workflows, Auth, Telemetry, …).

Catalyst Shared Core — full pack

Every shared-vocabulary stamp + every cross-BC integration event in one paste: 16 base-type stamps (Entity, IDomainEvent, Result, EventEnvelope, …) and 82 wire-format event cards across 13 contexts. Mined from catalyst-shared-core.

Catalyst Shared Core — base types

The 16 vocabulary stamps mined from Catalyst.Shared.{Domain, Application, Contracts}: abstract bases, interfaces, and generics. Drop next to entity / event / command cards to declare the inheritance vocabulary.

Catalyst Shared Core — integration events

All 82 wire-format integration-event DTOs from Catalyst.Shared.Contracts/Events. Distinct from per-BC domain events — these are the cross-context contracts every BC publishes/consumes over Azure Service Bus.

Core integration events · Enrollment & Demand

16 wire-format events from EnrollmentDemand (TRF lifecycle, school year, anti-affinity, students). The richest integration surface in catalyst-shared-core.

Core integration events · Provider Network

21 wire-format events on providers, vehicles, drivers, credentials, time-off, capacity. The largest cross-BC publishing surface.

Core integration events · Settlement

13 wire-format events covering payment lifecycle, reconciliation, disputes, and adjustments.

Catalyst Shared Platform — full pack

All 21 subsystem stamps mined from catalyst-shared-platform/Infrastructure: Messaging, Outbox, Reconciliation, Data, IdMapping, CaseManagement, Telemetry, Logging, Diagnostics, HealthChecks, Authentication, Authorization, Security, Resilience, RateLimiting, Workflows, Behaviors, StranglerFig, FeatureFlags, Startup, Services. Family-banded so the horizontal substrate reads in 8 colour groups.

Platform · Messaging family

Messaging + Outbox + Reconciliation — the wire to ASB and the safety net under DualWrite.

Platform · Persistence family

Data (EF Core) + IdMapping (Rhapsody↔Catalyst) + CaseManagement (shared support cases).

Platform · Observability family

Telemetry + Logging + Diagnostics + HealthChecks — OpenTelemetry, Serilog, Prometheus.

Platform · Identity family

Authentication (JWT/FusionAuth) + Authorization (RBAC + tenant scoping) + Security (PII, audit).

Platform · Resilience family

Resilience (Polly chain) + RateLimiting (per-tenant token buckets).

Platform · Workflow family

Workflows (Orkes Conductor) + Behaviors (cross-cutting MediatR pipeline behaviors).

Platform · Routing family

StranglerFig (legacy↔new request routing) + FeatureFlags (GrowthBook).

Platform · Lifecycle family

Startup (DI composition root, AddCatalyst* extensions) + Services (shared utilities).

BC Kit · Assignment

Auto-generated kit for Assignment from data/bc_anatomy/assignment.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Capacity Planning

Auto-generated kit for Capacity Planning from data/bc_anatomy/capacity-planning.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Communications

Auto-generated kit for Communications from data/bc_anatomy/communications.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Compliance & Eligibility

Auto-generated kit for Compliance & Eligibility from data/bc_anatomy/compliance-eligibility.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Enrollment & Demand Intake

Auto-generated kit for Enrollment & Demand Intake from data/bc_anatomy/enrollment-demand-intake.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Identity & Access

Auto-generated kit for Identity & Access from data/bc_anatomy/identity-access.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Incidents & Safety

Auto-generated kit for Incidents & Safety from data/bc_anatomy/incidents-safety.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Monitoring & Exceptions

Auto-generated kit for Monitoring & Exceptions from data/bc_anatomy/monitoring-exceptions.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Provider Network

Auto-generated kit for Provider Network from data/bc_anatomy/provider-network.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Reporting & Analytics

Auto-generated kit for Reporting & Analytics from data/bc_anatomy/reporting-analytics.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Rescue Orchestration

Auto-generated kit for Rescue Orchestration from data/bc_anatomy/rescue-orchestration.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Routing & Pricing

Auto-generated kit for Routing & Pricing from data/bc_anatomy/routing-pricing.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Settlement

Auto-generated kit for Settlement from data/bc_anatomy/settlement.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

BC Kit · Trip Operations

Auto-generated kit for Trip Operations from data/bc_anatomy/trip-operations.yaml + strangler-fig.csv. db + web-api + workers + ASB connection + external integrations + strangler seams. Drop the lot, arrange, wire with native Miro arrows.

DualWrite · Phase 1 — Core engine

Forward-fill inbox processor + reverse-fill outbox processor + 1-line middleware install. 164 hours of foundation work the rest of the initiative depends on.

DualWrite · Phase 2 — ID mapping

Publisher + subscriber + broker = the ID-mapping loop that lets the engine translate Rhapsody ↔ Catalyst identities. 28 hours, sits between the engine and the BC dataflows.

DualWrite · Phase 3 — BC dataflows

The first concrete per-BC work — TRF deltas in both directions. 48 hours. Template for every other BC that follows.

DualWrite · Phase 4 — Validation

Automated integration tests against docker instances + the QA-led testing-strategy walkthrough & approval. 64 hours — the acceptance gate.

DualWrite · Phase 5 — Rollout

CI/CD updates + design doc + dev docs + pre-prod demo. 56 hours — everything to get it shipped and handed over.

DualWrite · Full roadmap

All 14 SoW deliverables in phase order (engine → ID mapping → BC dataflows → validation → rollout). 360 hours, one view.

DualWrite · TRF enablement combo

The TRF slice of the initiative — engine + ID mapping + TRF-specific dataflows + Enrollment & Demand Intake context frame + the existing TRF intake migration seam. One paste → the whole TRF enablement story lands on the board.

PT/VR · Target architecture

The 8 capability tiles of the Catalyst Trip Operations target: domain defined, state machines, clean architecture, event backbone, versioned API + SignalR, multi-tenancy, observability, quality gates. Mined from the trips-service gap analysis — this is where we're going.

PT/VR · Switchover path

The delivery milestones (S1..S8) interleaved with the cutover gates (G0..G7) that unlock each step, plus the Jeff/Shahab enablement side-rail (N1). One paste → the full sequenced rollout plan with rollback safeties baked in.

PT/VR · Full powerpack

Destination + path + safeties. All 26 tiles: target architecture (A1..A8) followed by switchover milestones + gates + enablement (S/G/N interleaved in dependency order). The whole PT/VR initiative story on one board.

EasyStart · Full matrix

The full EasyStart requirements matrix — banner + frame + legend + every row as 3 atomic cards (title, legacy status, new-Catalyst status). Paste and compose into a board-scale matrix with the tag catalogue.

EasyStart · Titles only

Outline view — one title card per requirement. No status cards. For a scannable list of what's in scope.

Matrix · Tag catalogue

Every reusable tag: 14 BC tags, 10 capability tags, 5 surface tags. Drop the ones you need next to requirement cards; tags stay consistent across initiatives.

EasyStart · Milestone 1 only

EasyStart requirements tagged to Milestone 1 (Foundation). The MVP floor — what ships first.

EasyStart · Milestone 3 only

EasyStart requirements tagged to Milestone 3 (Visibility & Control). Parent-facing flows, routing review, cross-initiative notifications.

TripHQ · Full matrix

The full TripHQ requirements matrix — banner + frame + legend + every row as 3 atomic cards (title, legacy status, new-Catalyst status). Paste and compose into a board-scale matrix with the tag catalogue.

TripHQ · Titles only

Outline view — one title card per requirement. No status cards. For a scannable list of what's in scope.

TripHQ · Milestone 1 only

TripHQ requirements tagged to Milestone 1 (the Phase 2 / Baufest MVP push).

TripHQ · Milestone 2 only

TripHQ requirements tagged to Milestone 2 (deferred items: breadcrumbs, late-status, impersonation indicator).

Chronicle · Full matrix

Full Chronicle requirements matrix — banner + frame + legend + every row as 3 atomic cards. Chronicle is the post-trip historical insights & reporting layer.

Chronicle · Titles only

Outline view — one title card per requirement.

Chronicle · Milestone 1 only

Chronicle MUST-priority foundation requirements (M1).

Chronicle · Milestone 2 only

Chronicle M2 — SHOULD/COULD deferrals + EverWatch-gated historical capture.

DrivePath · Full matrix

Full DrivePath requirements matrix — banner + frame + legend + every row as 3 atomic cards. DrivePath delivers Compliance 2.0, replacing CC for driver compliance.

DrivePath · Titles only

Outline view — one title card per requirement.

DrivePath · Milestone 1 only

DrivePath M1 — Compliance 2.0 / CC replacement scope.

DrivePath · Milestone 2 only

DrivePath M2 — DrivePath MMP (Catalyst real-time API, ID badge, vehicle/equipment, schedule, OCR, LMS, CheckR).

EverPulse · Full matrix

Full EverPulse requirements matrix — banner + frame + legend + every row as 3 atomic cards. EverPulse is the unified notifications & comms platform (orchestration, preferences, consent, opt-out, quiet hours, suppression).

EverPulse · Titles only

Outline view — one title card per requirement.

EverPulse · Milestone 1 only

EverPulse M1 — orchestration core.

EverPulse · Milestone 2 only

EverPulse M2 — preferences + consent.

EverPulse · Milestone 3 only

EverPulse M3 — opt-out, quiet hours, frequency caps.

EverPulse · Milestone 4 only

EverPulse M4 — templates, i18n, audit, engagement.

EverPulse · Milestone 5 only

EverPulse M5 — broadcast, branding, retention, admin/ops.

EverWatch · Full matrix

Full EverWatch requirements matrix — banner + frame + legend + every row as 3 atomic cards. EverWatch is the live monitoring & exception-ops backbone (breadcrumbs, GPS feeds, deviation alerts, Rhapsody retirement).

EverWatch · Titles only

Outline view — one title card per requirement.

EverWatch · Milestone 1 only

EverWatch M1 (Phase 1) — live tracking foundations.

EverWatch · Milestone 2 only

EverWatch M2 (Phase 2) — historical capture + alerts.

EverWatch · Milestone 3 only

EverWatch M3 (Phase 3) — driver navigation + ops console.

EverWatch · Milestone 4 only

EverWatch M4 (Phase 4) — Rhapsody retirement.

FlexFare · Full matrix

Full FlexFare requirements matrix — banner + frame + legend + every row as 3 atomic cards. FlexFare is the pricing & rate-card engine (Rhapsody parity, rate-card lifecycle, NetSuite billing, dynamic pricing & quoting).

FlexFare · Titles only

Outline view — one title card per requirement.

FlexFare · Milestone 1 only

FlexFare M1 (Phase I) — Rhapsody parity + audit foundation.

FlexFare · Milestone 2 only

FlexFare M2 (Phase II) — dynamic pricing, quoting, SP-flex, direct-to-driver.

ParentLink · Full matrix

Full ParentLink requirements matrix — banner + frame + legend + every row as 3 atomic cards. ParentLink is the parent-facing mobile/PWA (driver badge, alerts, trip detail, cancel/hold, teacher mode, no-show insights).

ParentLink · Titles only

Outline view — one title card per requirement.

ParentLink · Milestone 1 only

ParentLink M1 — MVP scope (driver badge, alerts, trip detail).

ParentLink · Milestone 2 only

ParentLink M2 — SHOULDs + Catalyst-dependent FRs + no-show pipeline + 13+ student gate.

Pathfinder · Full matrix

Full Pathfinder requirements matrix — banner + frame + legend + every row as 3 atomic cards. Pathfinder is the routing optimisation engine (overrides, recommendations, configurator, bulk re-routing, parity certification).

Pathfinder · Titles only

Outline view — one title card per requirement.

Pathfinder · Milestone 1 only

Pathfinder M1 — MUST-priority foundation.

Pathfinder · Milestone 2 only

Pathfinder M2 — SHOULD/COULD deferrals.

Valkyrie · Full matrix

Full Valkyrie requirements matrix — banner + frame + legend + every row as 3 atomic cards. Valkyrie is the rescue orchestration / SMT live-trip recovery system (recommendation, offers, MDD assign, escalation).

Valkyrie · Titles only

Outline view — one title card per requirement.

Valkyrie · Milestone 1 only

Valkyrie M1 — recommendation engine, dashboard, agent push, advanced matching.

Valkyrie · Milestone 2 only

Valkyrie M2 — PROD-578/572/580 (auto-broadcast, EverPulse alerts).

Valkyrie · Milestone 3 only

Valkyrie M3 — PROD-579/577/632 (SP workflows, prevention).

Gap view · all MUSTs not yet full on new Catalyst

Cross-initiative gap view. Every MUST requirement where the new-Catalyst support posture is anything other than 'full'. The residual scope across the portfolio.

BC load · Enrollment & Demand Intake

Every requirement across initiatives that lands in the Enrollment & Demand Intake bounded context. The team's cross-portfolio workload in one view.

BC load · Identity & Access

Every requirement across initiatives that lands in the Identity & Access bounded context — RBAC, tenant isolation, auth flows.

BC load · Communications

Every requirement across initiatives that lands in the Communications bounded context — parent notifications, EverPulse, multi-channel outreach.

Capability coverage · state machines

Every requirement whose new-Catalyst story turns on domain state-machine enforcement (Blueprint Ch 10). Surfaces where Catalyst's illegal-transition-throws discipline pays off.

Capability coverage · event emission

Every requirement satisfied via domain-event emission on the transactional outbox (Blueprint Ch 08). The event-driven story told requirement by requirement.

Capability coverage · RBAC + multi-tenant

Every requirement on authorisation, district-scoped data isolation, and tenant separation (Blueprint Ch 03 multi-tenancy principle). The compliance surface.

BC load · Trip Operations

Every requirement across initiatives that lands in the Trip Operations BC — passenger-trip lifecycle, dispatch, live monitoring, post-trip closure.

BC load · Routing & Pricing

Every requirement across initiatives in the Routing & Pricing BC — rate cards, parity, route optimisation, dynamic pricing, billing handoff.

BC load · Assignment

Every requirement across initiatives in the Assignment BC — driver/vehicle pairing, run construction, manual overrides, swap mechanics.

BC load · Rescue Orchestration

Every requirement across initiatives in the Rescue Orchestration BC — SMT live-trip recovery, broadcast, MDD reassign, escalation, prevention.

BC load · Provider Network

Every requirement across initiatives in the Provider Network BC — SP portal, contracting, performance, settlement-side feedback.

BC load · Capacity Planning

Every requirement across initiatives in the Capacity Planning BC — forward demand modelling, route capacity, fleet sizing, bulk re-routing.

BC load · Compliance & Eligibility

Every requirement across initiatives in the Compliance & Eligibility BC — driver/vehicle compliance, expirations, DrivePath domain, eligibility gating.

BC load · Incidents & Safety

Every requirement across initiatives in the Incidents & Safety BC — safety incidents, escalation, rescue triggers, post-mortems, regulator-facing flows.

BC load · Settlement

Every requirement across initiatives in the Settlement BC — invoicing, NetSuite handoff, billing adjustments, service-provider compensation, financial workflows.

BC load · Monitoring & Exceptions

Every requirement across initiatives in the Monitoring & Exceptions BC — live-tracking exceptions, deviation alerts, audit/operations queues, breadcrumb pipelines.

BC load · Reporting & Analytics

Every requirement across initiatives in the Reporting & Analytics BC — post-trip historical insights, dashboards, BI feeds, churn / on-time / utilisation metrics.

Capability coverage · CQRS · read side

Every requirement satisfied by a CQRS read model — dashboards, projections, lookup queries (Blueprint Ch 09 CQRS).

Capability coverage · CQRS · write side

Every requirement that mutates state via aggregate-rooted command handlers (Blueprint Ch 04 design patterns + Ch 05 domain).

Capability coverage · event consumption

Every requirement that reacts to a domain event — projections, downstream side-effects, BC-to-BC reactions (Blueprint Ch 08 events).

Capability coverage · saga / orchestration

Every requirement that needs a multi-step orchestration across BCs — compensations, long-running flows (Blueprint Ch 09 orchestration).

Capability coverage · transactional outbox

Every requirement that depends on the transactional outbox for reliable cross-BC publication (Blueprint Ch 08 events + Ch 11 safety invariants).

Capability coverage · multi-tenancy

Every requirement that depends on tenant-isolation primitives — district scoping, cross-tenant guards (Blueprint Ch 03 principles).

Capability coverage · observability

Every requirement on audit logs, metrics, traces, alerts, and ops dashboards (Blueprint Ch 12 operating clarity).

Pillar coverage · Ch 01 Executive Summary

Every requirement whose support note cites Blueprint Ch 1 (Executive Summary).

Pillar coverage · Ch 02 Why DDD

Every requirement whose support note cites Blueprint Ch 2 (Why DDD).

Pillar coverage · Ch 03 Principles

Every requirement whose support note cites Blueprint Ch 3 (Architectural principles — multi-tenancy, idempotence, explicit failure).

Pillar coverage · Ch 04 Design Patterns

Every requirement whose support note cites Blueprint Ch 4 (Design patterns — CQRS, sagas, outbox).

Pillar coverage · Ch 05 Domain Model

Every requirement whose support note cites Blueprint Ch 5 (Domain model — aggregates, entities, value objects).

Pillar coverage · Ch 06 Contracts

Every requirement whose support note cites Blueprint Ch 6 (Cross-BC contracts and integration events).

Pillar coverage · Ch 07 System Landscape

Every requirement whose support note cites Blueprint Ch 7 (System landscape — BC map, integrations, data flow).

Pillar coverage · Ch 08 Events

Every requirement whose support note cites Blueprint Ch 8 (Event-driven model — emit, consume, outbox).

Pillar coverage · Ch 09 Orchestration

Every requirement whose support note cites Blueprint Ch 9 (Orchestration — sagas, CQRS, multi-step workflows).

Pillar coverage · Ch 10 Lifecycle

Every requirement whose support note cites Blueprint Ch 10 (Lifecycle — state machines, illegal-transition discipline).

Pillar coverage · Ch 11 Safety

Every requirement whose support note cites Blueprint Ch 11 (Safety — invariants, compensations, audit trails).

Pillar coverage · Ch 12 Operating Clarity

Every requirement whose support note cites Blueprint Ch 12 (Operating clarity — observability, ops dashboards).

Pillar coverage · Ch 13 Framework

Every requirement whose support note cites Blueprint Ch 13 (Framework guarantees and platform contracts).

EasyStart · Readiness (DOR + DOD)

What must be in place before EasyStart development starts, and what the initiative delivers. Prerequisites + core + outputs.

TripHQ · Readiness (DOR + DOD)

What must be in place before TripHQ development starts, and what the initiative delivers. Prerequisites + core + outputs.

Valkyrie · Readiness (DOR + DOD)

What must be in place before Valkyrie development starts, and what the initiative delivers. Prerequisites + core + outputs.

Chronicle · Readiness (DOR + DOD)

What must be in place before Chronicle development starts, and what the initiative delivers. Prerequisites + core + outputs.

DrivePath · Readiness (DOR + DOD)

What must be in place before DrivePath development starts, and what the initiative delivers. Prerequisites + core + outputs.

EverPulse · Readiness (DOR + DOD)

What must be in place before EverPulse development starts, and what the initiative delivers. Prerequisites + core + outputs.

EverWatch · Readiness (DOR + DOD)

What must be in place before EverWatch development starts, and what the initiative delivers. Prerequisites + core + outputs.

FlexFare · Readiness (DOR + DOD)

What must be in place before FlexFare development starts, and what the initiative delivers. Prerequisites + core + outputs.

ParentLink · Readiness (DOR + DOD)

What must be in place before ParentLink development starts, and what the initiative delivers. Prerequisites + core + outputs.

Pathfinder · Readiness (DOR + DOD)

What must be in place before Pathfinder development starts, and what the initiative delivers. Prerequisites + core + outputs.

Catalyst Architect Pack — all components

The full building-block library. 35 atomic architecture cards across 7 categories — domain primitives, persistence, API surfaces, events, workflow, security, ops. Compose any architecture by picking the ingredients.

Architect · Domain primitives

DDD building blocks — aggregate, entity, value object, domain event, command, query, policy. The 7 cards every Catalyst workshop reaches for first.

Architect · Persistence

Data-layer components — Postgres (DB-per-BC), read model / projection, migration runner, cache, blob storage.

Architect · API surfaces

API + real-time components — HTTP web API, API gateway (Traefik), SignalR, API versioning, OpenAPI contract.

Architect · Events

Event-driven components — Azure Service Bus, transactional outbox, event consumer, dead-letter queue, subscription.

Architect · Workflow

Saga + orchestration components — Orkes Conductor, task workers, compensation steps.

Architect · Security

Identity, authorisation, tenancy, secrets, and audit trail — the 5 cards that show up in every compliance conversation.

Architect · Ops

Observability, CI/CD, feature flags, health checks, rate limiter — the operational substrate every service runs on.

Catalyst Architect Pack — square grid

All 35 components as 240×240 squares. For ingredient-list layouts and compact tile walls where wide rows don't fit.

Architect · Domain (square)

7 DDD primitives as 240×240 squares.

Architect · Persistence (square)

5 persistence components as 240×240 squares.

Architect · API (square)

5 API components as 240×240 squares.

Architect · Events (square)

5 event components as 240×240 squares.

Architect · Workflow (square)

3 workflow components as 240×240 squares.

Architect · Security (square)

5 security components as 240×240 squares.

Architect · Ops (square)

5 ops components as 240×240 squares.

EasyStart · Matrix (square)

EasyStart requirements as 280×280 title cards + 240×240 status cards. Compose into a tile-wall grid instead of landscape rows.

Requires · Full vocabulary

Every Requires card — 10 type-level (API, Frontend, DB, Communication, Event, RBAC, Workflow, Integration, Audit, Observability) + 14 BC-level with scope. The ingredients list you compose features from.

Requires · Type-level

10 abstract dependency kinds — API / Frontend / DB / Comm / Event / RBAC / Workflow / Integration / Audit / Observability.

Requires · BC-level

14 bounded-context Requires cards. Scope described on each; drop beside a feature to declare which BC owns it.

EasyStart · FULL architectural pack

Everything. Hero + personas + journeys + milestones + services + entities + integrations + matrix (frame + legend + header + 14 req trios) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for drawing EasyStart on Miro.

EasyStart · Initiative lore

The 36 EasyStart-specific cards — hero + personas + journeys + milestones + entities + integrations + target services. No matrix, no components.

EasyStart · Personas

6 stakeholder cards — coordinator, parent, routing ops, field ops, school admin, cutover owner.

EasyStart · Journeys

J1 School Management · J2 Student Onboarding · J3 Trip Request · J4 Updates & Cancellations.

EasyStart · Milestones

M1 Foundation · M2 Data Quality · M3 Visibility & Control · M4 Scale & Special Care.

EasyStart · Data entities

12 domain entities — District, School, PickupZone, BellSchedule, StudentProfile, Household, Contact, Equipment, TripRequest, Verification, BulkImport, AuditEntry.

EasyStart · External integrations

6 external systems — TripHQ, Rhapsody, Catalyst, EverPulse, VIP app, Address validator.

EasyStart · Target backend services

The 3 new microservices — School, Student, Trip Request.

District Portal · Icon Pack (builder)

26 movable Lucide-icon tiles for the MRM District Portal replacement — personas, functional areas, trip-status states, special-needs flags, cross-cutting tech. Section-stacked palette layout; each tile is its own draggable item.

TripHQ · FULL architectural pack

Everything for TripHQ. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for TripHQ on Miro.

TripHQ · Initiative lore

All TripHQ-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

TripHQ · Personas

Stakeholder cards.

TripHQ · Journeys

User-journey cards (J1/J2/…).

TripHQ · Milestones

Delivery-milestone cards (M1/M2/…).

TripHQ · Data entities

Domain-entity cards.

TripHQ · External integrations

External-system cards.

TripHQ · Target backend services

New-service cards.

EverWatch · FULL architectural pack

Everything for EverWatch. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for EverWatch on Miro.

EverWatch · Initiative lore

All EverWatch-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

EverWatch · Personas

Stakeholder cards.

EverWatch · Journeys

User-journey cards (J1/J2/…).

EverWatch · Milestones

Delivery-milestone cards (M1/M2/…).

EverWatch · Data entities

Domain-entity cards.

EverWatch · External integrations

External-system cards.

EverWatch · Target backend services

New-service cards.

Chronicle · FULL architectural pack

Everything for Chronicle. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for Chronicle on Miro.

Chronicle · Initiative lore

All Chronicle-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

Chronicle · Personas

Stakeholder cards.

Chronicle · Journeys

User-journey cards (J1/J2/…).

Chronicle · Milestones

Delivery-milestone cards (M1/M2/…).

Chronicle · Data entities

Domain-entity cards.

Chronicle · External integrations

External-system cards.

Chronicle · Target backend services

New-service cards.

Valkyrie · FULL architectural pack

Everything for Valkyrie. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for Valkyrie on Miro.

Valkyrie · Initiative lore

All Valkyrie-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

Valkyrie · Personas

Stakeholder cards.

Valkyrie · Journeys

User-journey cards (J1/J2/…).

Valkyrie · Milestones

Delivery-milestone cards (M1/M2/…).

Valkyrie · Data entities

Domain-entity cards.

Valkyrie · External integrations

External-system cards.

Valkyrie · Target backend services

New-service cards.

EverPulse · FULL architectural pack

Everything for EverPulse. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for EverPulse on Miro.

EverPulse · Initiative lore

All EverPulse-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

EverPulse · Personas

Stakeholder cards.

EverPulse · Journeys

User-journey cards (J1/J2/…).

EverPulse · Milestones

Delivery-milestone cards (M1/M2/…).

EverPulse · Data entities

Domain-entity cards.

EverPulse · External integrations

External-system cards.

EverPulse · Target backend services

New-service cards.

ParentLink · FULL architectural pack

Everything for ParentLink. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for ParentLink on Miro.

ParentLink · Initiative lore

All ParentLink-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

ParentLink · Personas

Stakeholder cards.

ParentLink · Journeys

User-journey cards (J1/J2/…).

ParentLink · Milestones

Delivery-milestone cards (M1/M2/…).

ParentLink · Data entities

Domain-entity cards.

ParentLink · External integrations

External-system cards.

ParentLink · Target backend services

New-service cards.

FlexFare · FULL architectural pack

Everything for FlexFare. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for FlexFare on Miro.

FlexFare · Initiative lore

All FlexFare-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

FlexFare · Personas

Stakeholder cards.

FlexFare · Journeys

User-journey cards (J1/J2/…).

FlexFare · Milestones

Delivery-milestone cards (M1/M2/…).

FlexFare · Data entities

Domain-entity cards.

FlexFare · External integrations

External-system cards.

FlexFare · Target backend services

New-service cards.

Pathfinder · FULL architectural pack

Everything for Pathfinder. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for Pathfinder on Miro.

Pathfinder · Initiative lore

All Pathfinder-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

Pathfinder · Personas

Stakeholder cards.

Pathfinder · Journeys

User-journey cards (J1/J2/…).

Pathfinder · Milestones

Delivery-milestone cards (M1/M2/…).

Pathfinder · Data entities

Domain-entity cards.

Pathfinder · External integrations

External-system cards.

Pathfinder · Target backend services

New-service cards.

DrivePath · FULL architectural pack

Everything for DrivePath. Hero + personas + journeys + milestones + services + entities + integrations + matrix (if seeded) + tag catalogue + Requires vocabulary + the 35-card Catalyst Architect Pack. One paste = the complete composition kit for DrivePath on Miro.

DrivePath · Initiative lore

All DrivePath-specific cards: hero + personas + journeys + milestones + entities + integrations + services.

DrivePath · Personas

Stakeholder cards.

DrivePath · Journeys

User-journey cards (J1/J2/…).

DrivePath · Milestones

Delivery-milestone cards (M1/M2/…).

DrivePath · Data entities

Domain-entity cards.

DrivePath · External integrations

External-system cards.

DrivePath · Target backend services

New-service cards.

EasyStart · UI pack (full)

Every UI card for EasyStart — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

EasyStart · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

EasyStart · Surfaces

Navigable user experiences (route × shell × mode).

EasyStart · Panels

Sections within a surface (filter / main / metrics / detail / …).

EasyStart · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

EasyStart · Actions

Terminal business outcomes — named user-initiated mutations.

EasyStart · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

EasyStart · Complete (domain + UI)

Everything for EasyStart — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

TripHQ · UI pack (full)

Every UI card for TripHQ — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

TripHQ · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

TripHQ · Surfaces

Navigable user experiences (route × shell × mode).

TripHQ · Panels

Sections within a surface (filter / main / metrics / detail / …).

TripHQ · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

TripHQ · Actions

Terminal business outcomes — named user-initiated mutations.

TripHQ · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

TripHQ · Complete (domain + UI)

Everything for TripHQ — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

EverWatch · UI pack (full)

Every UI card for EverWatch — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

EverWatch · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

EverWatch · Surfaces

Navigable user experiences (route × shell × mode).

EverWatch · Panels

Sections within a surface (filter / main / metrics / detail / …).

EverWatch · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

EverWatch · Actions

Terminal business outcomes — named user-initiated mutations.

EverWatch · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

EverWatch · Complete (domain + UI)

Everything for EverWatch — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

Chronicle · UI pack (full)

Every UI card for Chronicle — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

Chronicle · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

Chronicle · Surfaces

Navigable user experiences (route × shell × mode).

Chronicle · Panels

Sections within a surface (filter / main / metrics / detail / …).

Chronicle · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

Chronicle · Actions

Terminal business outcomes — named user-initiated mutations.

Chronicle · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

Chronicle · Complete (domain + UI)

Everything for Chronicle — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

Valkyrie · UI pack (full)

Every UI card for Valkyrie — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

Valkyrie · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

Valkyrie · Surfaces

Navigable user experiences (route × shell × mode).

Valkyrie · Panels

Sections within a surface (filter / main / metrics / detail / …).

Valkyrie · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

Valkyrie · Actions

Terminal business outcomes — named user-initiated mutations.

Valkyrie · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

Valkyrie · Complete (domain + UI)

Everything for Valkyrie — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

EverPulse · UI pack (full)

Every UI card for EverPulse — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

EverPulse · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

EverPulse · Surfaces

Navigable user experiences (route × shell × mode).

EverPulse · Panels

Sections within a surface (filter / main / metrics / detail / …).

EverPulse · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

EverPulse · Actions

Terminal business outcomes — named user-initiated mutations.

EverPulse · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

EverPulse · Complete (domain + UI)

Everything for EverPulse — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

ParentLink · UI pack (full)

Every UI card for ParentLink — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

ParentLink · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

ParentLink · Surfaces

Navigable user experiences (route × shell × mode).

ParentLink · Panels

Sections within a surface (filter / main / metrics / detail / …).

ParentLink · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

ParentLink · Actions

Terminal business outcomes — named user-initiated mutations.

ParentLink · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

ParentLink · Complete (domain + UI)

Everything for ParentLink — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

FlexFare · UI pack (full)

Every UI card for FlexFare — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

FlexFare · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

FlexFare · Surfaces

Navigable user experiences (route × shell × mode).

FlexFare · Panels

Sections within a surface (filter / main / metrics / detail / …).

FlexFare · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

FlexFare · Actions

Terminal business outcomes — named user-initiated mutations.

FlexFare · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

FlexFare · Complete (domain + UI)

Everything for FlexFare — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

Pathfinder · UI pack (full)

Every UI card for Pathfinder — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

Pathfinder · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

Pathfinder · Surfaces

Navigable user experiences (route × shell × mode).

Pathfinder · Panels

Sections within a surface (filter / main / metrics / detail / …).

Pathfinder · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

Pathfinder · Actions

Terminal business outcomes — named user-initiated mutations.

Pathfinder · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

Pathfinder · Complete (domain + UI)

Everything for Pathfinder — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.

DrivePath · UI pack (full)

Every UI card for DrivePath — portals, surfaces, panels, flows, actions. Composed top-down so a board paste lands the strata in the order they appear in the product.

DrivePath · Portals

Role-scoped shells (e.g. dispatch, compliance, finance).

DrivePath · Surfaces

Navigable user experiences (route × shell × mode).

DrivePath · Panels

Sections within a surface (filter / main / metrics / detail / …).

DrivePath · Flows

Dialog/drawer/modal shells — multi-step UI workflows.

DrivePath · Actions

Terminal business outcomes — named user-initiated mutations.

DrivePath · User-story kit

Portals + surfaces + flows + actions (no panels). The minimal set to compose a user story: persona → portal → surface → flow → action → entity.

DrivePath · Complete (domain + UI)

Everything for DrivePath — initiative-lore full-pack unioned with the UI pack. One paste lays the entire product on the board: hero, personas, journeys, milestones, services, entities, integrations, matrix, requires, architect pack, and the UI strata on top.