Phase 4: Adapt direct and traversal strategies #277

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

Plan ID: P4-06-A
Record type: Implementation leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 3.5, 8.1, 8.2; parent requirements and common section-11/17.4 gates apply.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 6028.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.
Tracking parent: P4-06 (#276).

Goal

keep seven historical baselines comparable without changing semantics.

Applicable parent requirements

  • P4-06.R1: Add ManagerView adapters preserving legacy target and access algorithms.

Prerequisites

Steps

  • Connect direct/snapshot and BFS/DFS mechanisms to the declared retained views.

Definition of Done

Full-retention legacy outcomes/traversal order remain unchanged.

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/P4-06-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: P4-06-A; backlog-revision: 2.2.1 --> **Plan ID:** `P4-06-A` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 3.5, 8.1, 8.2; parent requirements and common section-11/17.4 gates apply. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 6028. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). **Tracking parent:** [P4-06 (#276)](https://git.erikinkinen.fi/erikinkinen/AES/issues/276). ## Goal keep seven historical baselines comparable without changing semantics. ## Applicable parent requirements - **P4-06.R1:** Add ManagerView adapters preserving legacy target and access algorithms. ## Prerequisites - [P3-27 (#262)](https://git.erikinkinen.fi/erikinkinen/AES/issues/262) - [P4-03 (#271)](https://git.erikinkinen.fi/erikinkinen/AES/issues/271) - [P4-04 (#274)](https://git.erikinkinen.fi/erikinkinen/AES/issues/274) - [P4-05 (#275)](https://git.erikinkinen.fi/erikinkinen/AES/issues/275) ## Steps - [ ] Connect direct/snapshot and BFS/DFS mechanisms to the declared retained views. ## Definition of Done Full-retention legacy outcomes/traversal order remain unchanged. ## 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/P4-06-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 4 milestone 2026-10-20 15:04:35 +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#277
No description provided.