Phase 6: Qualify forecasting timing and operational precision #509

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

Plan ID: P6-27
Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 5.3, 10.9.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 8947.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.

Goal

Verify that the pipeline can distinguish advance information, transfer and useful reaction time.

Retained requirements

  • P6-27.R1: Add the late-feature, prior-transient, guard-window, audit-isolation and matched-schedule fixtures from section 10.9.
  • P6-27.R2: Implement all-source pilot reports for event/eligibility counts, denominator bounds, false-alarm precision, warmup misses and mapped response latency.
  • P6-27.R3: Freeze the barrier-latency reference and inference recipe; finalize qualification fields and failure wording without changing models, sources or primary margins.

Child issues

Closure

This is an AND tracking parent, not an implementation task. Close it only after every child is accepted and the original parent acceptance below is verified. A permitted not_applicable child needs the signed route decision required by section 17.4.

Forecasting and potentially actionable warning remain separate from prevention; limited precision cannot be relabeled no signal.

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-27/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.

Native blocking dependencies below represent the child-closure requirements; the parent must never block its own children.

<!-- aes-plan-id: P6-27; backlog-revision: 2.2.1 --> **Plan ID:** `P6-27` **Record type:** Tracking parent; no implementation PR **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 5.3, 10.9. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 8947. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal Verify that the pipeline can distinguish advance information, transfer and useful reaction time. ## Retained requirements - **P6-27.R1:** Add the late-feature, prior-transient, guard-window, audit-isolation and matched-schedule fixtures from section 10.9. - **P6-27.R2:** Implement all-source pilot reports for event/eligibility counts, denominator bounds, false-alarm precision, warmup misses and mapped response latency. - **P6-27.R3:** Freeze the barrier-latency reference and inference recipe; finalize qualification fields and failure wording without changing models, sources or primary margins. ## Child issues - [ ] [P6-27-A (#510)](https://git.erikinkinen.fi/erikinkinen/AES/issues/510) — Check feature alert and outcome ordering - [ ] [P6-27-B (#511)](https://git.erikinkinen.fi/erikinkinen/AES/issues/511) — Report forecasting pilot qualification - [ ] [P6-27-C (#512)](https://git.erikinkinen.fi/erikinkinen/AES/issues/512) — Freeze operational timing measurement recipes ## Closure This is an AND tracking parent, not an implementation task. Close it only after every child is accepted and the original parent acceptance below is verified. A permitted `not_applicable` child needs the signed route decision required by section 17.4. Forecasting and potentially actionable warning remain separate from prevention; limited precision cannot be relabeled no signal. ## 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-27/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. Native blocking dependencies below represent the child-closure requirements; the parent must never block its own children.
erikinkinen added this to the Phase 6 milestone 2026-10-20 15:05:14 +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#509
No description provided.