Phase 2: Validate qualification records #190

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

Plan ID: P2-30-A
Record type: Implementation leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 2.5, 2.6, 4.5, 4.6, 6.6, 11.3–11.7, 17.4; parent requirements and common section-11/17.4 gates apply.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 4909.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.
Tracking parent: P2-30 (#189).

Goal

Turn novelty questions into reviewable proof/witness decisions and define the later full-manuscript deliverables.

Applicable parent requirements

  • P2-30.R1: Implement section-2.6 qualification manifests, dossier completeness checks and separate method/contribution/utility statuses.

Prerequisites

Steps

  • Implement section-2.6 method/contribution/utility status schemas and freeze checks.

Definition of Done

Invalid methods block execution; limited utility cannot silently become an informative result.

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/P2-30-A/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: P2-30-A; backlog-revision: 2.2.1 --> **Plan ID:** `P2-30-A` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 2.5, 2.6, 4.5, 4.6, 6.6, 11.3–11.7, 17.4; parent requirements and common section-11/17.4 gates apply. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 4909. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). **Tracking parent:** [P2-30 (#189)](https://git.erikinkinen.fi/erikinkinen/AES/issues/189). ## Goal Turn novelty questions into reviewable proof/witness decisions and define the later full-manuscript deliverables. ## Applicable parent requirements - **P2-30.R1:** Implement section-2.6 qualification manifests, dossier completeness checks and separate method/contribution/utility statuses. ## Prerequisites - [P2-25 (#161)](https://git.erikinkinen.fi/erikinkinen/AES/issues/161) - [P2-29 (#185)](https://git.erikinkinen.fi/erikinkinen/AES/issues/185) ## Steps - [ ] Implement section-2.6 method/contribution/utility status schemas and freeze checks. ## Definition of Done Invalid methods block execution; limited utility cannot silently become an informative result. ## 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/P2-30-A/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 2 milestone 2026-10-20 15:04:23 +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#190
No description provided.