Skip to content

Latest commit

 

History

History
26 lines (17 loc) · 3.43 KB

METRICS.md

File metadata and controls

26 lines (17 loc) · 3.43 KB

Metric contract

All data in this project is synthetic. Every report binds timezone-aware UTC timestamps. For a cutoff T, a snapshot includes entities and events strictly before T. Flow windows are [window_start, cutoff). Weekly cutoffs are Monday 00:00 UTC and show the state immediately before that moment.

State model

A finding is one tracked issue on one asset. An event is a complete state snapshot, including status, severity, owner, and due date. Latest state is selected by (occurred_at DESC, event_id DESC) after filtering events before the cutoff. A task follows the same rule. A NULL owner or deadline means missing; it does not inherit an older value.

open and in_progress are actionable. resolved is technical remediation in this synthetic model. false_positive and not_applicable are adjudications. accepted_risk is accepted exposure, shown separately from actionable backlog and never counted as a fix. An actionable episode begins at first actionable state or reopening and ends on a transition to a terminal state.

Team attribution uses the owner on the relevant historical event. Team names and asset identities are stable in the MVP. A NULL owner is reported as Unowned. A finding stays in backlog even if its asset would later be retired; retirement is not modeled.

Reports

Key Grain Definition
R1 backlog Team/severity bucket Count latest actionable findings and accepted risks separately. Show every eligible team and Unowned at all four severities, including zeros.
R2 exceptions Actionable finding Return one row if overdue (due_at < cutoff), unowned, or missing due date. An equal deadline is not overdue. Age is elapsed days since detection.
R3 weekly backlog Week/team bucket and labeled total Reconstruct each cutoff independently. Change is current count minus prior requested week's count; first change is NULL.
R4 remediation time Completed actionable episode, summarized by closure team and overall Count only actionable → resolved transitions in the window. Duration is exact elapsed seconds / 86400. p50 and p90 use percentile_cont. On-time means closure time <= due date at closure; percentage denominator is closures with known deadlines. Empty percentiles and percentages are NULL.
R5 backlog flows Team/movement and global reconciliation Count initial actionable findings as new, terminal → actionable as reopened, and actionable → terminal by distinct outcome. Global ending backlog equals beginning + new + reopened − each closure category. Per-team conservation is not claimed because transfers are not modeled as flows.
R6 rollout progress Rollout and weighted portfolio total Eligible tasks are current pending, in progress, blocked, or done; canceled tasks are excluded. Completion is 100 * done / eligible, NULL when eligible is zero. Overdue and missing-field exceptions apply only to incomplete eligible tasks.

Interpretation limits

These are effective event-time snapshots of the data currently loaded. They cannot reconstruct what an analyst knew on an earlier date if a backdated event arrived later. Team names are immutable; finding-to-asset associations do not change; history is never deleted. Risk acceptance approvals and expirations are outside this model. Completion percentiles describe completed episodes, not expected time to resolve the open backlog. The synthetic deadlines are lab assumptions, not a production policy.