Phase 0: Walking Skeleton¶

The walking skeleton established the first end-to-end scan: a request crossed the API Gateway, Passport resolved a database-seeded product, persisted a scan, attempted to publish a fact, and the consumer application displayed the result.

What this phase proved¶

• independently deployable services could start in one Compose environment;
• schema-per-service roles and migrations were viable;
• a public scan could cross the Gateway into Passport;
• JSON Schema-generated event types could connect Go and TypeScript services;
• the browser could use an HTTP adapter while retaining an in-memory development adapter.

Superseded details¶

This phase used database-seeded producer products and an earlier Go package layout. Producer systems later became authoritative, and persisted brand catalog rows were replaced with synchronized in-memory projections. A single Go core package with directional adapters was later adopted for Passport, Fridge, and Shopping List.

Publication after database commit was fire-and-forget. That known delivery gap remains documented under Event Sourcing and must not be described as reliable delivery.

Use the current Key Flows, Domain, and Software Structure for implementation guidance.