Advanced2 hr 10 min8 implementation labs5 hostile paths

Build Durable multi-stop itinerary

An eight-lab, source-bounded workshop for the complete trip itinerary lifecycle: exact commands and events, durable records, replay, concurrency, unknown outcomes, hostile fixtures, a maintained capstone, and production exit evidence.

Durable boundarytrip itinerary · 6 states · 9 transitions · 9 event identities

Freeze the evidence boundary first

This curriculum teaches the durable host workflow around reviewed Mappls surfaces. It does not manufacture provider endpoints, callbacks, resource states, entitlement, or completion evidence.

The journey blueprint and application event contracts are implementation guidance, not Mappls provider payload specifications.Only linked normalized contracts and source guides may define provider request syntax; empty evidence is never backfilled.The simulator and maintained capstone operate in explicit fixture mode and make no entitlement claim.Credentials, precise production payloads, opaque native objects, and provider secrets stay outside workshop inputs and durable examples.
Lab 1 · 15 min

Model the lifecycle before the UI

Turn the trip itinerary blueprint into an explicit aggregate boundary owned by the application.

Build

draft: An ordered, bounded set of provider-backed places represents current trip intent without claiming a valid route.planned: A route revision is bound to the exact ordered stop identities, travel profile, provider response, and planning time.active: The traveller started the current route revision and each next stop receives an explicit visited or skipped outcome.paused: An attributable interruption stops progress without discarding saved stops, outcomes, or route identity.completed: Every stop is visited or explicitly skipped and the terminal itinerary, route revision, outcomes, and event history are retained.cancelled: A named actor ended the itinerary with a reason while retaining all committed place, route, and progress evidence.

Prove before continuing

Every persisted state exists in the reviewed blueprint.Terminal states reject ordinary forward commands.Recovery text is operational guidance, not another hidden state.
Lab 2 · 20 min

Implement every command and event pair

Make intent, actor authority, allowed source state, committed state, and emitted fact reviewable together.

Build

create_trip by Traveller: new aggregate → draft; emit trip.created.add_or_reorder_stop by Traveller: draft | planned → draft; emit trip.sequence_changed.preview_route by Mappls routing service: draft → planned; emit trip.route_previewed.start_trip by Traveller: planned → active; emit trip.started.pause_trip by Traveller: active → paused; emit trip.paused.resume_trip by Traveller: paused → active; emit trip.resumed.visit_or_skip_next by Traveller: active → active; emit trip.stop_completed.complete_trip by Traveller: active → completed; emit trip.completed.cancel_trip by Traveller: draft | planned | active | paused → cancelled; emit trip.cancelled.

Prove before continuing

create_trip resolves to durable-weekend-itinerary-trip-created without claiming a provider webhook payload.add_or_reorder_stop resolves to durable-weekend-itinerary-trip-sequence-changed without claiming a provider webhook payload.preview_route resolves to durable-weekend-itinerary-trip-route-previewed without claiming a provider webhook payload.start_trip resolves to durable-weekend-itinerary-trip-started without claiming a provider webhook payload.pause_trip resolves to durable-weekend-itinerary-trip-paused without claiming a provider webhook payload.resume_trip resolves to durable-weekend-itinerary-trip-resumed without claiming a provider webhook payload.visit_or_skip_next resolves to durable-weekend-itinerary-trip-stop-completed without claiming a provider webhook payload.complete_trip resolves to durable-weekend-itinerary-trip-completed without claiming a provider webhook payload.cancel_trip resolves to durable-weekend-itinerary-trip-cancelled without claiming a provider webhook payload.
Lab 3 · 15 min

Persist restart-safe records

Separate business identity, provider evidence, command receipts, immutable facts, audit, and downstream delivery.

Build

Trip aggregate: Business identity, date, party, lifecycle, current route revision, and optimistic version. Keys: tripId, state, version, date, partySize, routeRevision.Itinerary stop: Ordered provider-backed place and progress outcome. Keys: mapplsPin, position, providerProvenance, status, completedAt, skipReason.Route revision: Immutable preview for one exact intent version. Keys: routeId, revision, orderedPins, profile, legs, distance, duration, plannedAt.Audit and outbox: Attributable changes and reliable downstream collaboration or notification. Keys: eventId, aggregateVersion, actor, commandId, outboxStatus.

Prove before continuing

Process restart restores the same aggregate version and command result.Opaque SDK or native UI objects are not durable records.Provider evidence and application decisions remain distinguishable.
Lab 4 · 15 min

Make concurrency and replay deterministic

Apply optimistic expected versions and aggregate-scoped idempotency before executing effects.

Build

Every saved stop originated from provider-backed discovery and retains its Mappls Pin and provenance.A Mappls Pin occurs at most once in an itinerary.A route revision is valid only for the exact ordered stop list and constraints that produced it.Only the next pending stop may receive a visit or skip outcome.Completion is impossible while any stop remains pending.Commands are idempotent and compare the expected trip version.

Prove before continuing

An exact replay returns the first result without another event or version.A reused key with different intent conflicts.A stale expected version changes no durable truth.
Lab 5 · 15 min

Control effects and unknown outcomes

Commit outbox intent atomically, execute effects outside the transaction, and reconcile ambiguous results.

Build

