Phase 5: Implement provenance-guarded loading #338

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

Plan ID: P5-05-D
Record type: Implementation leaf
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 9.2; parent requirements and common section-11/17.4 gates apply.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 6801.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.
Tracking parent: P5-05 (#334).

Goal

compare explicit cleanup commitments.

Applicable parent requirements

  • P5-05.R2: Add provenance_guarded origin records and load checks.
  • P5-05.R3: Instrument scrub scans, provenance checks, blocked epochs and collateral erasure.

Prerequisites

Steps

  • Retain runtime origin metadata and deny unknown/withdrawn-origin loads.

Definition of Done

Guard checks use no analyst ledger and their storage/access costs are measured.

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/P5-05-D/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: P5-05-D; backlog-revision: 2.2.1 --> **Plan ID:** `P5-05-D` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 9.2; parent requirements and common section-11/17.4 gates apply. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 6801. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). **Tracking parent:** [P5-05 (#334)](https://git.erikinkinen.fi/erikinkinen/AES/issues/334). ## Goal compare explicit cleanup commitments. ## Applicable parent requirements - **P5-05.R2:** Add provenance_guarded origin records and load checks. - **P5-05.R3:** Instrument scrub scans, provenance checks, blocked epochs and collateral erasure. ## Prerequisites - [P4-24 (#319)](https://git.erikinkinen.fi/erikinkinen/AES/issues/319) - [P5-06 (#339)](https://git.erikinkinen.fi/erikinkinen/AES/issues/339) ## Steps - [ ] Retain runtime origin metadata and deny unknown/withdrawn-origin loads. ## Definition of Done Guard checks use no analyst ledger and their storage/access costs are measured. ## 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/P5-05-D/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 5 milestone 2026-10-20 15:04:45 +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#338
No description provided.