Models
These are not projects. They are portable ways to think about permissions, validation, multi-tenancy and workflow state.
A reusable model for turning event operations into public schedules, speaker data and content updates.
flowchart LR Organizers --> Content Speakers --> Content Sponsors --> Content Content --> Review Review --> Publish Publish --> Attendees
Use this model when public event information depends on several internal actors and last-minute changes.
A reusable organization, team, role and user model for event-platform permissions.
flowchart TD Organization --> Team Team --> Role Role --> User Role --> Action Action --> Resource
Use this model when the same platform must support multiple teams, events or organizations without scattering one-off permission checks across pages.
Do not introduce the full hierarchy before the product has proven that team or organization boundaries matter.
A model for keeping people accountable when AI output or automated work reaches production.
flowchart TD Draft[Draft] --> InReview[In review] InReview --> Approved[Approved] InReview --> Rejected[Rejected] InReview --> NeedsChanges[Needs changes] NeedsChanges --> Draft Approved --> Published[Published]
Use this model when automation creates draft work but humans remain responsible for quality, policy or final publication.
A model for introducing tenancy only after repeated product behavior proves the need.
flowchart TD Single[Single tenant] --> Repeated[Repeated instances] Repeated --> Teams Teams --> Organizations Organizations --> Permissions Permissions --> Platform
Use this model when a one-off product begins to repeat across events, customers or organizations.
A model for verifying access, state and exceptions in event or admission workflows.
flowchart TD Ticket --> Lookup Lookup --> Valid Lookup --> Invalid Lookup --> Exception Valid --> Admit Exception --> ManualReview
Use this model when entry workflows need both fast happy paths and clear exception handling.