A collaborator edits after route preview: detect with Current stop identities or aggregate version differ from the route's intent version. Recover with Invalidate the route, show the edit, and require a new preview before start.Routing succeeds but response is lost: detect with The same ordered intent and request identity has no committed route revision. Recover with Reconcile or repeat the same idempotent request; never attach a response to newer intent.A venue becomes unavailable during the trip: detect with Traveller or fresh provider/business data marks the next stop unavailable. Recover with Record an explicit skip with reason, then offer a newly versioned replan from current context.Application restarts mid-trip: detect with A durable active aggregate exists without current client state. Recover with Restore visit/skip progress and current revision, refresh stale operational data, and ask before resuming guidance.

Prove before continuing

A timeout remains an unknown outcome until identity-based reconciliation completes.Retries are bounded and preserve the original business and command identities.Dead-letter or manual review retains the entire attempt history.
Lab 6 · 15 min

Run all hostile fixture scenarios

Exercise the success path plus replay, concurrency, state, and response-loss failures without an account.

Build

Complete journey: Commit the shortest reviewed success path to the journey-specific operating target.Idempotent replay: Repeat one command identity and prove that version, event identity, and side effects do not duplicate.Stale version: Reject a command based on an outdated aggregate version without changing durable truth.Invalid transition: Reject a known command when the current state does not permit it.Unknown outcome recovery: Reconcile after a lost response, then replay the original command identity safely.

Prove before continuing

All fixture checks pass for all five scenarios.Rejected commands emit no event and do not increment version.The fixture makes zero provider calls and exposes no write tool.
Lab 7 · 20 min

Trace the Weekend Trip Planner capstone

Follow the maintained source through domain rules, adapter seam, repository transaction, HTTP boundary, UI evidence, and restart test.

Build

Run the app's declared test suite (8 tests).Run fixture mode without a credential.Inspect audit and outbox evidence after each transition.Restart the process and continue the same aggregate.

Prove before continuing

The downloadable archive checksum verifies before execution.The capstone covers the journey target without inventing provider completion.Browser and HTTP surfaces report the same durable version.
Lab 8 · 15 min

Qualify the real integration boundary

Replace only reviewed adapter seams and collect independent production evidence without weakening application invariants.

Build

Discovery-to-save rate and Mappls Pin continuityStop edits, duplicates, limits, and version conflictsRoute preview latency, failures, profiles, and revisionsTime from preview to start and stale-preview invalidationVisited and skipped stops with reasonActive trips without recent progressIdempotent replay, outbox backlog, and restart recovery

Prove before continuing

Exact product entitlement and regional behavior are validated separately.Provider contract tests cover success, rejection, throttling, timeout, and unknown outcome.Security, privacy, operations, rollback, and product owners approve exact evidence.Fixture completion is never presented as provider or production completion.

Application-owned reliability scaffolds

The aggregate and SQL examples implement host truth; the fixture clients call the credential-free Journey Lab. Replace only the separately reviewed provider adapter seam.

Durable multi-stop itinerary workshop scaffolds
type State = "draft" | "planned" | "active" | "paused" | "completed" | "cancelled";
type CommandName = "create_trip" | "add_or_reorder_stop" | "preview_route" | "start_trip" | "pause_trip" | "resume_trip" | "visit_or_skip_next" | "complete_trip" | "cancel_trip";

type Command = {
  name: CommandName;
  aggregateId: string;
  expectedVersion: number;
  idempotencyKey: string;
};

const transitions = {
  "create_trip": { from: [null], to: "draft", event: "trip.created" },
  "add_or_reorder_stop": { from: ["draft", "planned"], to: "draft", event: "trip.sequence_changed" },
  "preview_route": { from: ["draft"], to: "planned", event: "trip.route_previewed" },
  "start_trip": { from: ["planned"], to: "active", event: "trip.started" },
  "pause_trip": { from: ["active"], to: "paused", event: "trip.paused" },
  "resume_trip": { from: ["paused"], to: "active", event: "trip.resumed" },
  "visit_or_skip_next": { from: ["active"], to: "active", event: "trip.stop_completed" },
  "complete_trip": { from: ["active"], to: "completed", event: "trip.completed" },
  "cancel_trip": { from: ["draft", "planned", "active", "paused"], to: "cancelled", event: "trip.cancelled" },
} as const;

export function decide(current: { state: State | null; version: number }, command: Command) {
  const rule = transitions[command.name];
  if (command.expectedVersion !== current.version) throw new Error("version_conflict");
  if (!rule.from.includes(current.state as never)) throw new Error("invalid_transition");
  return {
    state: rule.to as State,
    version: current.version + 1,
    event: rule.event,
    idempotencyKey: command.idempotencyKey,
  };
}

// Persist the result, immutable event, audit row, and outbox intent atomically.
// Store the first result by idempotencyKey before executing another effect.

Exit with reviewable evidence

All 9 reviewed transitions are implemented with actor and source-state checks.All 9 application event identities are immutable and versioned.Exact replay, idempotency conflict, stale version, invalid transition, and unknown outcome are tested.Aggregate, event, audit, command result, and outbox intent commit atomically.The Weekend Trip Planner capstone passes 8 declared tests after archive checksum verification.Provider entitlement, payload, callback, completion, and production behavior remain independently evidenced.
Workshop completion is not production authority

Workshop completion proves an application-owned reliability design only. Production still requires issued entitlement, exact adapter contract tests, regional and quota validation, security/privacy review, operational drills, and independent release approval.

Trace every external claim to an indexed source

Break the application before connecting the provider.

Run all five hostile scenarios and the maintained capstone test suite. Then qualify the exact provider seam under independently reviewed non-production entitlement.