Phase 2: Execute phase 2 and release evidence #194
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
#201 Phase 3: Implement ManagerView isolation
erikinkinen/AES
#200 Phase 3: Freeze epistemic semantics
erikinkinen/AES
#204 Phase 3: Hide edges and subject/object entities
erikinkinen/AES
#202 Phase 3: Implement provenance erasure
erikinkinen/AES
#209 Phase 3: Implement the permissive withdrawal planner
erikinkinen/AES
#205 Phase 3: Hide component layers
erikinkinen/AES
#206 Phase 3: Implement delayed observations
erikinkinen/AES
#207 Phase 3: Implement corrupt observation records
erikinkinen/AES
#211 Phase 3: Check planner information and action parity
erikinkinen/AES
#210 Phase 3: Implement the conservative withdrawal planner
erikinkinen/AES
#215 Phase 3: Implement csaII statistical contrasts
erikinkinen/AES
#214 Phase 3: Add belief and exposure measurements
erikinkinen/AES
#217 Phase 3: Validate fault isolation and replay
erikinkinen/AES
#216 Phase 3: Generate epistemic result artifacts
erikinkinen/AES
#219 Phase 3: Represent correlated feasible worlds
erikinkinen/AES
#213 Phase 3: Add shallow epistemic experiment tapes
erikinkinen/AES
#212 Phase 3: Implement restoration controls
erikinkinen/AES
#221 Phase 3: Enforce observation budgets and query exports
erikinkinen/AES
#225 Phase 3: Compute fixed nonadaptive query optima
erikinkinen/AES
#220 Phase 3: Implement trusted point and group queries
erikinkinen/AES
#223 Phase 3: Compute exact terminal minimax loss
erikinkinen/AES
#224 Phase 3: Compute exact adaptive decision policies
erikinkinen/AES
#226 Phase 3: Prove adaptive oracle optimality F3.1
erikinkinen/AES
#231 Phase 3: Integrate the five management policies
erikinkinen/AES
#229 Phase 3: Implement lexicographic budgeted queries
erikinkinen/AES
#230 Phase 3: Implement greedy budgeted queries
erikinkinen/AES
#237 Phase 3: Store product-component beliefs
erikinkinen/AES
#238 Phase 3: Compute local risk curves
erikinkinen/AES
#232 Phase 3: Generate the primary decision-frontier campaign
erikinkinen/AES
#241 Phase 3: Expose initial bound providers
erikinkinen/AES
#239 Phase 3: Allocate the shared budget by min-plus DP
erikinkinen/AES
#242 Phase 3: Build the canonical belief search DAG
erikinkinen/AES
#243 Phase 3: Refine bounds under the expansion cap
erikinkinen/AES
#244 Phase 3: Preserve the feasible minimizing policy
erikinkinen/AES
#245 Phase 3: Prove component brackets F3.4
erikinkinen/AES
#246 Phase 3: Prove refinement and policy bounds F3.5/F3.6
erikinkinen/AES
#249 Phase 3: Review the epistemic contribution before execution
erikinkinen/AES
#248 Phase 3: Implement the fixed scaling campaign
erikinkinen/AES
#247 Phase 3: Independently check small search certificates
erikinkinen/AES
#251 Phase 3: Define the local priced game
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
#254 Phase 3: Serialize local priced certificates
erikinkinen/AES
#256 Phase 3: Integrate priced initialization into search
erikinkinen/AES
#255 Phase 3: Verify priced certificates independently
erikinkinen/AES
#264 Phase 3: Execute the phase-3 pilot
erikinkinen/AES
#265 Phase 3: Select N3 and freeze the phase-3 production design
erikinkinen/AES
#259 Phase 3: Execute the paired-bound development manifest
erikinkinen/AES
#261 Phase 3: Finalize the csaII development qualification
erikinkinen/AES
#263 Phase 3: Verify phase-3 readiness and pilot capacity
erikinkinen/AES
#266 Phase 3: Execute the phase-3 production matrices
erikinkinen/AES
#267 Phase 3: Produce phase-3 inference and comparison outputs
erikinkinen/AES
#268 Phase 3: Review and archive the phase-3 evidence release
erikinkinen/AES
#196 Phase 2: Execute the fixed phase-2 AES matrices
erikinkinen/AES
#197 Phase 2: Verify phase-2 reference and external evidence
erikinkinen/AES
#198 Phase 2: Produce phase-2 tables figures and conclusions
erikinkinen/AES
#199 Phase 2: Review and archive the phase-2 evidence release
erikinkinen/AES
Reference
erikinkinen/AES#194
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:
P2-31Record type: Tracking parent; no implementation PR
Scientific protocol: 2.2 · Backlog revision: 2.2.1
Specification: sections 6, 11.1, 17.1, 17.2.
Source:
AES_PHASES_2_6_PLAN.md, issue heading at line 4953.Plan SHA-256:
8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212Protocol snapshot: Download the complete governing plan.
Goal
finish phase 2 with an auditable conclusion.
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.phase-2 implementation and evidence checks pass and every witness or
explicit null result is preserved. The phase-5 F2.7 supplement remains declared
pending; it is neither an admitted lemma nor a premise of phase-2 proofs.
Milestone 3 does not require journal_ready or a positive effect.
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-31/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.