milestone (entity)
Generated from solutions/ontological/lib/model/entities/milestone/schema.ts.
Schema version: 1.
Description
Section titled “Description”A Milestone is a release-shaped grouping of work with a target date and success criteria. It is the unit by which related work is scoped, sequenced, and shipped together. A Milestone is a delivery vehicle: it gathers whatever the project needs to ship the slice — Capabilities and Tasks today, plus references to supporting Decisions, Standards, Principles, planning artifacts, raw notes, or any other entity the shipping work depends on. The reference set is open; the delivery semantics (target date, success criteria, completion) are what make it a Milestone.
A Milestone is not:
- A Goal (the desired outcome the Milestone delivers; lives in the planned Product layer).
- A parent Task (a task with children — “epic-ness” is derived from
parent_key, not a separate entity type, perD-ORMG-data-model). A parent Task assembles related tasks under one theme; a Milestone is a delivery vehicle with a target date and success criteria. The two cut different axes over the Task graph.
Properties
Section titled “Properties”| Field | Type | Required | Description |
|---|---|---|---|
type | string | yes | Dispatch tag for the validator framework. |
schema_version | string | Numeric string version of the per-type schema this instance conforms to. Compare numerically when ordering versions. Independent of any product version. The value 0 is a documented sentinel meaning ‘pre-SDLC-managed’ — audit treats it as intentional, not stale. Optional in frontmatter: never in any per-type required set (audit flags a MISSING stamp as drift, not the validator). | |
id | string | yes | Immutable identifier in canonical M-NNNN shape per D-0002-entity-identifier-shape: ‘M-’ + 4 chars [0-9A-Z] (base-36 numbering; legacy incrementing ids are grandfathered). A .N suffix denotes a sub-milestone inserted between top-levels (e.g. M-0001.1). Never renamed once assigned. |
status | string | Lifecycle stage. open/* states are active; closed/* are terminal. | |
title | string | yes | Human-readable headline. Frontmatter is canonical; the body opens with # <title> for readability. |
created | string | yes | ISO date the entity was first authored. |
last_reviewed | string | ISO date the entity was last reviewed. Optional: never in any per-type required set. | |
related | array | Cross-references. Entries are wikilinks — typically to other entities by id (slug optional per D-0002-entity-identifier-shape; the decimal sub-milestone form M-NNNN.N is admitted), but may also reference non-entity planning docs by their wikilink slug. | |
tags | array | Free-form labels. Required at the common level, defaulting to []. Per-type schemas may add a contains constraint (e.g. Principle requires exactly one principle/<category> tag). | |
need_human_review | boolean | Review-tracking flag. | |
version | string | Semver of the product release this milestone targets (and ships as). Milestones are product releases, so version IS roadmap order — ascending semver. Set by a human once known; absent means deferred/unpositioned (sorts last). Required when status is closed/done. Two milestones sharing a version is a defect flagged by project-check (see milestone definition Workflow invariants). Distinct from this schema’s own version. | |
target_date | string | Aspirational landing date. Not a deadline gate. | |
tasks | array | Member items. Each entry is a wikilink to a Task (T-NNNN per D-0002-entity-identifier-shape) or another entity by id. Slug is optional. | |
relevance_note | string | Short note on what shifted since the milestone was planned. | |
completion_note | string | What shipped (or why work stopped). Required for any closed/* status. |
status
Section titled “status”open/draftopen/plannedopen/activeclosed/doneclosed/partialclosed/supersededclosed/abandoned