Stage explicit prerequisite sources inside behavior creation forms

harness/fixtures/staged-source-authoring/README.md

@@ -0,0 +1,46 @@
+# Staged prerequisite source creation: frozen native contract
+
+Codex-9e8r6t /root/palette_finish,2026-09-11. Prepared before inspecting any produced staged-source output. The standalone core-only evaluator is `harness/staged-source-authoring-contract.rs`. Root subsequently granted a direct-rustc window: warnings-denied compilation, self-check and exact baseline check **passed**. This validates the evaluator/fixture, not native staged-source creation. Existing immutable CLI admission of this starting fixture also succeeded with three ordinary completeness warnings. Build/provenance is in `harness/release-staged-source-authoring-oracle-20260911.md`.
+
+Copy the whole `base` directory into a new isolated native work directory. Do not edit these source fixtures or overwrite an earlier checkpoint. Baseline has a root project, an empty explicit OA OperationalActivity scenario, an empty SA Functional chain and an independent Unicode comment include. All three persistent IDs are explicit; there are no existing activities/functions/participants, views, relations or traces.
+
+| File | Bytes | SHA256 before native output |
+| --- | ---: | --- |
+| `base/project.arcadia` |593|`AA844950EC4FB86F262A257E1FC370A26557EA7978D8A4CAB78265037660234C`|
+| `base/notes.arcadia` |63|`AD9DE02963C20D1F43856455A797DEB05CA674659E45F2C4B96B52783024F8BD`|
+
+## Exact cumulative native actions
+
+1. OA Behavior → **Operational assessment**. The viewpoint is already **OperationalActivity**; use the semantic empty-state **Add first lifeline** action. Name the lifeline **Assessment lifeline**. Open **Create new source**, choose/retain Activity and layer-root semantic parent, and name it **Assess incident work**. Child **Use** returns to the retained parent. Verify the two distinct names, then apply the parent once. Only one root Activity plus one lifeline owned by the existing scenario, representing that Activity, should be created. Scenario steps remain empty; no occurrence, allocation, relation or view is implicit.
+2. SA Behavior → **System assessment**. Use **Add first function contribution**. Name the contribution **Classify this request**. Open **Create new source**, choose/retain Function and layer-root semantic parent, name it **Classify request**, and **Use**. Apply the retained parent once. Only one root Function and one Action occurrence under the existing chain should be created; the chain steps become exactly `[NEW_CONTRIBUTION]`. Its action is the new Function, lifeline is absent, conditions are empty. An isolated first contribution has no sequence link or allocation.
+3. SA Behavior → **New → State machine**. Name it **Field team operating modes**. Open **Create new owner**, explicitly select **SystemActor**, retain layer-root parent, name it **Field rescue team**, and **Use**. Check **Create the first state view**, then **Create and open** once. Only the root actor, its owned machine, and the opt-in diagram/root placement should be created. The diagram is **Field team operating modes · states**, SA StateMachine projection; default options, no routes/regions/states. Root placement is independently specified at60,60,size336×104 and passed through the shared core Layout command.
+
+After each creation, Save and preserve a fresh whole-directory **first-commit** checkpoint. Undo **once**, Save and preserve another directory; Redo **once**, Save and preserve another. After all three, use the real file picker to reopen the final project, Save and preserve a final directory. If checking child Use before Apply or cancellation, save into a separate checkpoint and compare against the preceding accepted stage: no staged prerequisite may have been adopted.
+
+All source/consumer names, ownership, references, defaults, membership and view geometry above are fixed expectations. The oracle borrows only unique fresh UUIDv4 roles by exact kind/layer/name (plus view projection and placement target). It never copies observed aliases, descriptions, parents, bodies, geometry, source text or diagrams wholesale. Every existing source byte and complete model field is compared after constructing the expected core-command result.
+
+## Checker invocation and identity authority
+
+After a root-authorized direct-rustc build using a matching completed `oa_core` rlib and `--edition2024 -D warnings`, let `$oracle` identify that immutable executable and `$base` the frozen baseline entry. Other variables below are preserved entry-file paths:
+
+```powershell
+& $oracle self-check $base
+& $oracle check baseline $base $base
+& $oracle check lifeline $base $firstLifeline $firstLifeline
+& $oracle same $base $undoLifeline $firstLifeline
+& $oracle check lifeline $base $redoLifeline $firstLifeline
+& $oracle check chain $base $firstChain $firstLifeline $firstChain
+& $oracle same $firstLifeline $undoChain $firstChain
+& $oracle check chain $base $redoChain $firstLifeline $firstChain
+& $oracle check machine $base $firstMachine $firstLifeline $firstChain $firstMachine
+& $oracle same $firstChain $undoMachine $firstMachine
+& $oracle check machine $base $redoMachine $firstLifeline $firstChain $firstMachine
+& $oracle check machine $base $reopen $firstLifeline $firstChain $firstMachine
+& $oracle same $redoMachine $reopen
+```
+
+Every stage supplies **all preceding original first-commit role carriers separately**. Those carriers are themselves checked against the cumulative contract. A later creation therefore cannot replace a prior stage's UUID and declare the replacement its own role authority; Redo and reopen cannot borrow new identities from their own output. The baseline source bytes are embedded in the checker at build time, so replacing the runtime fixture does not change its expected input.
+
+The retained-file rule matches the corrected creation-v2 harness: normal checkpoints must have exactly reachable `.arcadia` files. `same EXPECTED ACTUAL UNDO_FROM` requires complete Project and reachable SourceBundle equality, and exact physical bytes equal to the explicitly proven first-commit disk map overlaid with EXPECTED's restored reachable files. Only those known detached files may remain. Unknown, changed or missing retained files fail. No file is taken from actual Undo output to define its own expected bytes. There is no broad orphan-file exemption.
+
+Self-check prepares deliberately false metadata/geometry role carriers, full source fixed points, complete model/byte-drift falsifiers, exact repeated-command refusal, one core-session Undo/Redo, retained-file falsifiers and independent earlier-stage identity pinning. These **passed as evaluator checks**, not native acceptance. Predicted reachable-file counts are3 after Lifeline,4 after Chain and6 after Machine. Native focus, first-action discoverability, preserved raw parent/child drafts, selection, minimum/wide layout and real one-step history still require separate observation.

harness/fixtures/staged-source-authoring/base/notes.arcadia

@@ -0,0 +1 @@
+// Preserve this independent engineering note: secours 雨 Δ.

harness/fixtures/staged-source-authoring/base/project.arcadia

@@ -0,0 +1,15 @@
+arcadia 7;
+project contextual_source_acceptance "Contextual source acceptance" id "d1510000-0000-4000-8000-000000000001" {
+    include "notes.arcadia";
+
+    // The viewpoint is explicit before any lifeline exists.
+    oa_scenario operational_assessment "Operational assessment" id "d1510000-0000-4000-8000-000000000002" {
+        viewpoint OperationalActivity;
+        steps [];
+    }
+
+    // Contributions are occurrences; root Functions are separate sources.
+    sa_functional_chain system_assessment "System assessment" id "d1510000-0000-4000-8000-000000000003" {
+        steps [];
+    }
+}