H1Recursive Audit Round 2
Status: markdown-only audit pass against current app/ route groups and prisma/schema.prisma.
H2Verified surfaces
- Trips have their own planner, detail, join, and schedule surfaces.
- Documents have the richest subsystem surface and remain the document orchestration layer.
- Offers and Orders are thinner and should stay snapshot-driven.
- Products have a real engine split into loaders and rules.
- Projects act as the umbrella platform surface for nested features.
- Assistant is schema-backed and route-backed.
- Sponsor/WeekSlot is schema-backed and operational, not just conceptual.
H2What the docs now cover better
- TripJoin as booking intent.
- BookingBundle as fulfillment wrapper.
- Calendar / agenda as projection, not truth.
- Assistant system and dev prompt boundaries.
- LineItems as shared pricing authority.
- Route map for the main app surfaces.
H2Remaining doc gaps
- Offer and order regeneration edge cases still need tighter separation notes if the implementation evolves.
- Product pricing should eventually get a dedicated, more formal engine spec once the current rule set stabilizes.
- Project sub-surfaces may need additional leaf docs if they become too large to keep under one README.
H2Outcome
The audit pass confirms the docs are moving toward one canonical hub per feature area with route-aware notes and schema-backed contracts.