Filmclusive
Audiences
An Audience identifies intended recipients. It never grants access to unrelated resources.
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
- Group can select eligible people for Audience.
- Permission / Capability authorizes eligible Review.
- Permission / Capability controls current access to Resource.
- Audience targets Update.
Audience ≠ Authorization. Role ≠ Permission.
Who is this intended for?
Audiences can describe fixed people, work context or current operational state.
- Everyone
- Specific People
- Assignments
- Roles
- Groups
- Group Leads
- Departments
- Department Leads
- Called Today
- Called Tomorrow
- On Set Now
- Not Checked In
- Not Acknowledged
Who may act?
Software capabilities and resource access are evaluated independently. A Camera update does not grant payroll access. A Client review invitation does not open internal crew conversations.
Targeting also needs authority
The ability to select a broad audience is itself scoped. Membership alone is not permission to distribute private material to everyone. Dynamic audiences describe state at the relevant point in the workflow.
Go deeper
Conceptual architecture. Implementation and release status are assessed separately.
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
Production Resource
A creative or operational artifact with production context.
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
Review
Evaluation of an exact submitted version by eligible reviewers.
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.
Primitive
Audience
A selector describing intended recipients or reviewers.
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.
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.
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.