Phase 3: Prove and implement the priced-query lower bound #250
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#249 Phase 3: Review the epistemic contribution before execution
erikinkinen/AES
#252 Phase 3: Evaluate exact prices and compose the lower bound
erikinkinen/AES
#253 Phase 3: Prove hard-budget admissibility F3.7
erikinkinen/AES
#251 Phase 3: Define the local priced game
erikinkinen/AES
#254 Phase 3: Serialize local priced certificates
erikinkinen/AES
#255 Phase 3: Verify priced certificates independently
erikinkinen/AES
#256 Phase 3: Integrate priced initialization into search
erikinkinen/AES
Reference
erikinkinen/AES#250
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan ID:
P3-25Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 7.5, 7.6.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 5682.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
Replace the degenerate sole lower bound with the explicitly budget-priced relaxation.
Retained requirements
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_applicablechild needs the signed route decision required by section 17.4.Every advertised lower bound has a proof and checkable certificate; standard Lagrangian techniques are credited.
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-25/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.