About · Data model
What the platform knows about
22 entity types · 171 seeded records · click any entity to see the surfaces that render it.
Entity types
22
Distinct domain entities
Total records
171
Seeded across the prototype
Cross-references
87
Foreign-key edges between entities
AI surfaces grounded
28
Citations resolve into this graph
Company · Client · Event — the spine of the data model.
Every entity sits within this hierarchy. Permissions, branding, and budgeting cascade top-down; activity rolls up bottom-up.
Entities
22 types · 171 records2 records
Fields
Rendered on
7 records
Fields
Rendered on
14 records
Fields
Rendered on
29 records
Fields
Rendered on
8 records
Fields
Rendered on
12 records
Fields
Rendered on
6 records
Fields
Rendered on
3 records
Fields
Rendered on
15 records
Fields
Rendered on
5 records
Fields
Rendered on
10 records
Fields
Rendered on
1 record
Fields
Rendered on
7 records
Fields
Rendered on
30 records
Fields
2 records
Fields
Rendered on
1 record
Fields
Rendered on
1 record
Fields
Rendered on
3 records
Fields
Rendered on
3 records
Fields
Rendered on
9 records
Fields
Rendered on
2 records
Fields
Rendered on
1 record
Fields
Rendered on
How entities link to each other. The Playbook’s graph is dense — the AI uses these edges as citation paths.
- EventVendorvia Contract / VendorProposal / EngagedVendoran event lists its engaged vendors; each engagement traces back to a contract and a proposal
- EventContractorvia JobCodejob codes attribute hours to a person against a specific event
- EventVenuevia event.venue fieldone venue per event; venue regulations cascade to the event
- EventEventTemplatevia event.template fieldtemplates seed the BOM, phases, and budget skeleton
- EventProjectBurnvia eventSlugforecast vs actual hours rolled up per event
- VendorContractvia vendorSlug + eventSlugevery contract links a vendor to an event with anomaly findings
- VendorCatalogItemvia vendorSlugreusable items roll up to the vendor that supplies them
- ContractorContractorFeedbackvia contractorSlug + eventSlugevery past event with a contractor has a behavior + delivery rating
- VenueVenueRegulationsvia venueSlugunion labor, rigging caps, and mandatory vendors travel with the venue
- ClientVizIDPackagevia clientIdeach client has one brand kit — series names, mood tiles, palette
- ClientRetainerEngagementvia clientIdmonthly hours, reviews, and retainer line items per client
When you ask the Playbook a question, it walks the graph: an event leads to its vendors and contractors, a vendor leads to its proposals and contracts, a contractor leads to feedback and job codes. Every answer cites a path through this graph — never an opinion, always an entity, a field, and a value.
The AI flags; the producer decides. Citations resolve into the same entity surfaces a human producer would open by hand — so every number is auditable, every claim is traceable, and no answer is a black box.
AI grounded in 171 seeded records across 22 entity types.