Phase 5: Review and freeze the job case contract #420

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

Plan ID: P5-30-B
Record type: Review leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 9.10, 10.10; parent requirements and common section-11/17.4 gates apply.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 7822.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.
Tracking parent: P5-30 (#418).

Goal

Establish external-validation prerequisites before forecasting pilots.

Applicable parent requirements

  • P5-30.R1: Obtain and archive each case-contract review with source, parameter and mapping hashes.

Prerequisites

Steps

  • Archive the job workflow's requirement and mapping review.

Definition of Done

Every modeled event maps to an actual call or an explicit unsupported behavior.

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/P5-30-B/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: P5-30-B; backlog-revision: 2.2.1 --> **Plan ID:** `P5-30-B` **Record type:** Review leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 9.10, 10.10; parent requirements and common section-11/17.4 gates apply. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 7822. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). **Tracking parent:** [P5-30 (#418)](https://git.erikinkinen.fi/erikinkinen/AES/issues/418). ## Goal Establish external-validation prerequisites before forecasting pilots. ## Applicable parent requirements - **P5-30.R1:** Obtain and archive each case-contract review with source, parameter and mapping hashes. ## Prerequisites - [P4-24 (#319)](https://git.erikinkinen.fi/erikinkinen/AES/issues/319) - [P5-29 (#409)](https://git.erikinkinen.fi/erikinkinen/AES/issues/409) ## Steps - [ ] Archive the job workflow's requirement and mapping review. ## Definition of Done Every modeled event maps to an actual call or an explicit unsupported behavior. ## 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/P5-30-B/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 5 milestone 2026-10-20 15:04:59 +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#420
No description provided.