Logical tier transaction

Milestone

opda:Milestone

Milestone

Summary

Transaction lifecycle milestone. [Event particular; UFO Event particular / DOLCE Achievement (instant) or Accomplishment (interval) / PROV-O Activity]. Hybrid PROV-O typing per S007 Q2: instant milestones (instruction, offerAccepted, exchange) carry prov:atTime; interval milestones (completion-process, registration-process) carry prov:startedAtTime + prov:endedAtTime per Moreau W3C-grade discipline. Each Milestone Activity may pair with a prov:Plan carrying plannedAtTime for expected-vs-actual variance. Concept tier →

Attributes

Attribute	Type	Cardinality	Required	Identity-bearing	Description
`occurredAtTime`	`dateTime`	`0..1`	N	N	Actual completion instant (informational alias for `prov:atTime` on instant milestones)
`plannedAtTime`	`dateTime`	`0..1`	N	N	Expected completion timestamp; carried on the `prov:Plan` companion via the PROV-O qualified-form chain — declared on Milestone domain at this tier for ER simplicity

Relationships

This entity declares no module-local object properties. Inbound predicates: Transaction.hasMilestone. The plan-vs-activity link uses the inherited PROV-O predicates prov:qualifiedAssociation → prov:Association → prov:hadPlan.

Identity key

Identity key = (Transaction, MilestoneKind) tuple — each transaction has at most one of each milestone Kind at a given lifecycle point. The surface IC element is plannedAtTime (when present). Cross-reference: Concept-tier Milestone narrative.

Constraints

plannedAtTime MUST be a single dateTime value when present (Violation, MilestoneIdentityKeyShape)

Derived attributes

Attribute	Derived from	Rule summary	Severity
`hasVarianceStatus`	`occurredAtTime` − `plannedAtTime`	`info-flagged` when slip < 14 days; `warning-flagged` otherwise (dynamic-severity surface; the rule itself stays `Info`)	`Info`
`hasVarianceDays`	`occurredAtTime` − `plannedAtTime`	Integer-day slip between planned and actual	`Info`

ER diagram

%%{init: {"theme": "base", "themeVariables": {"primaryColor": "#E1BEE7", "primaryTextColor": "#4A148C", "primaryBorderColor": "#6A1B9A", "lineColor": "#37474F"}}}%% erDiagram accTitle: Milestone — Entity-Relationship Diagram accDescr: Direct-neighbour view of Milestone — inverse hasMilestone from Transaction with optional PROV-O qualifiedAssociation hadPlan companion. Transaction ||--o{ Milestone : "hasMilestone" Milestone }o--o| Plan : "qualifiedAssociation hadPlan"

Lifecycle state-transition diagram

Five canonical MilestoneKind events drive Transaction progression per ODR-0007 §Q2. Each milestone is a PROV-O Activity with hybrid instant/interval typing.

%%{init: {"theme": "base", "themeVariables": {"primaryColor": "#E1BEE7", "primaryTextColor": "#4A148C", "primaryBorderColor": "#6A1B9A", "lineColor": "#37474F"}}}%% stateDiagram-v2 accTitle: Milestone — Lifecycle State-Transition Diagram accDescr: Five canonical MilestoneKind values (instruction, offerAccepted, exchange, completion, registration) form a strict-ordering chain of PROV-O Activities driving Transaction lifecycle. [*] --> instruction : property instructed
(instant: prov:atTime) instruction --> offerAccepted : offer accepted
(instant: prov:atTime) offerAccepted --> exchange : contracts exchanged
(instant: prov:atTime) exchange --> completion : completion process
(interval: prov:startedAtTime
+ prov:endedAtTime) completion --> registration : registration process
(interval: prov:startedAtTime
+ prov:endedAtTime) registration --> [*]

Source ODR + ADR

ODR-0007 — Transaction lifecycle, §Q2 Milestone hybrid typing; §Q6 Plan-vs-Activity reification
ADR-0011 — Module TBox emission — implementation
ADR-0012 — SHACL + DPV annotation emission — MilestoneVarianceRule

Milestone

Milestone

Summary

Attributes

Relationships

Identity key

Constraints

Derived attributes

ER diagram

Lifecycle state-transition diagram

Source ODR + ADR

Comments