Identity
One identity can participate in many Productions and have different presentations and relationships.
Filmclusive
People persist. Context connects.
One professional identity connects to temporary productions, shared work, and lasting relationships.
Drag to move · Hover to trace. Select to read more. Keyboard: Alt + arrow keys to move.
One connected Production
Drag a card to rearrange it. Select it to learn more.
Connections in words
- Person participates through Membership.
- Membership belongs to Production.
- Production includes participation Membership.
- Membership identifies Person.
- Membership performs work through Assignment.
- Assignment retains participation Membership.
- Assignment belongs to / leads Group.
- Production organizes work in Group.
- Group can select eligible people for Audience.
- Assignment is called for work on Day.
- Production owns operational Day.
- Person may retain a reviewed Roster relationship.
- Roster relationship supports future work in Production.
- Production owns Resource.
- Resource has person context Person.
- Resource has work context Assignment.
- Resource has operational context Day.
- Group provides context for Resource.
- Production scopes Message.
- Assignment contributes work to Today.
- Production has public projection Website.
Ten primitives. Deliberate boundaries.
Open a primitive for its analogy, diagram and example.
PersonPersistent professional identity.
The professional who continues from job to job.
Person → Memberships → Productions
Mas participates in several Productions without becoming a different Person.
Inspect the concept →SpaceA collaboration context with its own rules.
The place a particular set of people work together.
Space → Context → Scoped participation
Production, Production Group, Team, Organization and Community can share interface patterns while retaining different authority, privacy and lifecycle rules.
Inspect the concept →MembershipWhy a Person belongs to a Production.
Being on this production’s crew list.
Person → Membership → Production
Mas belongs to the Production, independently of the jobs performed there.
Inspect the concept →AssignmentThe work a Production member performs.
The jobs beside a person’s name on the crew list.
Membership → Assignments → Work
One Membership can carry a BTS assignment and a second assignment with different dates.
Inspect the concept →GroupFlexible operational grouping.
A unit or working group that crosses department lines.
Assignment → BTS + Marketing + A Unit
A BTS assignment belongs to BTS, Marketing and A Unit at once.
Inspect the concept →Time / Production DayA canonical operational work day.
The shared day people are called to work.
Production Day → Call sheet + Presence
A day connects location, schedule, active groups, assignments and individual calls.
Inspect the concept →ResourceA creative or operational artifact in context.
A storyboard or wardrobe look tied to the work.
Resource → Version → Review
A storyboard connects scenes, shots, departments, people and reviewed versions.
Inspect the concept →WorkflowAn explicit process for moving work forward.
The agreed route from submission to a decision.
Submission → Review → Decision
Eligible reviewers decide on the exact submitted storyboard version.
Inspect the concept →AudienceWho something is intended for.
The distribution list for a particular update.
Context → Audience → Distribution
A location change targets the relevant people called tomorrow.
Inspect the concept →RelationshipA deliberate professional connection that persists.
Remembering a coworker and the work you shared.
Shared work → Deliberate connection → Roster
Save to My Roster while respecting the contact information the person permits.
Inspect the concept →This vocabulary explains the architecture. It does not imply ten universal stored entities or identical rules for every collaboration context.
Follow the connected context.
Production
Membership connects a Person to a Production. Assignments describe the work; Groups organize it.
Network
Shared Production context makes a professional relevant without erasing contact consent.
Resources
Resources connect scenes, shots, departments, people, versions and approvals.
Operations
A canonical operational work day coordinates calls, publication, acknowledgement and recorded presence.
Audiences
An Audience identifies intended recipients. It never grants access to unrelated resources.
Websites
A public website presents deliberately authored information from a canonical context.
Today
Today brings calls, assignments, schedules and eligible obligations together.
Context creates relevance. It does not erase consent.
Shared Production participation enables authorized discovery and permitted communication. Private contact information, software authority and permanent relationships require separate decisions.
Follow the professional relationship →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.
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
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
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.
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.
Domain
Message
A conversation contribution with participant and context boundaries.
CanonicalImplemented locally
Why it exists
Operational communication needs a persistent thread without making every observer a participant.
Example
Crew discuss tomorrow’s work in a scoped conversation.
Connects to
- Production scopes Message
- Message may create eligible Attention
Implementation notes
Private conversation visibility is distinct from optional activity following.
Public evidence: Today composes authorized source work rather than owning it.
Related workflows
No curated journey in this edition.
Related decisions
See the system-wide decisions.
Technical details
Private conversation visibility is distinct from optional activity following.
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.