Files
ARCADIA-Studio/harness/experiments/contextual-source-lifeline-v2-20260911/README.md
T

28 lines
4.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Direct Lifeline creation and history — GUI5657, 2026-09-11
Codex-9e8r6t `/root/behavior_audit`. Exact archival copy of root's closed native trial: **22 original files, 336,846 bytes**, plus this README, `manifest.json` and `readback.json`. Only `runs/direct-creation`, the three First/Undo/Redo checkpoints and their result/log pairs are included. Recovery, profile/work data, cancellation and Machine evidence remain excluded. The two empty direct-run stdout/stderr logs are preserved.
The [native v2 report](../../release-contextual-source-native-v2-20260911.md) owns native observations. The pre-observation [fixture contract](../../fixtures/staged-source-authoring/README.md) and [oracle preparation](../../release-staged-source-authoring-oracle-20260911.md) own expected semantics. This reviewer inspected those contracts, the actual result arguments/logs, complete checkpoint bytes and both pre-Save screenshots. **No oracle, test or compiler was rerun**, and no native input or Git staging occurred.
PID9792 launched at 15:33:13 UTC and closed through native Alt+F4 at 15:37:41 UTC. The close record reports the process absent and leaves its exit code null. Launch evidence pins GUI SHA256 `5657BAB5C841939B66F901EFE6C0FFB2D7CBBE8CC5F111A0CA3DE8073D3846CE` and runtime `F45604A12E8BCD839FD86F667C1BE1CC7C4F9DA2B3C69FF381AC708F0E1AE7D4`. The recorded checks pin oracle executable `967D9BA3C6FB3A7EFB410833903EC94556CA2D48A67D5072C8BB160F40A00F9C`; its existing source was independently rehashed as `9EB9DD3868B6CB772F907D16AE02995AD10A16F85C087012C24948E6E6FE775D`. No binary is copied here.
Before parent Create, the screenshot shows `Assessment lifeline`, staged root Activity `Assess incident work`, and 2 objects/0 links. After Create and before Save, the screenshot shows the selected Lifeline, represented Activity, unsaved status and 4 objects/0 links. Root's recorded action sequence establishes that Create preceded Save; these screenshots corroborate the two states.
| Checkpoint | Recorded command | Actual checker exit | Reachable / physical source files |
| --- | --- | ---: | --- |
| First | `check lifeline BASE FIRST FIRST` | 0 | 3 / 3 |
| Undo | `same BASE UNDO FIRST` | 0 | 2 / 3 |
| Redo | `check lifeline BASE REDO FIRST` | 0 | 3 / 3 |
`BASE` is the unchanged two-file published fixture. `FIRST` always means `checkpoint-first/project.arcadia`, including for Redo. It supplies only fresh, uniquely named/kinded UUID roles to the oracle's independently constructed complete Project and exact source expectation. **Redo is never its own UUID authority.** Reviewed oracle code creates a root OA Activity and scenario-owned Lifeline representing it; it adds no occurrences, steps, allocations, relations or view.
The original first-commit UUIDs are Activity **Assess incident work** `9b8b4b55-1e91-46de-bf71-cdf7f78b29cf` and Lifeline **Assessment lifeline** `bdb0f3c1-9781-4049-ab35-a23646e5e718`. Both are distinct fresh UUIDv4 values. Existing project, scenario and SA chain retain the published `d1510000-0000-4000-8000-000000000001` / `…0002` / `…0003` identities; full values are in the readback record.
Fresh archive comparison confirms all three Redo files are byte-identical to First. Undo's reachable project and Unicode note equal BASE byte-for-byte; its only retained file is the exact First Activity file, `oa/activities/activity_assess_incident_work.arcadia`, SHA256 `65FACE018ACFBDA615703833D598CA4D5D7DA15A266943430B66F2AD45AD2C75`. All nine recorded checkpoint file hashes/sizes match the actual files. These byte/argument checks supplement the recorded full-core oracle passes; they are not a new semantic evaluator run.
All three screenshots contain **JPEG (`image/jpeg`)** bytes at 1442×932 pixels. `runs/direct-creation/staged-before-create.png` and `created-before-save.png` retain their original misleading `.png` names; `redo-saved.jpg` has the correct extension. No image was transcoded or renamed. The manifest records decoder-confirmed MIME, dimensions, original extension, mismatch and exact SHA256 separately.
`manifest.json` inventories all 22 originals by source path, size and hash. `readback.json` pins the manifest and README and records the fresh exact-copy, carrier and result-inventory comparisons; it excludes itself from hash coverage. One orchestration syntax error occurred before filesystem execution. The first archive preflight then refused an assumed 20-file count before creating output: complete enumeration found the two authorized empty logs omitted by the initial ignored-file-aware listing. The corrected archive includes both; these were archival preparation failures, not native or oracle failures.
The archive's narrow repository attributes rule disables newline conversion so measured source/log bytes can survive a later Git round trip. Staging, publication and round-trip verification remain root-owned. No broader recovery, Machine, full-suite or final release acceptance follows from this archive.