md / archive / recap / 20260422_schema-gap-audit.md
Molino⺢Pro

20260422_schema-gap-audit

Master Codebase Guidebook
Markdown + HTML Dev-Docs Renderer - Frontend Client Module

Default Index
Open README.md
Root: README.mdrecap
Milestones
⬆ Parent folder📝 20260421_trips-next-step-recap📝 20260421_trips-spec-next-steps-audit📝 20260422_module-status-audit📝 20260422_recursive-audit-round2📝 20260422_schema-gap-audit📝 micro-goals.next-steps-specs📝 README📝 recursive-audit-playbook
H1Schema Gap Audit

Status: verified against prisma/schema.prisma and current dev-docs contents.

Scope:

  • Trips
  • TripJoin
  • Weekly sponsor system
  • Deliverables
  • Calendar / agenda layer
  • Assistant system
  • Dev prompt layer
  • Routes and projection boundaries
H2Verified present in schema
  • Trip
  • LineItem
  • Offer
  • Order
  • TripJoin
  • WeekSlot
  • WeekAssignment
  • WeekUpdate
  • Donation
  • Deliverable
  • CalendarEvent
  • AgendaNote
  • MapLocation
  • AssistantThread
  • AssistantMessage
  • AIContext
  • AIPersona
H2What is already documented well enough
  • Trips hub boundary.
  • Document engine / Offer / Order / LineItem relationships.
  • Calendar projection as a Trips-related concern.
  • Assistant modes as a general concept in the broader framework notes.
H2What still needed explicit docs
  • TripJoin contract.
  • WeekSlot commercial role.
  • Deliverable projection role.
  • Assistant system boundary.
  • Dev prompt boundary.
  • Route map.
  • Snapshot discipline.
  • Shared LineItem authority across Trip, Experience, Document, Offer, and Order.
H2Resolution

The codebase does not need new schema entities for these concerns. The docs need to expose the existing schema-backed systems more clearly, with one canonical note per topic and archive copies for older variants.