5. Time as an operational primitive

Walk through the visual explanation →

Several facts about time

Availability answers whether a person can work during a proposed period. Conditional responses and alternatives can inform planning without becoming a commitment. Staffing turns that evidence into intended work through its own lifecycle.

Assignments describe the job and a broad work period. A Production Day describes an operational day. Schedule describes the sequence and timing of planned work. Call Sheet describes an issued projection of that plan. These facts are connected, but they cannot safely be collapsed into one calendar event.

Publication is versioned

An issued call sheet needs to identify the content and context the recipient actually received. Revising the plan creates a new publication question rather than changing the meaning of an old acknowledgement. Review of a draft and publication of the issued version remain distinct actions.

Queueing a delivery does not prove that a provider delivered it. Delivery does not prove that a person viewed it. Viewing does not prove acknowledgement, and acknowledgement does not prove arrival. A useful operational system needs these distinctions even when the interface keeps the presentation compact.

Presence records actuality

Presence describes operational participation. Called, acknowledged, checked in, late, absent, wrapped and replaced are conceptual distinctions used here to explain the domain. This list is not a published internal enum or complete transition table.

An ordinary meeting or hold should not automatically create an operational production day. Conversely, a day can relate multiple assignments, schedule items and recipients rather than being reduced to one person’s calendar entry.

Calendar semantics

Date-only work periods and time-zone-aware instants have different meaning. A calendar day should not shift because a viewer is in another timezone. Scheduled instants should retain their intended context. Display conventions belong at the human-facing boundary.

The model introduces more records and publication state than a simple calendar. It supports the practical question the production needs answered: what was planned, what was issued, who acknowledged it, and what actually happened?