Phase 6: Implement alert episode accounting #456

Open
opened 2026-10-20 15:05:05 +02:00 by erikinkinen · 0 comments
Owner

Plan ID: P6-10
Record type: Implementation leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 10.5, 10.6; common contracts in sections 3–5, 11 and 17.4.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 8281.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.

Goal

distinguish timely warning from sustained false or late alarms.

Prerequisites

Steps

  • Implement two-high start, two-low termination and unbackdated start times.
  • Match episodes to first onset using the exact horizon and guard interval.
  • Compute false episodes, alert duration, lead time and unwarned-event counts.

Definition of Done

repeated threshold crossings cannot inflate recall and an alert
inside the guard band is never credited as early warning.

Execution and acceptance contract

Apply the governing semantic/data/statistical contracts in sections 3–5 and the relevant phase section, plus the section-11 checks applicable to this task. Section 17.4 defines the required acceptance evidence. Store the outcome and immutable prerequisite/input/output hashes at

artifacts/backlog/2.2.1/P6-10/acceptance.json.

Only explicit dependency and parent-closure edges govern readiness; numbering adds no predecessor dependency. Checkboxes are work/acceptance items, not commit quotas. Keep implementation changes independently reviewable using the existing PR template. Execution, review and gate tasks close with their evidence/decision records and a PR only when tracked artifacts change.

An unsupported scientific effect is a valid result. Missing correctness validation, invalid inference or absent required review is not completion. Do not change endpoints, matrices, margins, inference rules or sample sizes outside the protocol change-control process.

<!-- aes-plan-id: P6-10; backlog-revision: 2.2.1 --> **Plan ID:** `P6-10` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 10.5, 10.6; common contracts in sections 3–5, 11 and 17.4. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 8281. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal distinguish timely warning from sustained false or late alarms. ## Prerequisites - [P5-32 (#427)](https://git.erikinkinen.fi/erikinkinen/AES/issues/427) - [P6-04 (#442)](https://git.erikinkinen.fi/erikinkinen/AES/issues/442) ## Steps - [ ] Implement two-high start, two-low termination and unbackdated start times. - [ ] Match episodes to first onset using the exact horizon and guard interval. - [ ] Compute false episodes, alert duration, lead time and unwarned-event counts. ## Definition of Done repeated threshold crossings cannot inflate recall and an alert inside the guard band is never credited as early warning. ## Execution and acceptance contract Apply the governing semantic/data/statistical contracts in sections 3–5 and the relevant phase section, plus the section-11 checks applicable to this task. Section 17.4 defines the required acceptance evidence. Store the outcome and immutable prerequisite/input/output hashes at `artifacts/backlog/2.2.1/P6-10/acceptance.json`. Only explicit dependency and parent-closure edges govern readiness; numbering adds no predecessor dependency. Checkboxes are work/acceptance items, not commit quotas. Keep implementation changes independently reviewable using the existing PR template. Execution, review and gate tasks close with their evidence/decision records and a PR only when tracked artifacts change. An unsupported scientific effect is a valid result. Missing correctness validation, invalid inference or absent required review is not completion. Do not change endpoints, matrices, margins, inference rules or sample sizes outside the protocol change-control process.
erikinkinen added this to the Phase 6 milestone 2026-10-20 15:05:05 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
erikinkinen/AES#456
No description provided.