Supporting records
Use adjacent operations entities without confusing them with the automated KPI path.
Triage incoming work
Intake preserves a submission and its evidence. After reviewing it, link Classified As (Milestone), Classified As (Task) or Classified As (Incident) and record the resolution plan. These are manual data-model steps; no workflow classifies intakes. An intake view on Metric or Observation is a filtered queue, not a row in Intake.
Document and change
Procedure holds repeatable instructions; Content holds supporting knowledge. Assignment Role pairs actors and roles with a subject. Record a proposed change as Change Decision; record actual delivery as Release with version and evidence. Incident can link a postmortem to Content or Change Decision. Nothing approves or deploys changes automatically.
Separate compliance duties
Compliance Definition is the catalog. Compliance Obligation states applicability to an organization. Task represents an occurrence of work, and Registration stores a resulting identifier or permit. These tables have real links to operations records but are not read or written by the three current KPI collection workflows. Their presence does not prove reminders, renewals or task generation are automated.