Glossary | Sundial

Term	Meaning in Sundial
Baseline	Saved snapshot used as the starting endpoint of a Delta comparison.
Current / Now	Latest successfully processed current model; distinct from a saved checkpoint.
Delta	Difference between a baseline and current model or later saved snapshot.
Effort	Total declared work estimate, normalized to hours for presentation.
Spent	Recorded effort already performed; the task form aggregates its baseline and entries.
Remaining effort	Total effort minus spent effort, used for scheduling.
Forecast	Deterministic simulated delivery under declared assumptions.
Initiative / Release	Project-level grouping; history specifications use Release terminology.
Milestone	Standalone commitment date with no work or dependency of its own.
Deadline / Goal	Deliverable need-by date, shown as a reference or emphasized goal where applicable.
Reporting snapshot	Dated Project-and-Team checkpoint for Delta/history charts, distinct from native startup snapshots.
Reporting start	Date from which remaining work is simulated.
Draft	Project, Team, or planning inputs not yet committed with Apply or the relevant confirmation.
Default capacity	Daily available hours used on working days outside overrides.
Scheduled override	Inclusive period whose daily hours replace the default; calendars still apply.
Work tracker	Heatmap of simulated developer allocation, not a timesheet system.
What-if roster	Alternative team assembled without editing the reference Team.
Native container	The .sundial folder holding authoritative collaboration state and history.
Concurrent edit	Independent changes made by separate browser instances before receiving each other's work.
Conflict	Retained competing field values or edit/delete intentions requiring a decision.
Tombstone	Recoverable native record of a deleted task, retaining its identity and history.
Workflow state	Named, colored step in the project process, mapped to one simulation category.
Simulation category	Backlog, In progress, Blocked, or Done scheduling behavior behind a detailed state.
Canceled outcome	Terminal non-delivery retaining history, using no future capacity, and satisfying no dependencies.
Effective priority	Explicit priority, nearest explicit ancestor priority, or Normal by default.
Manual order	Preference among eligible unfinished leaves at the same effective priority.
Acceptance criteria	Markdown description of observable completion conditions; not an executable completion gate.
Sprint scope	Actionable work assigned to a sprint, independent of task status.
Sprint capacity	Remaining estimated sprint effort compared with calendar hours, without developer speed or outside-sprint work.
Issue key	Project prefix and allocated issue number, separate from native identity and hierarchy position.
Next states	Allowed outgoing workflow destinations; an empty list is terminal.
Comment	Append-only Markdown note with a stored UTC timestamp, persisted when the task draft is applied.
Sunburst over time	Up to two historical Sunbursts beside Current, using one angular effort scale.
Milestones Scope mode	Delivery date versus total estimated effort for each observation.