Phase 3: Allocate the shared budget by min-plus DP #239

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

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

Goal

Represent large product beliefs without global-world enumeration.

Applicable parent requirements

  • P3-21.R2: Implement min-plus allocation with deterministic ties and an executable component policy.
  • P3-21.R3: Cross-check factored terminal risk and allocations against small exhaustive instances.

Prerequisites

Steps

  • Produce deterministic feasible component allocations and executable policies.

Definition of Done

Allocation risk and tie order match exhaustive small allocations.

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-21-C/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-21-C; backlog-revision: 2.2.1 --> **Plan ID:** `P3-21-C` **Record type:** Implementation leaf **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 7.5; parent requirements and common section-11/17.4 gates apply. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 5550. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). **Tracking parent:** [P3-21 (#236)](https://git.erikinkinen.fi/erikinkinen/AES/issues/236). ## Goal Represent large product beliefs without global-world enumeration. ## Applicable parent requirements - **P3-21.R2:** Implement min-plus allocation with deterministic ties and an executable component policy. - **P3-21.R3:** Cross-check factored terminal risk and allocations against small exhaustive instances. ## Prerequisites - [P2-31 (#194)](https://git.erikinkinen.fi/erikinkinen/AES/issues/194) - [P3-21-B (#238)](https://git.erikinkinen.fi/erikinkinen/AES/issues/238) ## Steps - [ ] Produce deterministic feasible component allocations and executable policies. ## Definition of Done Allocation risk and tie order match exhaustive small allocations. ## 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-21-C/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:30 +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#239
No description provided.