Work is the organizing unit
NOS does not require a project to begin with a complete organizational chart. It starts with a visible creative idea, lets the project discover what it needs, and gradually turns those needs into defined units of work. The Work Card is the human-facing unit of work; the Work Board provides a project-level view of those units and their relationships. The Work Card is not merely a to-do list entry: it identifies what a participant is being asked to deliver, how that result can be reviewed, and how the work relates to other work.
A project can be a film, animated series, game, book, song, piece of software, marketing campaign, or another collaborative undertaking. Work Cards provide a consistent coordination vocabulary without insisting that those mediums use identical creative software or production pipelines.
Work Card versus Commitment
A Work Card describes the proposed responsibility. A Commitment records the explicit agreement under which the work is authorized. This distinction is essential: discussing a card, showing interest in it, or participating in Discovery does not automatically make a Member a Collaborator or create an obligation.
A governing agreement may address scope, deliverables, timing, consideration, approval authority, acceptance conditions, confidentiality, ownership, revenue participation, exit, and disputes. The terms are chosen by the participants within applicable rules; NOS metrics do not set them. Once accepted, a Commitment establishes a durable reference for what the parties agreed.
Submissions, review, and revisions
Creative work often proceeds through iterations. A submission is not the same event as approval, and approval is not always the same thing as final delivery or a downstream release. NOS's work-system research separates these states so a project can remember which version was reviewed, what feedback was given, which decision was made, and what was ultimately accepted.
Work may depend on other work. For example, an animation Work Card might rely on approved character design or a validated rig. Tracking these relationships makes a production pipeline understandable without assuming all teams use the same authoring tools.
Acceptance carries meaning
Acceptance is consequential because it can establish validated contribution and may satisfy conditions defined by the agreement. It may inform future Creative Capital or other analytics, but it does not independently grant unspecified ownership, bonuses, or equity. Rights and payments follow the governing terms, not an AI judgment about the quality of someone's work.
Changes should be explicit. When scope or compensation changes, the relevant agreement must be amended or replaced through the agreed process. Old submissions, approvals, and terms remain part of the historical record rather than silently disappearing.
What this means for an Owner or Collaborator
For an Owner, Work Cards make needs visible before team obligations are created, and they support scoped delegation as production grows. For a Collaborator, they make expectations and acceptance conditions legible before work begins. For a producer, they connect schedules and dependencies to evidence of what actually happened.
Current versus planned: The current Alpha focuses on Work Cards, Commitments, collaboration, review, acceptance, and project history. The more elaborate dependency, cryptographic artifact-lineage, and fully automated economic features described in some engineering drafts are design directions, not a claim that every control is already in Alpha.
Further reading: Lifecycle, Participation, Event Spine, and Product Documentation.