Phase 3: Qualify certificate tightness and full-campaign feasibility #258

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

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

Goal

Resolve algorithm validity, certificate usefulness and resource needs before production.

Retained requirements

  • P3-26.R1: Execute all 3456 development runs in section 7.6 and archive paired old/priced gaps, nontrivial-cell coverage and complete time/memory/certificate costs.
  • P3-26.R2: Apply the fixed nonzero-U0 count and 75% engineering criteria per cell, preserve limited results, and complete the exact prior-result/consequence dossier.
  • P3-26.R3: Record development qualification/resource projections and prepare the 17280-run production matrix; P3-27 freezes its final protocol/manifest after pilot qualification, and method changes require a new protocol.

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.

Loose certificates remain visible and cannot trigger more search nodes, test seeds or selected benchmark cells.

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/P3-26/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: P3-26; backlog-revision: 2.2.1 --> **Plan ID:** `P3-26` **Record type:** Tracking parent; no implementation PR **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 7.6. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 5775. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal Resolve algorithm validity, certificate usefulness and resource needs before production. ## Retained requirements - **P3-26.R1:** Execute all 3456 development runs in section 7.6 and archive paired old/priced gaps, nontrivial-cell coverage and complete time/memory/certificate costs. - **P3-26.R2:** Apply the fixed nonzero-U0 count and 75% engineering criteria per cell, preserve limited results, and complete the exact prior-result/consequence dossier. - **P3-26.R3:** Record development qualification/resource projections and prepare the 17280-run production matrix; P3-27 freezes its final protocol/manifest after pilot qualification, and method changes require a new protocol. ## Child issues - [ ] [P3-26-A (#259)](https://git.erikinkinen.fi/erikinkinen/AES/issues/259) — Execute the paired-bound development manifest - [ ] [P3-26-B (#260)](https://git.erikinkinen.fi/erikinkinen/AES/issues/260) — Classify certificate utility and resource feasibility - [ ] [P3-26-C (#261)](https://git.erikinkinen.fi/erikinkinen/AES/issues/261) — Finalize the csaII development qualification ## 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. Loose certificates remain visible and cannot trigger more search nodes, test seeds or selected benchmark cells. ## 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/P3-26/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 3 milestone 2026-10-20 15:04:33 +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#258
No description provided.