One persistent identity
Person answers “who is this?” independently of a particular production.
The visual architecture guide
See how it fits together.
Scroll to build the model, one connection at a time. Open any concept to go deeper.
Start with the real-world organization.
A Production brings specialized people together temporarily. Their schedules, information and working relationships change across stages. Phone contacts, messages, PDFs and spreadsheets carry pieces of that context; the people persist after the organization disperses.
1Development
Producer · Writer · Director
- Financing
- Initial creative development
- Script and concept
2Pre-Production
Production office · Department heads · Casting
- Hiring
- Casting
- Availability
- Locations
- Scheduling
- Department preparation
- Equipment
- Approvals
3Production
Cast · Shooting crew · Production office
- Production Days
- Call sheets
- Shooting
- Department coordination
- Presence
- Changes
- Daily communication
4Wrap
Production management · Department heads · Post
- Equipment returns
- Media handoff
- Department closeout
- Outstanding paperwork
5Post-Production
Editorial · Sound · VFX · Color
- Editorial
- Sound
- Music
- VFX
- Color
- Review
- Delivery preparation
6Delivery / Distribution
Producer · Distribution · Marketing
- Masters
- Marketing
- Distribution
- Archival
Phases overlap. People, decisions and resources carry forward; the active crew changes with the work.
One Production · 125 people
Fictional demo. Reporting lines illustrate one simplified organization, not a universal film hierarchy. Department leads report to the Producer here; other assignments report to their department lead. Communication and software permissions are separate.
Full connection graph · all 125 people
Arrows run from supervisor to direct report. The reporting table below lists every relationship.
Production125 distinct people
ProducerCrew member 001
↓ Department reporting lines
Production Management10 people · Producer
Production leadershipProducerCrew member 001
- Line ProducerCrew member 002Reports to Producer
- UPM where applicableCrew member 003Reports to Producer
- Production ManagerCrew member 004Reports to Producer
- Production CoordinatorCrew member 005Reports to Producer
- Production SecretaryCrew member 006Reports to Producer
- Production AssistantsCrew member 007Reports to Producer
- Production AssistantsCrew member 008Reports to Producer
- Production AssistantsCrew member 009Reports to Producer
- Production AssistantsCrew member 010Reports to Producer
Assistant Directors5 people · 1st AD
Producer1st ADCrew member 011
- 1st ADCrew member 011Reports to Producer
- 2nd ADCrew member 012Reports to 1st AD
- Additional ADs where applicableCrew member 013Reports to 1st AD
- Additional ADs where applicableCrew member 014Reports to 1st AD
- Additional ADs where applicableCrew member 015Reports to 1st AD
Directing3 people · Director
ProducerDirectorCrew member 016
- DirectorCrew member 016Reports to Producer
- Assistant to DirectorCrew member 017Reports to Director
- Additional directing supportCrew member 018Reports to Director
Camera9 people · Director of Photography
ProducerDirector of PhotographyCrew member 019
- Director of PhotographyCrew member 019Reports to Producer
- Camera OperatorsCrew member 020Reports to Director of Photography
- 1st Assistant CameraCrew member 021Reports to Director of Photography
- 2nd Assistant CameraCrew member 022Reports to Director of Photography
- DIT / Data where applicableCrew member 023Reports to Director of Photography
- Specialty camera roles where applicableCrew member 024Reports to Director of Photography
- Specialty camera roles where applicableCrew member 025Reports to Director of Photography
- Specialty camera roles where applicableCrew member 026Reports to Director of Photography
- Specialty camera roles where applicableCrew member 027Reports to Director of Photography
Grip7 people · Key Grip
ProducerKey GripCrew member 028
- Key GripCrew member 028Reports to Producer
- Best Boy GripCrew member 029Reports to Key Grip
- GripsCrew member 030Reports to Key Grip
- Dolly Grip where applicableCrew member 031Reports to Key Grip
- Dolly Grip where applicableCrew member 032Reports to Key Grip
- Dolly Grip where applicableCrew member 033Reports to Key Grip
- Dolly Grip where applicableCrew member 034Reports to Key Grip
Electric7 people · Gaffer
ProducerGafferCrew member 035
- GafferCrew member 035Reports to Producer
- Best Boy ElectricCrew member 036Reports to Gaffer
- ElectriciansCrew member 037Reports to Gaffer
- ElectriciansCrew member 038Reports to Gaffer
- ElectriciansCrew member 039Reports to Gaffer
- ElectriciansCrew member 040Reports to Gaffer
- ElectriciansCrew member 041Reports to Gaffer
Sound3 people · Production Sound Mixer
ProducerProduction Sound MixerCrew member 042
- Production Sound MixerCrew member 042Reports to Producer
- Boom OperatorCrew member 043Reports to Production Sound Mixer
- Sound UtilityCrew member 044Reports to Production Sound Mixer
Art6 people · Production Designer
ProducerProduction DesignerCrew member 045
- Production DesignerCrew member 045Reports to Producer
- Art DirectorCrew member 046Reports to Production Designer
- Set DecorationCrew member 047Reports to Production Designer
- PropsCrew member 048Reports to Production Designer
- Graphic DesignCrew member 049Reports to Production Designer
- ConstructionCrew member 050Reports to Production Designer
Set Decoration5 people · Set Decorator
ProducerSet DecoratorCrew member 051
- Set DecoratorCrew member 051Reports to Producer
- LeadpersonCrew member 052Reports to Set Decorator
- Set DressersCrew member 053Reports to Set Decorator
- Set DressersCrew member 054Reports to Set Decorator
- Set DressersCrew member 055Reports to Set Decorator
Props3 people · Property Master
ProducerProperty MasterCrew member 056
- Property MasterCrew member 056Reports to Producer
- Assistant PropsCrew member 057Reports to Property Master
- On-set PropsCrew member 058Reports to Property Master
Construction5 people · Construction Coordinator
ProducerConstruction CoordinatorCrew member 059
- Construction CoordinatorCrew member 059Reports to Producer
- CarpentersCrew member 060Reports to Construction Coordinator
- Scenic ArtistsCrew member 061Reports to Construction Coordinator
- Scenic ArtistsCrew member 062Reports to Construction Coordinator
- Scenic ArtistsCrew member 063Reports to Construction Coordinator
Costume4 people · Costume Designer
ProducerCostume DesignerCrew member 064
- Costume DesignerCrew member 064Reports to Producer
- Costume SupervisorCrew member 065Reports to Costume Designer
- Set CostumersCrew member 066Reports to Costume Designer
- Set CostumersCrew member 067Reports to Costume Designer
Hair2 people · Hair Department Head
ProducerHair Department HeadCrew member 068
- Hair Department HeadCrew member 068Reports to Producer
- Hair StylistsCrew member 069Reports to Hair Department Head
Makeup3 people · Makeup Department Head
ProducerMakeup Department HeadCrew member 070
- Makeup Department HeadCrew member 070Reports to Producer
- Makeup ArtistsCrew member 071Reports to Makeup Department Head
- Makeup ArtistsCrew member 072Reports to Makeup Department Head
Locations4 people · Location Manager
ProducerLocation ManagerCrew member 073
- Location ManagerCrew member 073Reports to Producer
- Assistant Location ManagerCrew member 074Reports to Location Manager
- Location AssistantsCrew member 075Reports to Location Manager
- Location AssistantsCrew member 076Reports to Location Manager
Transportation6 people · Transportation Coordinator
ProducerTransportation CoordinatorCrew member 077
- Transportation CoordinatorCrew member 077Reports to Producer
- Transportation CaptainCrew member 078Reports to Transportation Coordinator
- DriversCrew member 079Reports to Transportation Coordinator
- DriversCrew member 080Reports to Transportation Coordinator
- DriversCrew member 081Reports to Transportation Coordinator
- DriversCrew member 082Reports to Transportation Coordinator
Cast10 people · Principal Cast
ProducerPrincipal CastCrew member 083
- Principal CastCrew member 083Reports to Producer
- Supporting CastCrew member 084Reports to Principal Cast
- Background performers where applicableCrew member 085Reports to Principal Cast
- Background performers where applicableCrew member 086Reports to Principal Cast
- Background performers where applicableCrew member 087Reports to Principal Cast
- Background performers where applicableCrew member 088Reports to Principal Cast
- Background performers where applicableCrew member 089Reports to Principal Cast
- Background performers where applicableCrew member 090Reports to Principal Cast
- Background performers where applicableCrew member 091Reports to Principal Cast
- Background performers where applicableCrew member 092Reports to Principal Cast
Stunts4 people · Stunt Coordinator
ProducerStunt CoordinatorCrew member 093
- Stunt CoordinatorCrew member 093Reports to Producer
- Stunt PerformersCrew member 094Reports to Stunt Coordinator
- Stunt PerformersCrew member 095Reports to Stunt Coordinator
- Stunt PerformersCrew member 096Reports to Stunt Coordinator
Special Effects3 people · Special Effects Supervisor
ProducerSpecial Effects SupervisorCrew member 097
- Special Effects SupervisorCrew member 097Reports to Producer
- Special Effects TechniciansCrew member 098Reports to Special Effects Supervisor
- Special Effects TechniciansCrew member 099Reports to Special Effects Supervisor
VFX / Data3 people · VFX Supervisor
ProducerVFX SupervisorCrew member 100
- VFX SupervisorCrew member 100Reports to Producer
- On-set VFX supportCrew member 101Reports to VFX Supervisor
- Data support where applicableCrew member 102Reports to VFX Supervisor
Script Supervision1 people · Script Supervisor
ProducerScript SupervisorCrew member 103
- Script SupervisorCrew member 103Reports to Producer
Catering / Craft5 people · Catering Lead
ProducerCatering LeadCrew member 104
- Catering LeadCrew member 104Reports to Producer
- Catering CrewCrew member 105Reports to Catering Lead
- Craft ServiceCrew member 106Reports to Catering Lead
- Craft ServiceCrew member 107Reports to Catering Lead
- Craft ServiceCrew member 108Reports to Catering Lead
Stills / BTS / EPK2 people · Unit Stills Photographer
ProducerUnit Stills PhotographerCrew member 109
- Unit Stills PhotographerCrew member 109Reports to Producer
- BTS Photographer / EPK CrewCrew member 110Reports to Unit Stills Photographer
Security2 people · Security Lead
ProducerSecurity LeadCrew member 111
- Security LeadCrew member 111Reports to Producer
- Security CrewCrew member 112Reports to Security Lead
Safety / Medical2 people · Set Medic
ProducerSet MedicCrew member 113
- Set MedicCrew member 113Reports to Producer
- Safety Officer where applicableCrew member 114Reports to Set Medic
Post-Production8 people · Editor
ProducerEditorCrew member 115
- EditorCrew member 115Reports to Producer
- Assistant EditorCrew member 116Reports to Editor
- Post SupervisorCrew member 117Reports to Editor
- SoundCrew member 118Reports to Editor
- MusicCrew member 119Reports to Editor
- VFXCrew member 120Reports to Editor
- ColorCrew member 121Reports to Editor
- ColorCrew member 122Reports to Editor
Marketing / Client3 people · Client Representative
ProducerClient RepresentativeCrew member 123
- Client RepresentativeCrew member 123Reports to Producer
- Marketing LeadCrew member 124Reports to Client Representative
- Agency / Brand support where applicableCrew member 125Reports to Client Representative
All 125 people and reporting relationships
| Person | Assignment | Department | Reports to |
|---|---|---|---|
| Crew member 001 | Producer | Production Management | Production leadership |
| Crew member 002 | Line Producer | Production Management | Crew member 001 · Producer |
| Crew member 003 | UPM where applicable | Production Management | Crew member 001 · Producer |
| Crew member 004 | Production Manager | Production Management | Crew member 001 · Producer |
| Crew member 005 | Production Coordinator | Production Management | Crew member 001 · Producer |
| Crew member 006 | Production Secretary | Production Management | Crew member 001 · Producer |
| Crew member 007 | Production Assistants | Production Management | Crew member 001 · Producer |
| Crew member 008 | Production Assistants | Production Management | Crew member 001 · Producer |
| Crew member 009 | Production Assistants | Production Management | Crew member 001 · Producer |
| Crew member 010 | Production Assistants | Production Management | Crew member 001 · Producer |
| Crew member 011 | 1st AD | Assistant Directors | Crew member 001 · Producer |
| Crew member 012 | 2nd AD | Assistant Directors | Crew member 011 · 1st AD |
| Crew member 013 | Additional ADs where applicable | Assistant Directors | Crew member 011 · 1st AD |
| Crew member 014 | Additional ADs where applicable | Assistant Directors | Crew member 011 · 1st AD |
| Crew member 015 | Additional ADs where applicable | Assistant Directors | Crew member 011 · 1st AD |
| Crew member 016 | Director | Directing | Crew member 001 · Producer |
| Crew member 017 | Assistant to Director | Directing | Crew member 016 · Director |
| Crew member 018 | Additional directing support | Directing | Crew member 016 · Director |
| Crew member 019 | Director of Photography | Camera | Crew member 001 · Producer |
| Crew member 020 | Camera Operators | Camera | Crew member 019 · Director of Photography |
| Crew member 021 | 1st Assistant Camera | Camera | Crew member 019 · Director of Photography |
| Crew member 022 | 2nd Assistant Camera | Camera | Crew member 019 · Director of Photography |
| Crew member 023 | DIT / Data where applicable | Camera | Crew member 019 · Director of Photography |
| Crew member 024 | Specialty camera roles where applicable | Camera | Crew member 019 · Director of Photography |
| Crew member 025 | Specialty camera roles where applicable | Camera | Crew member 019 · Director of Photography |
| Crew member 026 | Specialty camera roles where applicable | Camera | Crew member 019 · Director of Photography |
| Crew member 027 | Specialty camera roles where applicable | Camera | Crew member 019 · Director of Photography |
| Crew member 028 | Key Grip | Grip | Crew member 001 · Producer |
| Crew member 029 | Best Boy Grip | Grip | Crew member 028 · Key Grip |
| Crew member 030 | Grips | Grip | Crew member 028 · Key Grip |
| Crew member 031 | Dolly Grip where applicable | Grip | Crew member 028 · Key Grip |
| Crew member 032 | Dolly Grip where applicable | Grip | Crew member 028 · Key Grip |
| Crew member 033 | Dolly Grip where applicable | Grip | Crew member 028 · Key Grip |
| Crew member 034 | Dolly Grip where applicable | Grip | Crew member 028 · Key Grip |
| Crew member 035 | Gaffer | Electric | Crew member 001 · Producer |
| Crew member 036 | Best Boy Electric | Electric | Crew member 035 · Gaffer |
| Crew member 037 | Electricians | Electric | Crew member 035 · Gaffer |
| Crew member 038 | Electricians | Electric | Crew member 035 · Gaffer |
| Crew member 039 | Electricians | Electric | Crew member 035 · Gaffer |
| Crew member 040 | Electricians | Electric | Crew member 035 · Gaffer |
| Crew member 041 | Electricians | Electric | Crew member 035 · Gaffer |
| Crew member 042 | Production Sound Mixer | Sound | Crew member 001 · Producer |
| Crew member 043 | Boom Operator | Sound | Crew member 042 · Production Sound Mixer |
| Crew member 044 | Sound Utility | Sound | Crew member 042 · Production Sound Mixer |
| Crew member 045 | Production Designer | Art | Crew member 001 · Producer |
| Crew member 046 | Art Director | Art | Crew member 045 · Production Designer |
| Crew member 047 | Set Decoration | Art | Crew member 045 · Production Designer |
| Crew member 048 | Props | Art | Crew member 045 · Production Designer |
| Crew member 049 | Graphic Design | Art | Crew member 045 · Production Designer |
| Crew member 050 | Construction | Art | Crew member 045 · Production Designer |
| Crew member 051 | Set Decorator | Set Decoration | Crew member 001 · Producer |
| Crew member 052 | Leadperson | Set Decoration | Crew member 051 · Set Decorator |
| Crew member 053 | Set Dressers | Set Decoration | Crew member 051 · Set Decorator |
| Crew member 054 | Set Dressers | Set Decoration | Crew member 051 · Set Decorator |
| Crew member 055 | Set Dressers | Set Decoration | Crew member 051 · Set Decorator |
| Crew member 056 | Property Master | Props | Crew member 001 · Producer |
| Crew member 057 | Assistant Props | Props | Crew member 056 · Property Master |
| Crew member 058 | On-set Props | Props | Crew member 056 · Property Master |
| Crew member 059 | Construction Coordinator | Construction | Crew member 001 · Producer |
| Crew member 060 | Carpenters | Construction | Crew member 059 · Construction Coordinator |
| Crew member 061 | Scenic Artists | Construction | Crew member 059 · Construction Coordinator |
| Crew member 062 | Scenic Artists | Construction | Crew member 059 · Construction Coordinator |
| Crew member 063 | Scenic Artists | Construction | Crew member 059 · Construction Coordinator |
| Crew member 064 | Costume Designer | Costume | Crew member 001 · Producer |
| Crew member 065 | Costume Supervisor | Costume | Crew member 064 · Costume Designer |
| Crew member 066 | Set Costumers | Costume | Crew member 064 · Costume Designer |
| Crew member 067 | Set Costumers | Costume | Crew member 064 · Costume Designer |
| Crew member 068 | Hair Department Head | Hair | Crew member 001 · Producer |
| Crew member 069 | Hair Stylists | Hair | Crew member 068 · Hair Department Head |
| Crew member 070 | Makeup Department Head | Makeup | Crew member 001 · Producer |
| Crew member 071 | Makeup Artists | Makeup | Crew member 070 · Makeup Department Head |
| Crew member 072 | Makeup Artists | Makeup | Crew member 070 · Makeup Department Head |
| Crew member 073 | Location Manager | Locations | Crew member 001 · Producer |
| Crew member 074 | Assistant Location Manager | Locations | Crew member 073 · Location Manager |
| Crew member 075 | Location Assistants | Locations | Crew member 073 · Location Manager |
| Crew member 076 | Location Assistants | Locations | Crew member 073 · Location Manager |
| Crew member 077 | Transportation Coordinator | Transportation | Crew member 001 · Producer |
| Crew member 078 | Transportation Captain | Transportation | Crew member 077 · Transportation Coordinator |
| Crew member 079 | Drivers | Transportation | Crew member 077 · Transportation Coordinator |
| Crew member 080 | Drivers | Transportation | Crew member 077 · Transportation Coordinator |
| Crew member 081 | Drivers | Transportation | Crew member 077 · Transportation Coordinator |
| Crew member 082 | Drivers | Transportation | Crew member 077 · Transportation Coordinator |
| Crew member 083 | Principal Cast | Cast | Crew member 001 · Producer |
| Crew member 084 | Supporting Cast | Cast | Crew member 083 · Principal Cast |
| Crew member 085 | Background performers where applicable | Cast | Crew member 083 · Principal Cast |
| Crew member 086 | Background performers where applicable | Cast | Crew member 083 · Principal Cast |
| Crew member 087 | Background performers where applicable | Cast | Crew member 083 · Principal Cast |
| Crew member 088 | Background performers where applicable | Cast | Crew member 083 · Principal Cast |
| Crew member 089 | Background performers where applicable | Cast | Crew member 083 · Principal Cast |
| Crew member 090 | Background performers where applicable | Cast | Crew member 083 · Principal Cast |
| Crew member 091 | Background performers where applicable | Cast | Crew member 083 · Principal Cast |
| Crew member 092 | Background performers where applicable | Cast | Crew member 083 · Principal Cast |
| Crew member 093 | Stunt Coordinator | Stunts | Crew member 001 · Producer |
| Crew member 094 | Stunt Performers | Stunts | Crew member 093 · Stunt Coordinator |
| Crew member 095 | Stunt Performers | Stunts | Crew member 093 · Stunt Coordinator |
| Crew member 096 | Stunt Performers | Stunts | Crew member 093 · Stunt Coordinator |
| Crew member 097 | Special Effects Supervisor | Special Effects | Crew member 001 · Producer |
| Crew member 098 | Special Effects Technicians | Special Effects | Crew member 097 · Special Effects Supervisor |
| Crew member 099 | Special Effects Technicians | Special Effects | Crew member 097 · Special Effects Supervisor |
| Crew member 100 | VFX Supervisor | VFX / Data | Crew member 001 · Producer |
| Crew member 101 | On-set VFX support | VFX / Data | Crew member 100 · VFX Supervisor |
| Crew member 102 | Data support where applicable | VFX / Data | Crew member 100 · VFX Supervisor |
| Crew member 103 | Script Supervisor | Script Supervision | Crew member 001 · Producer |
| Crew member 104 | Catering Lead | Catering / Craft | Crew member 001 · Producer |
| Crew member 105 | Catering Crew | Catering / Craft | Crew member 104 · Catering Lead |
| Crew member 106 | Craft Service | Catering / Craft | Crew member 104 · Catering Lead |
| Crew member 107 | Craft Service | Catering / Craft | Crew member 104 · Catering Lead |
| Crew member 108 | Craft Service | Catering / Craft | Crew member 104 · Catering Lead |
| Crew member 109 | Unit Stills Photographer | Stills / BTS / EPK | Crew member 001 · Producer |
| Crew member 110 | BTS Photographer / EPK Crew | Stills / BTS / EPK | Crew member 109 · Unit Stills Photographer |
| Crew member 111 | Security Lead | Security | Crew member 001 · Producer |
| Crew member 112 | Security Crew | Security | Crew member 111 · Security Lead |
| Crew member 113 | Set Medic | Safety / Medical | Crew member 001 · Producer |
| Crew member 114 | Safety Officer where applicable | Safety / Medical | Crew member 113 · Set Medic |
| Crew member 115 | Editor | Post-Production | Crew member 001 · Producer |
| Crew member 116 | Assistant Editor | Post-Production | Crew member 115 · Editor |
| Crew member 117 | Post Supervisor | Post-Production | Crew member 115 · Editor |
| Crew member 118 | Sound | Post-Production | Crew member 115 · Editor |
| Crew member 119 | Music | Post-Production | Crew member 115 · Editor |
| Crew member 120 | VFX | Post-Production | Crew member 115 · Editor |
| Crew member 121 | Color | Post-Production | Crew member 115 · Editor |
| Crew member 122 | Color | Post-Production | Crew member 115 · Editor |
| Crew member 123 | Client Representative | Marketing / Client | Crew member 001 · Producer |
| Crew member 124 | Marketing Lead | Marketing / Client | Crew member 123 · Client Representative |
| Crew member 125 | Agency / Brand support where applicable | Marketing / Client | Crew member 123 · Client Representative |
Jump to a visual chapter
1 / 8
Start with a person
Different context, same person
Profile presents the person. Membership places that same identity inside a temporary Production.
Person · Profile · Membership · Production
Keep the professional connection
A deliberate Roster Relationship can outlast the shared work. The production membership itself does not become that relationship.
Person · Profile · Membership · Production · Roster relationship
Identity persists. A profile presents it.
All connections in words
- Person has presentation Profile.
- Person participates through Membership.
- Membership belongs to Production.
- Person may retain a reviewed Roster relationship.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
Start with a person
Drag a card to rearrange it. Select it to learn more.
2 / 8
Separate belonging from work
Who belongs here?
Membership connects a Person to a Production. It records participation in that context.
What work do they perform?
The membership can have assignments. Each assignment describes a role; it is distinct from an individual to-do task.
Person · Membership · Production · Assignment · Role
Organize the work
Groups organize assignments without redefining the person or turning a descriptive role into a permission.
Person · Membership · Production · Assignment · Role · Group
Membership is participation. Assignment describes work.
All connections in words
- Person participates through Membership.
- Membership belongs to Production.
- Membership performs work through Assignment.
- Assignment describes work as Role.
- Assignment belongs to / leads Group.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
Separate belonging from work
Drag a card to rearrange it. Select it to learn more.
3 / 8
Organize, target, authorize
Select recipients
A Group can help resolve an Audience. That audience targets an update to eligible people.
Check the right to act
Permission / Capability governs access to a Resource and eligibility to Review. Receiving a message does not grant either right.
Group · Audience · Update · Permission / Capability · Resource · Review
These are three separate decisions.
All connections in words
- Group can select eligible people for Audience.
- Permission / Capability authorizes eligible Review.
- Permission / Capability controls current access to Resource.
- Audience targets Update.
4 / 8
One review model, many artifacts
Freeze the content being reviewed
A storyboard, document or VFX artifact is a Resource. Review begins from a specific Resource Version.
Run the agreed process
Workflow orders stages. Each stage requests eligible review, using its defined ANY or ALL policy.
Resource · Resource Version · Workflow · Workflow Stage · Review
Record a decision, then select a final
Approval refers to the reviewed version. Final selection remains explicit; approval does not silently replace the canonical artifact.
Resource · Resource Version · Workflow · Workflow Stage · Review · Approval · Final reference
The workflow reviews an exact version.
All connections in words
- Approval supports explicit selection of Final reference.
- Resource has immutable Resource Version.
- Resource Version is reviewed through Workflow.
- Workflow orders Workflow Stage.
- Workflow Stage requests eligible Review.
- Review records a version-specific Approval.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
One review model, many artifacts
Drag a card to rearrange it. Select it to learn more.
5 / 8
Bring work into a day
Connect work to time
An Assignment is called for a Production Day. A Schedule plans the work within that day.
Assignment · Day · Schedule
Publish a shared plan
The schedule is frozen into a Call Sheet. Acknowledgement records receipt of that published version.
Assignment · Day · Schedule · Call Sheet · Acknowledgement
Record what actually happened
Presence records operational attendance. Acknowledging the call sheet is not evidence of checking in on set.
Assignment · Day · Schedule · Call Sheet · Acknowledgement · Presence
Being called, acknowledging and being present differ.
All connections in words
- Assignment is called for work on Day.
- Day plans work through Schedule.
- Schedule is frozen into Call Sheet.
- Call Sheet receives version-specific Acknowledgement.
- Acknowledgement is distinct from recorded Presence.
- Day records Presence.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
Bring work into a day
Drag a card to rearrange it. Select it to learn more.
6 / 8
Compose without taking ownership
Find current obligations
Workflows and Call Sheets contribute eligible obligations to Attention.
Bring the day together
Today combines attention, assignments and scheduled time. Actions return to the owning domains; Today does not become a second source of truth.
Workflow · Call Sheet · Attention · Today · Assignment · Schedule
A view of work is not the owner of work.
All connections in words
- Workflow projects current obligations into Attention.
- Call Sheet projects recipient obligations into Attention.
- Attention contributes actionable work to Today.
- Assignment contributes work to Today.
- Schedule contributes planned time to Today.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
Compose without taking ownership
Drag a card to rearrange it. Select it to learn more.
7 / 8
Follow a request through the system
Enter through the edge
The Web Client reaches Cloudflare Edge. Admitted application requests continue to the Next.js origin on Google Cloud Run.
Evaluate and execute in the domain
Domain services check identity and scoped authority before reading or changing canonical data in Firebase / Google Cloud.
Web Client · Cloudflare Edge · Next.js Origin · Domain Service · Firebase Auth · Firestore
Return a scoped response
The client receives an authorized response projection. Identity checks, permission decisions and UI visibility remain distinct.
Web Client · Cloudflare Edge · Next.js Origin · Domain Service · Firebase Auth · Firestore · Response projection
Each layer has a different responsibility.
All connections in words
- Firestore supplies scoped source data for Response projection.
- Domain Service returns an authorized Response projection.
- Web Client requests application access through Cloudflare Edge.
- Cloudflare Edge forwards admitted requests to Next.js Origin.
- Next.js Origin runs Domain Service.
- Domain Service persists canonical records in Firestore.
- Domain Service checks identity using Firebase Auth.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
Follow a request through the system
Drag a card to rearrange it. Select it to learn more.
8 / 8
Publish a projection
Choose what becomes public
A Profile or Production can supply a public Website projection. Private canonical records remain in the application.
Profile · Production · Website
Configure and publish
Publication delivers the configured website through Cloudflare. A public page is not a second private application record.
Profile · Production · Website · Publication · Cloudflare Edge
Public presentation has its own boundary.
All connections in words
- Production has public projection Website.
- Profile has public projection Website.
- Website is configured for Publication.
- Publication is delivered through Cloudflare Edge.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
Publish a projection
Drag a card to rearrange it. Select it to learn more.
Now choose your own path.
Primitive
Person
A persistent professional identity across changing work contexts.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
A person should not be recreated each time they work on a production.
Example
One person participates in two productions with different work assignments.
Connects to
- Person has presentation Profile
- Person participates through Membership
- Membership identifies Person
- Person responds with Availability
- Person may retain a reviewed Roster relationship
- Resource has person context Person
Implementation notes
Identity persists; access is evaluated in the current collaboration context.
Public evidence: Production membership and work assignments are separate records.
Related workflows
Related decisions
Technical details
Identity persists; access is evaluated in the current collaboration context.
Conceptual explanation; private implementation details are omitted.
Projection
Profile
An editable presentation of a person.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Public biography and contact presentation change independently of identity.
Example
A public profile highlights selected credits while production contact details stay scoped.
Connects to
Implementation notes
A profile is a projection, not membership or access authority.
Public evidence: Websites publish selected projections of canonical contexts.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
A profile is a projection, not membership or access authority.
Conceptual explanation; private implementation details are omitted.
Domain
Roster relationship
A personal professional relationship retained beyond a production.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Temporary participation should not become an automatic permanent contact record.
Example
Save a coworker to My Roster after reviewing the contact information you may retain.
Connects to
- Person may retain a reviewed Roster relationship
- Roster relationship supports future work in Production
Implementation notes
Personal Roster records and Production People remain distinct.
Public evidence: Websites publish selected projections of canonical contexts.
Related workflows
Related decisions
See the system-wide decisions.
Technical details
Personal Roster records and Production People remain distinct.
Conceptual explanation; private implementation details are omitted.
Domain
Production
The operational context in which people coordinate production work.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Identity alone cannot describe who belongs to a specific production and what happens there.
Example
A production organizes crew, work, days, resources and communication.
Connects to
- Membership belongs to Production
- Production includes participation Membership
- Production organizes work in Group
- Production owns operational Day
- Roster relationship supports future work in Production
- Production owns Resource
- Production scopes Message
- Production has public projection Website
- Space includes the concept of Production
Implementation notes
Canonical Production direction retains existing compatible application records.
Related workflows
- Add a person to Production
- Issue a call sheet
- Check in on set
- Save a Production coworker to Personal Roster
- Publish a website
Related decisions
Technical details
Canonical Production direction retains existing compatible application records.
Conceptual explanation; private implementation details are omitted.
Domain
Production Membership
A person’s participation in one production.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Belonging to a production and performing a particular job have different lifecycles.
Example
A crew member stays in the production while a camera assignment changes.
Connects to
- Person participates through Membership
- Membership belongs to Production
- Production includes participation Membership
- Membership identifies Person
- Membership performs work through Assignment
- Assignment retains participation Membership
- Staffing leads to participation through Membership
Implementation notes
Membership is stable participation; source-backed preparation is not an application release claim.
Public evidence: Production membership and work assignments are separate records.
Related workflows
- Add a person to Production
- Book a crew member
- Assign a crew member to a group
- Replace an assignment
- Save a Production coworker to Personal Roster
Related decisions
Technical details
Membership is stable participation; source-backed preparation is not an application release claim.
Conceptual explanation; private implementation details are omitted.
Domain
Production Assignment
A descriptive record of the work a production member performs.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
A person can perform several jobs without duplicating identity or membership.
Example
One member has a camera assignment and a later second-unit assignment.
Connects to
- Membership performs work through Assignment
- Assignment retains participation Membership
- Assignment describes work as Role
- Assignment classifies work in Department
- Assignment belongs to / leads Group
- Assignment is called for work on Day
- Resource has work context Assignment
- Assignment contributes work to Today
Implementation notes
Work assignments may describe role, department, groups, dates and reporting relationships.
Public evidence: Production membership and work assignments are separate records.
Related workflows
Related decisions
Technical details
Reports-to, shadowing and replacement describe relationships between assignments within one Production. They preserve participation and history and do not grant software authority.
Conceptual explanation; private implementation details are omitted.
Domain
Production Group
Flexible operational organization inside a production.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Units, departments and working teams should not require separate group architectures.
Example
A Unit and a lighting working group organize assignments.
Connects to
- Assignment belongs to / leads Group
- Production organizes work in Group
- Group can select eligible people for Audience
- Group provides context for Resource
Implementation notes
Parent groups, leadership and group membership do not automatically confer authority.
Public evidence: Production membership and work assignments are separate records.
Related workflows
Related decisions
Technical details
Parent groups, leadership and group membership do not automatically confer authority.
Conceptual explanation; private implementation details are omitted.
Domain
Role
A human-readable description of production work.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
A job title should communicate work without silently granting software access.
Example
A gaffer leads lighting work; a casting director finds performers; an actor performs a part. Each still needs explicit permission to edit or approve.
Connects to
- Assignment describes work as Role
Implementation notes
Role labels and permissions remain independent.
Public evidence: Production membership and work assignments are separate records.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
Role labels and permissions remain independent.
Conceptual explanation; private implementation details are omitted.
Domain
Production Day
An operational work day inside a production.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
A calendar event alone does not define a production’s calls, publication and attendance.
Example
Tomorrow’s production day ties a schedule to people, assignments and an issued call sheet.
Connects to
- Assignment is called for work on Day
- Production owns operational Day
- Day plans work through Schedule
- Day publishes Call Sheet
- Day records Presence
- Resource has operational context Day
Implementation notes
Meetings and holds do not automatically become Production Days.
Public evidence: Production Days connect schedules, issued call sheets and presence.
Related workflows
Related decisions
Technical details
Meetings and holds do not automatically become Production Days.
Conceptual explanation; private implementation details are omitted.
Domain
Schedule
The planned sequence and timing of work.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Planning must remain distinguishable from publication and actual attendance.
Example
A day’s schedule orders scenes, calls and locations.
Connects to
- Day plans work through Schedule
- Schedule is frozen into Call Sheet
- Schedule contributes planned time to Today
Implementation notes
Date-only periods and time-zone-aware instants are different concepts.
Public evidence: Production Days connect schedules, issued call sheets and presence.
Related workflows
Related decisions
See the system-wide decisions.
Technical details
Date-only periods and time-zone-aware instants are different concepts.
Conceptual explanation; private implementation details are omitted.
Projection
Call Sheet
An issued operational projection of a production day.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
People need a stable version of the plan they were actually called against.
Example
An issued sheet freezes the reviewed schedule and recipient context.
Connects to
- Schedule is frozen into Call Sheet
- Day publishes Call Sheet
- Call Sheet targets eligible recipients through Audience
- Call Sheet receives version-specific Acknowledgement
- Call Sheet projects recipient obligations into Attention
Implementation notes
Publication, delivery, viewing and acknowledgement have separate meanings.
Public evidence: Production Days connect schedules, issued call sheets and presence.
Related workflows
Related decisions
See the system-wide decisions.
Technical details
Publication, delivery, viewing and acknowledgement have separate meanings.
Conceptual explanation; private implementation details are omitted.
Domain
Acknowledgement
A recipient’s response to an issued call-sheet version.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Opening a page or admitting delivery does not establish a crew member’s acknowledgement.
Example
A member acknowledges the exact issued call sheet.
Connects to
- Call Sheet receives version-specific Acknowledgement
- Acknowledgement is distinct from recorded Presence
Implementation notes
Acknowledgement is version-specific and distinct from arrival.
Public evidence: Production Days connect schedules, issued call sheets and presence.
Related workflows
Related decisions
See the system-wide decisions.
Technical details
Acknowledgement is version-specific and distinct from arrival.
Conceptual explanation; private implementation details are omitted.
Domain
Presence
Recorded participation and arrival state on a production day.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Planned work and actual on-set participation should never be inferred from each other.
Example
Called, acknowledged, checked in, late, absent, wrapped and replaced are conceptual distinctions.
Connects to
- Acknowledgement is distinct from recorded Presence
- Day records Presence
Implementation notes
State vocabulary illustrates operations; it is not a published internal enum or complete state machine.
Public evidence: Production Days connect schedules, issued call sheets and presence.
Related workflows
Related decisions
See the system-wide decisions.
Technical details
State vocabulary illustrates operations; it is not a published internal enum or complete state machine.
Conceptual explanation; private implementation details are omitted.
Domain
Production Resource
A creative or operational artifact with production context.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Assets should share version and review mechanisms rather than separate approval silos.
Example
A storyboard, wardrobe look or VFX version connects to people, scenes, shots and days.
Connects to
- Resource has a separately selected Final reference
- Production owns Resource
- Resource has immutable Resource Version
- Permission / Capability controls current access to Resource
- Resource has person context Person
- Resource has work context Assignment
- Resource has narrative context Scene
- Resource has shot context Shot
- Resource has operational context Day
- Group provides context for Resource
Implementation notes
Resources are implemented locally; hosted acceptance and production release remain pending.
Public evidence: Resources have immutable versions and exact-version review.
Related workflows
Related decisions
Technical details
Resources are implemented locally; hosted acceptance and production release remain pending.
Conceptual explanation; private implementation details are omitted.
Domain
Resource Version
An immutable snapshot of a resource’s submitted content.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Approval is meaningful only when it identifies what was reviewed.
Example
A new storyboard upload starts a new review without inheriting old approvals.
Connects to
Implementation notes
Current, approved and final versions are separate pointers.
Public evidence: Resources have immutable versions and exact-version review.
Related workflows
Related decisions
Technical details
Current, approved and final versions are separate pointers.
Conceptual explanation; private implementation details are omitted.
Service
Workflow
The review and transition lifecycle of a specific subject.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Financial documents, creative assets and call-sheet review need common transition and audit mechanics.
Example
A resource version moves through configured review stages.
Connects to
- Resource Version is reviewed through Workflow
- Workflow Definition configures a submitted Workflow
- Workflow orders Workflow Stage
- Workflow projects current obligations into Attention
Implementation notes
The common engine has subject adapters; coverage is stated per integration.
Public evidence: Supported domains use shared workflow transitions and audit mechanics.
Related workflows
Related decisions
Technical details
The common engine has subject adapters; coverage is stated per integration.
Conceptual explanation; private implementation details are omitted.
Domain
Workflow Stage
An ordered part of a submitted review process.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Sequential review responsibilities need explicit state rather than ambiguous flags.
Example
A VFX stage precedes a client review stage.
Connects to
- Workflow orders Workflow Stage
- Workflow Stage requests eligible Review
- Workflow Stage selects reviewers through Audience
Implementation notes
ANY means one eligible approval; ALL means every required reviewer approves.
Public evidence: Supported domains use shared workflow transitions and audit mechanics.
Related workflows
Related decisions
Technical details
ANY means one eligible approval; ALL means every required reviewer approves.
Conceptual explanation; private implementation details are omitted.
Domain
Review
Evaluation of an exact submitted version by eligible reviewers.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
A familiar job title does not establish that someone can inspect or decide on this subject.
Example
A reviewer opens the submitted storyboard version and records feedback.
Connects to
- Workflow Stage requests eligible Review
- Review records a version-specific Approval
- Permission / Capability authorizes eligible Review
- Review may create corrections as Task
Implementation notes
Reviewer audience and current authority are distinct checks.
Public evidence: Supported domains use shared workflow transitions and audit mechanics.
Related workflows
Related decisions
See the system-wide decisions.
Technical details
Reviewer audience and current authority are distinct checks.
Conceptual explanation; private implementation details are omitted.
Domain
Approval
A recorded decision concerning the reviewed subject and version.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Approval cannot float independently of content identity and process state.
Example
An approved storyboard version remains historical after a later upload.
Connects to
- Approval supports explicit selection of Final reference
- Review records a version-specific Approval
- Approval produces transition history in Audit Event
Implementation notes
Approval is not finalization; a final reference is selected explicitly.
Public evidence: Supported domains use shared workflow transitions and audit mechanics.
Related workflows
Related decisions
See the system-wide decisions.
Technical details
Approval is not finalization; a final reference is selected explicitly.
Conceptual explanation; private implementation details are omitted.
Primitive
Audience
A selector describing intended recipients or reviewers.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Targeting the right people is different from granting access to their data.
Example
Send an update to eligible assignments in A Unit called today.
Connects to
- Group can select eligible people for Audience
- Call Sheet targets eligible recipients through Audience
- Workflow Stage selects reviewers through Audience
- Audience targets Update
Implementation notes
Audience membership never grants resource access.
Public evidence: Role and audience selection are separate from scoped authority.
Related workflows
Related decisions
Technical details
Audience membership never grants resource access.
Conceptual explanation; private implementation details are omitted.
Service
Permission / Capability
Explicit authority to perform an action in a scope.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Software authority must be evaluated independently of job labels and UI presentation.
Example
A person may view a resource without having permission to approve it.
Connects to
- Permission / Capability authorizes eligible Review
- Permission / Capability controls current access to Resource
- Firebase Auth precedes evaluation of Permission / Capability
- Permission / Capability admits scoped commands to Domain Service
Implementation notes
Authentication establishes identity; authorization evaluates current scoped authority.
Public evidence: Role and audience selection are separate from scoped authority.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
Authentication establishes identity; authorization evaluates current scoped authority.
Conceptual explanation; private implementation details are omitted.
Domain
Update
A production announcement targeted at an eligible audience.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
One operational message should reach the right current recipients without broad data exposure.
Example
Publish an update for everyone called on a production day.
Connects to
- Audience targets Update
- Update admits delivery intent to Functions / Jobs
Implementation notes
Delivery admission and successful provider delivery are separate states.
Public evidence: Today composes authorized source work rather than owning it.
Related workflows
Related decisions
See the system-wide decisions.
Technical details
Delivery admission and successful provider delivery are separate states.
Conceptual explanation; private implementation details are omitted.
Projection
Attention
A projection of currently actionable source obligations.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
A notification history is not a reliable ledger of unfinished work.
Example
A pending acknowledgement or review appears as attention while still eligible.
Connects to
- Message may create eligible Attention
- Workflow projects current obligations into Attention
- Call Sheet projects recipient obligations into Attention
- Attention contributes actionable work to Today
Implementation notes
Source records own completion; projection coverage can be partial.
Public evidence: Today composes authorized source work rather than owning it.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
Source records own completion; projection coverage can be partial.
Conceptual explanation; private implementation details are omitted.
Projection
Today
An authorized read model composing work across contexts.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
People need one understandable view of their work without creating another source of truth.
Example
Today combines upcoming calls, assignments, activity and attention.
Connects to
- Attention contributes actionable work to Today
- Assignment contributes work to Today
- Schedule contributes planned time to Today
- Availability contributes eligible requests to Today
- Firestore supplies authorized source records for Today
Implementation notes
Today does not own canonical work, complete actions, or grant permission.
Public evidence: Today composes authorized source work rather than owning it.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
Today does not own canonical work, complete actions, or grant permission.
Conceptual explanation; private implementation details are omitted.
Projection
Website
A configured public projection of an eligible canonical context.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Publishing should reuse identity and content without exposing private application records.
Example
A production website presents approved public information.
Connects to
- Production has public projection Website
- Profile has public projection Website
- Team has public projection Website
- Organization has public projection Website
- Networking Community has public projection Website
- Website is configured for Publication
Implementation notes
Public projection, configuration and publication have distinct responsibilities.
Public evidence: Websites publish selected projections of canonical contexts.
Related workflows
Related decisions
Technical details
Public projection, configuration and publication have distinct responsibilities.
Conceptual explanation; private implementation details are omitted.
Service
Publication
The deliberate selection and release of public presentation.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Public visibility must be an explicit boundary rather than a side effect of membership.
Example
Publish a reviewed website configuration to a public domain.
Connects to
- Website is configured for Publication
- Publication is delivered through Cloudflare Edge
Implementation notes
The public presentation differs from canonical private records.
Public evidence: Websites publish selected projections of canonical contexts.
Related workflows
Related decisions
Technical details
The public presentation differs from canonical private records.
Conceptual explanation; private implementation details are omitted.
Client
Web Client
The React and Next.js product experience.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
The operational application needs interaction and authenticated domain access.
Example
The web crew directory and production workspaces share server contracts.
Connects to
- Web Client requests application access through Cloudflare Edge
- Desktop Client hosts the experience of Web Client
- Web Client calls explicit API Transport
Implementation notes
This engineering site is a separate static project and does not use the application runtime.
Public evidence: Clients share domain contracts while retaining distinct interfaces.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
This engineering site is a separate static project and does not use the application runtime.
Conceptual explanation; private implementation details are omitted.
Infrastructure
Cloudflare Edge
The edge and control plane surrounding application workloads.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Ingress, static delivery and coordination have different responsibilities from canonical domain data.
Example
The edge delivers assets and forwards admitted application requests.
Connects to
- Publication is delivered through Cloudflare Edge
- Web Client requests application access through Cloudflare Edge
- iOS Client requests application access through Cloudflare Edge
- MCP Client accesses public APIs through Cloudflare Edge
- Cloudflare Edge forwards admitted requests to Next.js Origin
Implementation notes
Public disclosure is limited to provider roles, not private gateways or recovery mechanisms.
Public evidence: Cloudflare edge and Google Cloud application workloads have separate roles.
Related workflows
Related decisions
Technical details
Public disclosure is limited to provider roles, not private gateways or recovery mechanisms.
Conceptual explanation; private implementation details are omitted.
Infrastructure
Next.js Origin
The Node-capable web runtime hosted on Google Cloud Run.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Server-side application and provider workloads need a suitable runtime behind the edge.
Example
The origin executes authorized domain commands and queries.
Connects to
- Cloudflare Edge forwards admitted requests to Next.js Origin
- Next.js Origin runs Domain Service
Implementation notes
Cloudflare owns ingress; Google Cloud Run hosts the Next.js runtime.
Public evidence: Cloudflare edge and Google Cloud application workloads have separate roles.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
Cloudflare owns ingress; Google Cloud Run hosts the Next.js runtime.
Conceptual explanation; private implementation details are omitted.
Service
Domain Service
Server-owned commands and queries for a bounded domain.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
UI state should not decide privileged transitions or storage authority.
Example
A production command validates context before committing work.
Connects to
- Domain Service returns an authorized Response projection
- Next.js Origin runs Domain Service
- Domain Service persists canonical records in Firestore
- Domain Service accesses admitted files in Storage
- Domain Service checks identity using Firebase Auth
- Domain Service admits background work to Functions / Jobs
- Domain Service uses scoped adapters for External Provider
- Permission / Capability admits scoped commands to Domain Service
Implementation notes
Commands own transitions; queries return bounded authorized projections.
Public evidence: Cloudflare edge and Google Cloud application workloads have separate roles.
Related workflows
No curated journey in this edition.
Related decisions
See the system-wide decisions.
Technical details
Commands own transitions; queries return bounded authorized projections.
Conceptual explanation; private implementation details are omitted.
Provider
Firebase Auth
The application identity provider.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Identity verification needs a dedicated provider, separate from domain permission decisions.
Example
Sign-in identifies a user before production access is evaluated.
Connects to
- Domain Service checks identity using Firebase Auth
- Request Boundary establishes identity through Firebase Auth
- Firebase Auth precedes evaluation of Permission / Capability
Implementation notes
Authentication is not authorization.
Public evidence: Cloudflare edge and Google Cloud application workloads have separate roles.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
Authentication is not authorization.
Conceptual explanation; private implementation details are omitted.
Provider
Firestore
Canonical application records and scoped persistence.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Durable records need transactional ownership rather than being reconstructed from the UI.
Example
Membership and production work records retain their own owners.
Connects to
- Firestore supplies scoped source data for Response projection
- Domain Service persists canonical records in Firestore
- Firestore supplies authorized source records for Today
Implementation notes
Public diagrams do not expose collection inventories or production identifiers.
Public evidence: Cloudflare edge and Google Cloud application workloads have separate roles.
Related workflows
No curated journey in this edition.
Related decisions
Technical details
Public diagrams do not expose collection inventories or production identifiers.
Conceptual explanation; private implementation details are omitted.
Domain
Final reference
The explicitly selected final version of a production resource.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Approved, current and final versions answer different questions.
Example
A later upload does not replace the previously selected final storyboard version.
Connects to
- Approval supports explicit selection of Final reference
- Resource has a separately selected Final reference
Implementation notes
Finalization is explicit and requires the relevant approved version; it is not upload success.
Related workflows
No curated journey in this edition.
Related decisions
See the system-wide decisions.
Technical details
Finalization is explicit and requires the relevant approved version; it is not upload success.
Conceptual explanation; private implementation details are omitted.
Projection
Response projection
The minimum authorized output returned by a domain query or command.
CanonicalImplemented locally
See this concept connect visually →
Why it exists
Clients need useful presentation data without receiving private canonical records wholesale.
Example
A response describes the permitted work fields for the current actor.
Connects to
- Firestore supplies scoped source data for Response projection
- Domain Service returns an authorized Response projection
Implementation notes
A response projection does not become permission truth or replace canonical source ownership.
Related workflows
No curated journey in this edition.
Related decisions
See the system-wide decisions.
Technical details
A response projection does not become permission truth or replace canonical source ownership.
Conceptual explanation; private implementation details are omitted.