Phase 4: Implement compressed ancestor membership #287

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

Plan ID: P4-14
Record type: Implementation leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 8.4; common contracts in sections 3–5, 11 and 17.4.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 6165.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.

Goal

Expose a measurable storage/selectivity trade-off.

Prerequisites

Steps

  • Implement 64/256/1024-bit masks with the fixed four SHA-256 positions.
  • Implement inherited masks and eager live-token scans on withdrawal.
  • Add no-false-negative and collision/false-positive fixtures with measured costs.

Definition of Done

The production implementation cannot consult true ancestry when evaluating a mask; collisions remain visible as collateral.

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-14/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-14; backlog-revision: 2.2.1 --> **Plan ID:** `P4-14` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 8.4; common contracts in sections 3–5, 11 and 17.4. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 6165. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal Expose a measurable storage/selectivity trade-off. ## Prerequisites - [P3-27 (#262)](https://git.erikinkinen.fi/erikinkinen/AES/issues/262) - [P4-13 (#286)](https://git.erikinkinen.fi/erikinkinen/AES/issues/286) ## Steps - [ ] Implement 64/256/1024-bit masks with the fixed four SHA-256 positions. - [ ] Implement inherited masks and eager live-token scans on withdrawal. - [ ] Add no-false-negative and collision/false-positive fixtures with measured costs. ## Definition of Done The production implementation cannot consult true ancestry when evaluating a mask; collisions remain visible as collateral. ## 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-14/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:37 +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#287
No description provided.