Phase 2: Check adequate summaries and information bounds #137

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

Plan ID: P2-19
Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 2.3, 6.4.
Source: AES_PHASES_2_6_PLAN.md, issue heading at line 4268.
Plan SHA-256: 8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212
Protocol snapshot: Download the complete governing plan.

Goal

Discharge F2.1 through F2.4 without assuming the desired result.

Retained requirements

  • P2-19.R1: Formalize the standard adequacy lemma and the ideal root/subtree withdrawal models.
  • P2-19.R2: Check origin-summary and ancestor-summary sufficiency and the fixed-length information bound.
  • P2-19.R3: Export statement hashes, dependencies, assumptions and refuted cases in proof_manifest.json.

Child issues

Closure

This is an AND tracking parent, not an implementation task. Close it only after every child is accepted and the original parent acceptance below is verified. A permitted not_applicable child needs the signed route decision required by section 17.4.

The checker accepts all asserted theorems with no admissions; failed propositions are explicit counterexamples rather than silent assumptions.

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-19/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.

Native blocking dependencies below represent the child-closure requirements; the parent must never block its own children.

<!-- aes-plan-id: P2-19; backlog-revision: 2.2.1 --> **Plan ID:** `P2-19` **Record type:** Tracking parent; no implementation PR **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 2.3, 6.4. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 4268. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal Discharge F2.1 through F2.4 without assuming the desired result. ## Retained requirements - **P2-19.R1:** Formalize the standard adequacy lemma and the ideal root/subtree withdrawal models. - **P2-19.R2:** Check origin-summary and ancestor-summary sufficiency and the fixed-length information bound. - **P2-19.R3:** Export statement hashes, dependencies, assumptions and refuted cases in proof_manifest.json. ## Child issues - [ ] [P2-19-A (#138)](https://git.erikinkinen.fi/erikinkinen/AES/issues/138) — Establish the adequacy lemma F2.1 - [ ] [P2-19-B (#139)](https://git.erikinkinen.fi/erikinkinen/AES/issues/139) — Check root-origin adequacy F2.2 - [ ] [P2-19-C (#140)](https://git.erikinkinen.fi/erikinkinen/AES/issues/140) — Check ancestor adequacy F2.3 - [ ] [P2-19-D (#141)](https://git.erikinkinen.fi/erikinkinen/AES/issues/141) — Check the information bound F2.4 - [ ] [P2-19-E (#142)](https://git.erikinkinen.fi/erikinkinen/AES/issues/142) — Export proof manifests ## Closure This is an AND tracking parent, not an implementation task. Close it only after every child is accepted and the original parent acceptance below is verified. A permitted `not_applicable` child needs the signed route decision required by section 17.4. The checker accepts all asserted theorems with no admissions; failed propositions are explicit counterexamples rather than silent assumptions. ## 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-19/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. Native blocking dependencies below represent the child-closure requirements; the parent must never block its own children.
erikinkinen added this to the Phase 2 milestone 2026-10-20 15:04:16 +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#137
No description provided.