Multinode fleetWhat each physical gate requires, the commands for the handheld transfer run, and the run checklist. Nothing on this page assesses a gate or a device.
- Gates
- 6
- Gates assessed on this page
- 0
Physical multinode verification gates (G0 to G5)
These are gate requirements. Recorded events carry their own evidence scope; device readiness and physical gate completion remain unassessed here.
| Gate | Requirement | Target | Status |
|---|---|---|---|
| G0: Owned Payload | Requires a source-bound payload manifest and matching checksums for every staged artifact. | Desktop -> Staged Artifacts | Gate not assessed |
| G1: Handheld Life | Requires execution of the exact RV64 CRE8OS payload on the handheld, with returned device receipts and capsule. | Anbernic RG353V (RK3566) | Gate not assessed |
| G2: Living Filesystem | Requires physical transfer, restored content verification, measured interface bytes, interruption/resume, and corruption evidence. | Desktop <-> RG353V WiFi | Gate not assessed |
| G3: Useful Peer | Requires a bounded job executed on the handheld and its returned computation receipt. | Anbernic RG353V (RK3566) | Gate not assessed |
| G4: Always-On Node | Requires physical appliance reboot/rejoin, durable store reopen, discovery, and resource measurements. | Raspberry Pi 4 Appliance | Gate not assessed |
| G5: One Semantic Machine | Requires native, VM, and remote results for the same identified program and inputs, with explicit comparison tolerance. | Complete Mesh (All Nodes) | Gate not assessed |
Recorded executions
Recorded causal events, and the re-verification of a stored capsule, are on CausalCapsule's pages.
Open causal event history · Open VM-OS occurrence history
A recording peer ID identifies the receipt issuer. Physical device identity and G0–G5 acceptance require their own evidence; portable verification does not establish those gates.
Anbernic RG353V operator commands (G2 transfer)
Run from the CRE8 repository root in PowerShell. Copy a command, run it in your terminal and inspect its output. SSH requires configured key access. The transfer harness expects a desktop gateway on port 19421 and a device gateway on port 8080; override the script parameters for your setup.
Phase 1: Preflight Network & Storage Probe
Enter a valid device address above to prepare this command.
Queries host architecture, storage, memory, wlan0 counters, and gateway status. Inspect the output for suitability; this does not certify a gate.
Phase 2: Deploy Headless Runtime Daemon
Enter a valid device address above to prepare this command.
Requires the AArch64 runtime binary under runtime/target. Copies it to /userdata/cre8, starts the gateway on port 8080, and queries status.
Phase 3: Execute Live Living Transfer Benchmark
Enter a valid device address above to prepare this command.
Runs cold transfer, one-byte edit, 4 KiB insert, interrupted resume, and duplicate-tree cases. Checks restored roots and reports measured bytes and savings; this script does not run the corruption case required for full G2 acceptance.
Local Sanity Rehearsal (Optional Desktop Pre-Check)
powershell -ExecutionPolicy Bypass -File runtime/scripts/g2_physical_rg353v_transfer.ps1 -Mode Rehearse -DesktopHost 127.0.0.1Uses the desktop gateway at 127.0.0.1:19421 for both endpoints. Exercises local transfer and restore; produces rehearsal evidence only.
Direct SSH Shell / Status Query
Enter a valid device address above to prepare this command.
Inspects the running handheld daemon status and registered routes directly from your terminal.
Execute and Rehearse write summary.json and table.md under runtime/target/g2_physical/<run-id>/. Review the run mode, restored roots, and measured bytes before treating an output as evidence.
Fleet nodes
| Node | Role | Status |
|---|---|---|
| Desktop Workstation (Orchestrator) | Operator workstation. Runs the transfer harness and retains returned evidence. | Not assessed here |
| Raspberry Pi 4 (Always-On Appliance Node) | Target role: always-on storage and relay. Physical reboot/rejoin evidence must identify the appliance and run. | Device not assessed |
| Anbernic RG353V (Handheld Edge Node) | Target role: native AArch64 CRE8VM hosting RV64 CRE8OS, plus a Runtime filesystem receiver. Confirm installed artifacts on the device. | Device not assessed |
Live physical run checklist
A reminder of the order of a live physical run. Following it does not verify a gate or record an execution receipt.
- Boot Anbernic RG353V with Linux SD card in Slot 1 (ROCKNIX / Linux OS).
- Ensure RG353V is connected to the same Wi-Fi subnet as this desktop.
- Confirm device IP in Settings → Network and enter it as the target device address.
- Run Phase 1 Preflight and review SSH connectivity, architecture, storage, and gateway output.
- Run Phase 2 Deploy to transfer and launch the headless daemon on port 8080.
- Run Phase 3 Execute to run the living filesystem benchmark and measure hardware wire savings.