How lunar-studio-dev/travelkar-holidays works
TRAVELKARS is a planning-document set for a travel-operations product, not a built application. Its principal workflow is to gather and lock requirements through grilling, record canonical terminology and rules, then describe real client/staff work in the user flow before producing a developer requirements document. The README also identifies planned capabilities such as tour planning, quotations, trip pieces, paper pooling, and money tracking; their details are not available in the supplied excerpts. No runtime components or calls can be established.
Main entry points: product-spec.md Locked product rules · convo2.md Second grilling · user-flow.md User flow · convo1.md First grilling
Components 8
Planning inputs
- First grilling
docs/grilling/convo1.md - Second grilling
docs/grilling/convo2.md
Product definition
- Canonical glossary
CONTEXT.md - Locked product rules
docs/product-spec.md
Workflows
- User flow
docs/user-flow.md - Developer requirements
Other components
- Builders and agents
- Client and staff
Connections 7
- First grilling → Second grilling: continues grilling
- Second grilling → Locked product rules: informs rules
- Builders and agents → Canonical glossary: uses glossary
- Builders and agents → Locked product rules: uses rules
- Client and staff → User flow: uses workflow
- Locked product rules → Developer requirements: feeds requirements
- User flow → Developer requirements: feeds requirements