Phase 3: Add belief and exposure measurements #214

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

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

Goal

quantify the consequences of the observation function.

Prerequisites

Steps

  • Export belief false positives/negatives, missed/false target atoms and retained bytes.
  • Add exposure area, smoothed amplification, first-breach durations and overshoot.
  • Add per-checkpoint truth-versus-belief reconciliation.

Definition of Done

ground truth is evaluated against the same state and zero baselines
cannot become infinite or silently perfect ratios.

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-10/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: P3-10; backlog-revision: 2.2.1 --> **Plan ID:** `P3-10` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 7.3; common contracts in sections 3–5, 11 and 17.4. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 5227. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal quantify the consequences of the observation function. ## Prerequisites - [P2-31 (#194)](https://git.erikinkinen.fi/erikinkinen/AES/issues/194) - [P3-08 (#212)](https://git.erikinkinen.fi/erikinkinen/AES/issues/212) ## Steps - [ ] Export belief false positives/negatives, missed/false target atoms and retained bytes. - [ ] Add exposure area, smoothed amplification, first-breach durations and overshoot. - [ ] Add per-checkpoint truth-versus-belief reconciliation. ## Definition of Done ground truth is evaluated against the same state and zero baselines cannot become infinite or silently perfect ratios. ## 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-10/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 3 milestone 2026-10-20 15:04:26 +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#214
No description provided.