Filmclusive
Identity
One identity can participate in many Productions and have different presentations and relationships.
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 has presentation Profile.
- Person participates through Membership.
- Membership belongs to Production.
- Person may retain a reviewed Roster relationship.
Person ≠ Profile ≠ Production Membership ≠ Team Membership ≠ Roster Relationship.
Person versus Profile
Person is the persistent identity. Profile is a professional or public presentation of that identity. Changing a biography does not create a new Person.
Before an account is claimed
A Production may know about a Person before that Person has claimed a full Filmclusive account or profile. Knowing the Person exists is separate from sign-in, account control and consent.
Different relationships, different lifecycles
Production Membership records participation in temporary work. Team Membership records participation in a persistent shared context. A Roster Relationship retains a personal professional connection. None replaces 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.
Projection
Profile
An editable presentation of a person.
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.
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.
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.