Resource campaign attempt ledger
This directory retains immutable machine observations for #239. It does not declare full Phase 3 or ticket completion.
| Attempt | Observation | Disposition |
|---|---|---|
| Initial Docker access | Engine pipe unavailable before creation of the owned container | Host unavailable; no resource measurement attempted |
| Initial guest build | Maintained builder rejected missing wit-bindgen | Failed setup; pinned repository installer used before a new attempt |
| Guest build 02 | Maintained builder and signed phase3_workflow_fixture export completed | Input preparation only, not resource PASS |
| Container outage | Docker reports exit 255, OOMKilled: false, finished 2026-09-19T16:56:07.924178783Z | Interrupted container lifetime; not graceful cleanup; no application-failure cause inferred |
| Standalone smoke 01 | Real node rejected configuration before sampling | Failed, zero samples; corrected the harness to use two shared bindings instead of exceeding the existing 16-binding bound |
| Standalone smoke 02 / 03 | Actual deployment mutation 55 returned definite resource-exhausted after six samples | Failed attempts retained; a refusal is not proof of a capacity ceiling. Incomplete requested populations fail the campaign; parent #344 reconciliation work remains separate |
| Python regressions 03 | All 16 small tests passed against code checkpoint 7971a1e3 | Method/process regression result only; not provider measurement PASS |
| Rust experiment 01 | Child-call cancellation observation timed out | Failed unfinished test experiment; not a passed provider report |
| Rust experiment 02 | Pool observation returned actual capability-busy under two runtime workers | Failed unfinished test experiment; no unavailable counter was replaced by zero |
| Rust experiment 03 | Direct blob write returned actual BudgetExhausted under two workers | Failed experiment retained; direct providers now follow their maintained current-thread fixture runtime, separately from the two-worker child manager |
| Rust checkpoint 04 | One actual test passed and wrote 70 snapshots | Preliminary small-fixture observations, not standalone/SSR or full-ticket PASS |
| Cargo-bound Rust run 01 / observations 05 | Exact Cargo artifact and nonempty listing, one passed test, 70 validated snapshots at source 983624be | Real small HTTP/blob/secret/child ownership checkpoint only; full ticket pending |
| Standalone smoke 04 | First package publication returned permission-denied, after three fixed samples | Failed, not the earlier admission refusal. Retained input signature/provenance expired at Unix second 1789837726; native build 02 began at 1789839233 |
| Standalone smoke 05 | Binary identity changed after fresh maintained fixture export | Failed before sampling. Rebuild and record a new identity; never relabel or silently accept the changed executable |
| Standalone smoke 06 | Twelve actual snapshots; cold/warm HTTP and blob worked, peer disconnect returned guest error 11; invalid blob handle returned 10, not the harness's expected 11 | Failed harness expectation retained. Actual added dormant populations were 4 and 14 (requested 16 refused); this is not a capacity proof. Node and peer were force-reaped, not graceful shutdown, and temporary outputs were removed |
| Python regressions 08 | All 22 tests passed | Includes density-refusal, failed-call retention, exact Cargo artifact, nonempty observations and signed-window regressions; not standalone resource PASS |
| Expired-input preflight 01 | Declared signature expiry 1789837726 was earlier than check time 1789839973 | Failed freshness check retained; no clock, signature or trust-policy mutation |
| Standalone smoke 07 | Fourteen actual snapshots before resource-overload-empty; the real rejection carried gRPC resource-exhausted, not a known platform outcome | Failed classifier attempt retained; fixed classification is separately tested, never proof that an ambiguous RPC was not accepted |
| Python regressions 09 | All 23 tests passed at post-merge code 13b21503 | Adds the uncertain-gRPC-versus-known-platform-overload regression; method checks, not standalone resource PASS |
| Cargo-bound Rust run 02 / observations 06 | Exact Cargo artifact, nonempty listing, one passed test and 70 snapshots after merging required parent bec5d8bf, at code 13b21503 | Real small HTTP/blob/secret/child checkpoint only; same actual test binary, new verified source inventory and execution receipt; ticket pending |
| Fixture export 04 / native build 04 | One real signed-fixture export passed, followed by source-bound native node/CLI build at 13b21503 | Preparation only; fresh signed inputs and exact new binaries used by smoke 08 |
| Standalone smoke 08 | Twenty-three actual snapshots, complete HTTP/blob failure/cancel/churn/recovery/unrouting sequence and clean node shutdown; requested 16 dormant deployments admitted only 14 | Failed resource-plateau-check-failed: requested-density check false despite other measured checks true. Node/peer reaped and temporary outputs removed; gRPC overload outcome remains unknown. No resource campaign PASS or capacity-ceiling claim |
| Strict Clippy 01 / 02 | Inherited library warnings denied before the new target | Failed validation retained; unrelated library code left unchanged |
| Provider smoke v2 / 01 / build / export / matrix | Source 4b94e524, 23 snapshots, full 4/16 added dormant population, real provider work and clean shutdown | Seven checkpoint checks passed, not full-ticket acceptance; shutdown retained 11 inactive blob stages |
| Provider campaign v2 / 02 / build / export / matrix | Source 4b94e524, 67 snapshots, full 4/16/32 population and eight cycles; final blob recovery returned known guest-trap | Failed; no graceful shutdown, no reusable blob write-capacity proof; 372 dropped audit observations reported |
| Web smoke v1 / 03 / build / export / matrix | Source 4b94e524, 10 snapshots, complete 2/4 dormant Angular populations; preparation returned gRPC resource-exhausted before rendering | Failed unknown RPC outcome; one control job was shared by preparation and observation, not a successful renderer campaign |
| Web smoke v2 / 04 / build / export / matrix | Source 324f7110, 15 snapshots; preparation launched the actual compiler, then collection raised PermissionError | Failed sampling; compiler dump protection remains enabled, node force-reaped; no preparation or render PASS |
The outage receipt is actual docker inspect output projected to identity,
state, mounts and configured CPU/memory bounds before restarting this worker's
same container. The independent target volume survived. Existing other-agent
containers and volumes were not adopted or modified. A resumed campaign must
identify the host condition and create fresh measurement receipts.
The 20 September recovery qualification records four newly passing bounded profiles and retains the failed setup matrix with its exact disposition.