Core source: 0409a481c7571e887f8912f0a8cdb93cfdcc01a7. This archive publishes the self-contained service-details.arcadia fixture, its baseline and edit expectations, and the completed core-only evidence. The fixture models a console calling a valve service: two operation allocations, two correlated Call/Reply pairs, typed input/return values and one saved Scenario arrangement.

Closed stage	Result	Evidence
Isolated core probe build 02	Exit 0; empty compiler log; 952 bound inputs unchanged	receipt, log, toolchain
Core probe run 01	Exit 0; exact report passed; 13 bound inputs unchanged	run receipt, stdout, stderr, result

The successful probe used the actual source_files::load_project → compile_bundle → Session::try_new admission path. The original and compiled SourceBundle were equal: no implicit migration, generated identity insertion or source rewrite was admitted. The original source/expectation bytes also remained unchanged after execution. Baseline assertions checked all four complete Exchange bodies, operation allocations, interface/port resolution and Scenario step order.

Accepted changes and rejection

The executed probe translated the listed edits into real single-record Command::EditElement operations. Separately constructed expected Projects changed only the intended fields. Every complete actual Project equalled its expected Project; all unrelated model data, including the control Call/Reply pair and saved arrangement, stayed unchanged.

Task	Complete allowed delta
1	First Call's expression: `"primary"` → `"secondary"`
3a	Remove the first Reply's existing read-result value
3b	First Call's allocation: ReadStatus → SetLimit; its value field becomes Pressure and its expression becomes `18.75`
3c	Add Accepted = `true` to that exact first Reply
3d	First Call's Pressure expression: `18.75` → `19.25`

After task 1, changing only the first Call's operation allocation while retaining its incompatible input and Reply values failed with message_value_field. The executing assertions required unchanged complete Project, revision, dirty state and Undo/Redo flags. Actual Undo still returned directly to baseline. Each accepted edit had exact one-step Undo/Redo, and the final history drain/replay required exactly five accepted records. Both Replies continued to derive their operation from their exact correlated Calls, including allocation, item, interface, ports and transmission; their stored operation remained absent.

All 12 original probe outputs are preserved: the baseline Project, five complete actual/expected Project pairs and the result. Archive preparation independently compared each pair byte for byte and reconstructed the complete successive Projects from the baseline and edit manifest. The separate parent model-difference readback enumerates the same deltas and no others. That readback was created after the run; it is not one of the 12 probe outputs or an original run-receipt artifact. An absent before or after property there denotes addition or removal.

Initial compile diagnostic

Build 01 failed before execution with E0609: the local probe accessed SourceDiagnostic.severity instead of its wrapped SourceDiagnostic.diagnostic.severity. The original source, compiler log, receipt, toolchain and correction record remain intact. Archive preparation verified the only source change was d.severity → d.diagnostic.severity. No production source changed. The corrected probe was then compiled and executed successfully as recorded above.

The two duplicate-sized failed-build input manifests and its dependency-information file are intentionally omitted; their hashes and sizes remain listed as exclusions. The complete successful build input closure is retained. Original preparation notes and hashes may still say “unexecuted” or bind the original probe: those are historical preparation records. This root note describes the completed core scope without rewriting them.

Identity and limits

Build 02 ran from 11:34:15.5331347 to 11:34:45.7793523 UTC on 2026-09-13. Run 01 ran from 11:38:26.3003189 to 11:38:31.9384161 UTC. The direct-rustc builder reused the exact existing oa_core-86a2622fbe014324 and serde_json-da2c4f333fc47818 artifacts from the closed 0409 desktop listing. The runner bound the build receipt, executable, runtime, fixture, expectations and probe source before and after its child process.

The excluded executable is 19,905,536 bytes, SHA-256 7d80f9bca005a9aee7f985235fa520f3e25fe0192d44d00696c2da8b8cb6c439. The excluded runtime DLL is 190,464 bytes, SHA-256 aa282fa47bb2c4e210cea5e470cdbdca58568f0be0bc73e404d86ab9cd95ef6a. Their identities are preserved, not their bytes. The fixture SHA-256 is 0e4325222a451b9d4e503974ce86bb95a9931edd0d2d65b8cd9db8d0f99d69e5; expectations SHA-256 is 6670cd0a07c109dde46128bd094a12d00ea008fc65efd73ad9477efcff976063.

The payload expressions here are stored strings associated with declared typed fields; this probe does not evaluate literal/expression types, calculations or units.

This establishes core admission, operation/field-signature semantics, atomic command rejection and model history for this fixture. It establishes no native Details-form behavior, draft recovery, desktop source-writer synchronization, Save/reopen, graphical interaction or whole-application acceptance. The original native checklist remains a proposed workflow. Original absolute paths are historical provenance; portable fixture/evidence links are provided here. Reproduction requires a compatible source/dependency checkout and fresh output paths, rather than assuming another machine has the original .local layout.

Archive integrity

All 38 selected originals (680,337 bytes) are copied byte for byte under original/. manifest.json records byte counts, SHA-256/Git blob hashes, exclusions and independent comparison checks; it excludes itself. Attributes prevent newline conversion. The four logs—both build compile.log files plus run stdout.log and empty stderr.log—are Git-ignored and require git add -f. Archive preparation performed no compilation, probe execution, staging, commit or publication and did not touch the live primary desktop gate.