Phase 5: Inject process crashes and storage-prefix faults #379

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

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

Goal

Test implementation recovery at the declared failure boundaries.

Retained requirements

  • P5-21.R1: Add the ten SIGKILL hooks and deterministic prefix-loss emulator.
  • P5-21.R2: Prepare and fixture-test the 3840 fault-trace and 384 no-crash manifests; actual production execution belongs to P5-32-F.
  • P5-21.R3: Compare acknowledged withdrawals and post-recovery access and minimize every mismatch.

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.

Process-crash and modeled-storage evidence remain separate; broken configurations demonstrate the expected negative controls.

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-21/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: P5-21; backlog-revision: 2.2.1 --> **Plan ID:** `P5-21` **Record type:** Tracking parent; no implementation PR **Scientific protocol:** 2.2 · **Backlog revision:** 2.2.1 **Specification:** sections 9.8. **Source:** `AES_PHASES_2_6_PLAN.md`, issue heading at line 7323. **Plan SHA-256:** `8acdaeb52d6a94fcad7de64d64521cd465f608344d63560b45f9202f5af71212` **Protocol snapshot:** [Download the complete governing plan](https://git.erikinkinen.fi/attachments/31cb768b-4788-4e38-aba9-9d7f0d1ee16d). ## Goal Test implementation recovery at the declared failure boundaries. ## Retained requirements - **P5-21.R1:** Add the ten SIGKILL hooks and deterministic prefix-loss emulator. - **P5-21.R2:** Prepare and fixture-test the 3840 fault-trace and 384 no-crash manifests; actual production execution belongs to P5-32-F. - **P5-21.R3:** Compare acknowledged withdrawals and post-recovery access and minimize every mismatch. ## Child issues - [ ] [P5-21-A (#380)](https://git.erikinkinen.fi/erikinkinen/AES/issues/380) — Inject deterministic process crashes - [ ] [P5-21-B (#381)](https://git.erikinkinen.fi/erikinkinen/AES/issues/381) — Emulate storage-prefix loss independently - [ ] [P5-21-C (#382)](https://git.erikinkinen.fi/erikinkinen/AES/issues/382) — Plan and compare the crash campaign ## 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. Process-crash and modeled-storage evidence remain separate; broken configurations demonstrate the expected negative controls. ## 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-21/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 5 milestone 2026-10-20 15:04:50 +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#379
No description provided.