Phase 2: Introduce operation counter contracts #88

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

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

Goal

freeze the measurable work unit.

Prerequisites

Steps

  • Add OperationCountersV1 and the ten record-access counting rules.
  • Add bucket identities, sum checks and abstract packed-storage accounting.
  • Specify queue/stack peaks and exclude oracle/validation overhead.

Definition of Done

counters have explicit units and every primitive operation has one
counting point; old counters 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/P2-05/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-05; backlog-revision: 2.2.1 --> **Plan ID:** `P2-05` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 3.6; common contracts in sections 3–5, 11 and 17.4. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 3658. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal freeze the measurable work unit. ## Prerequisites - [P2-01 (#84)](https://git.erikinkinen.fi/erikinkinen/AES/issues/84) ## Steps - [x] Add OperationCountersV1 and the ten record-access counting rules. - [x] Add bucket identities, sum checks and abstract packed-storage accounting. - [x] Specify queue/stack peaks and exclude oracle/validation overhead. ## Definition of Done counters have explicit units and every primitive operation has one counting point; old counters 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/P2-05/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:09 +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#88
No description provided.