• Editable block-based document system exists.
• Pagination engine uses engine/wagon separation.
• Autosave/queueSave plumbing exists.
• AI-assisted document generation exists.
• Trip data is embedded and editable in the document surface.
• PDF export is wired in the document tooling.

Working, but not fully standardized.

• deterministic block IDs are not yet clearly enforced
• no-content-loss between engine and wagon still needs continued verification
• exact reload-state reproduction still needs audit

• Trip creation and edit surfaces exist.
• Trip persistence exists in Prisma.
• TripCities and route composition are present.
• Pricing estimation is implemented through the trip engine.

Working, with some remaining normalization.

• stable ID is present at the database level
• idempotent persistence still deserves re-checks
• join-mode nuance still needs policy cleanup

• LineItems are generated from trip pricing.
• Document -> LineItems plumbing exists.
• Offer and Order both consume LineItems.

Working, but legacy mutation patterns still exist.

• traceability via sourceType and sourceId is supported in schema
• delete + recreate discipline is not yet universally enforced
• totals should continue to derive from LineItems only

• Document pagination projection is implemented.
• Offer and Order projection actions exist.
• Apps Script and office export concepts are documented.

Partial but functional.

• document export and calendar export are not yet verified as a complete stable pipeline
• external keys for calendar/export sync still need hardening

• Trips landing and featured surfaces exist.
• Trips new, trip detail, and schedule surfaces exist.
• DB-backed trips, cities, and experiences are used in the route stack.

Partial but useful.

• CTA coverage is mostly there, but still needs final route/read-model cleanup
• featured data and city data should continue to be validated as DB-driven

• Offer creation and Offer read models exist.
• Offer line-item presentation exists.
• Trip/Product/Experience pickers exist for offer composition.

Partial.

• snapshot creation is present, but legacy mutation code still exists
• confirmation logic should remain separated from mutable offer editing

• Order creation from offer exists.
• Order snapshot copying exists.
• Order projection hooks exist.

Partial.

• atomic snapshot discipline still needs hardening
• offer lock after order is not yet fully enforced in a single canonical path

• TripDays generation exists.
• Trip schedule surfaces exist.

Working.

• schedule generation is the stronger part of the current trips stack
• export should continue to reuse the same TripDays structure

• Experience schema and engine family exist.
• Experience pricing loaders and rules mirror the trip engine shape.

Partial.

• selection inside planner and end-to-end pricing normalization still need final harmonization

• CalendarEvent, AgendaNote, and MapLocation exist in Prisma.

Partial.

• schema support is there
• projection and idempotent sync still need the actual operational layer to be fully proven

• Apps Script docs and office-server planning are present.
• Export concepts are wired into document controls and trip planning notes.

Partial.

• the docs are ahead of the verified runtime contract
• stable endpoint contracts still need completion

• TripJoin exists in Prisma.
• TripJoin create/read/recompute actions exist.
• Join UI exists on the trip detail surface.
• pricingSnapshot is stored on TripJoin.

Partial.

• the join flow exists, but the shared/private/add-participants policy still needs clear finalization
• optional Offer-from-join behavior is not yet the canonical path

• Documented in the trips planning notes.

Missing.

• no verified app implementation found yet

• WeekSlot exists in Prisma.
• Sponsor route and execution notes exist.

Partial.

• monetization/execution wiring still needs the LineItem / Offer / Deliverable links to be formalized

• Deliverable exists in Prisma.

Partial.

• the projection-node concept is documented
• the end-to-end projection linkage still needs tightening

• Stripe is referenced in docs and older planning artifacts.

Missing / not yet complete in the audited app paths.

• no complete order-to-payment lifecycle was verified in the current app routes/actions

• FareHarbor appears in docs, embeds, and planning notes.

Partial.

• there are embedded presentation surfaces and strong docs intent
• a validated sync/execution bridge is not yet fully proven

• ProjectContact exists in Prisma and is linked to several commercial entities.

Partial.

• the contact layer exists structurally
• the cross-pipeline reuse story still needs clearer formalization

• AssistantThread, AssistantMessage, AIContext, and AIPersona exist in Prisma.
• runDevLayerAction persists threads, messages, and dev prompts.

Working / partial.

• structured outputs are present
• mode/tool normalization still has legacy complexity

• DevPrompt entities and thread/message structures exist.
• Prompt history and generation flows exist.

Partial.

• the tooling surface is present, but it is still fragmented across docs, modes, and assistant paths