28. Lifecycle transactions, maintenance scheduling, and accountable work

A maintenance note is not a lifecycle transaction. Every task has a definition, applicability decision, planned work package, execution, findings, material movements, measurements, release decision and resulting configuration or condition state. Care, wash, repair, modification, restoration, software deployment and decommissioning reuse this transaction spine while retaining their distinct intent and authority requirements.

#28.1 Work package state machine

#28.2 Maintenance requirement and due engine

Maintenance requirement and due projection
MaintenanceRequirement {
  requirementId, revision, authority, taskDefinitionRef,
  applicabilityExpression, initialThresholds[], repeatIntervals[],
  intervalBasis: calendar | distance | cycles | hours | launches |
                 landings | pressureEvents | energyThroughput |
                 componentMeter | condition | event,
  tolerance, escalationPolicy, terminationCondition,
  supersessionPolicy, complianceEvidenceRequirements[]
}

DueProjection = evaluate(requirement, target, configuration,
                         meterLineage, eventHistory, condition,
                         deferrals, knownAt, evaluatorVersion)

• Meters are independent typed histories. Replacing an odometer, battery, controller or component never resets prior readings.
• A requirement may use several thresholds; the earliest applicable due boundary controls unless the rule explicitly combines them.
• Missing meter history produces unknown or a conservative declared rule, never a silently estimated exact value.
• Deferral is an authorized record with basis, limits, compensating actions, expiry and follow-up; it is not an edited due date.
• A superseded task remains resolvable for work performed under its revision; projections explain which revision now applies.

#28.3 Execution step contract

#28.4 Finding, defect, damage, failure, and cause graph

Observed condition, requirement violation, functional failure, damage event and causal hypothesis are different records. A root-cause analysis may be revised without changing the original crack photograph, power-loss event or test result. Repair records link what was addressed; they do not erase the finding.

#28.5 Cost, inventory, sustainability, and warranty ledgers

No accounting by note parsing
Money, inventory, warranty recovery and environmental claims are typed records with exact quantities and parties. A mechanic's narrative may explain them but cannot substitute for a balanced transaction or source document.