Filmclusive
Production
Membership connects a Person to a Production. Assignments describe the work; Groups organize it.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
Drag a card to rearrange it. Select it to learn more.
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.
Membership means “this person belongs to this Production.” It does not describe their exact job, software authority or permanent professional relationship.
One member, multiple Assignments
An Assignment describes production work, independently of to-do tasks. One Membership may have multiple Assignments.
- Role
- Department
- Groups
- Dates
- Status
- Leadership
- Reports To
- Shadows
- Replaces
Groups are flexible
An Assignment may belong to multiple Groups. Units and working groups overlap; they cannot be represented by one rigid hierarchy.
- A Unit
- B Unit
- Camera
- BTS
- Security
- Client
- Marketing
- Producers
- Stunts
- Vendors
Mas’s work in one Production
Role: BTS Photographer. Department: Photography. Groups: BTS, Marketing and A Unit. One Person and one Membership support all of that work context.
Role ≠ Permission
Being a Producer does not automatically mean software administrator. Being DP does not grant payroll visibility. Being a PA may allow operational contact without private financial access. Filmclusive evaluates software authority separately from descriptive work identity.
Go deeper
Conceptual architecture. Implementation and release status are assessed separately.
Primitive
Person
A persistent professional identity across changing work contexts.
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.
Domain
Production
The operational context in which people coordinate production work.
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.
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.
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.
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.
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.