Stitch / recoverable objects and replayable pure jobs

Local Node: ... | WebRTC Open Peers: 0 | Application budget: 0 requests

Available next actions:

About modeled evidence

Join a mesh

What this evidence means

Inspect external network observations

Scheduler estimates, not availability evidence: Scheduler λ̂: 0.017/s | P(alive): 1.000 | H(p): 0.000 bit |

Network evidence and independent verification

Cloudflare Edge PoP: probing 1.1.1.1... | STUN Candidate: waiting
These commands inspect external records. Inspection alone does not establish integrity, authority, or durability; use the repository verifier for exported object evidence:
curl -s "https://ntfy.sh/syntra-warm-syntra-uor-bus-01/json?poll=1&since=30m" | tail -n 5

Inspect and renew allowances

What this evidence means

Application resource policy (operational demo configuration)

These are configurable operating allowances, not semantic limits. An expired epoch or exhausted allowance refuses further effects. Choose a new epoch to continue; previous charges are retained, including failed or uncertain effects. Existing objects, jobs and pointer heads stay in this tab.

Transfer allowances include reserved relay/DNS response ceilings. Cache allowances count new allocations in each epoch, not total browser memory. TLS, ICE/STUN, VM work and host overhead are outside this accounting. History is kept in this tab until exported. Renewal does not retry failed effects; use the relevant sync or resume control.

No prior epochs.
Experimental diagnostics and trial export

Live Network UOR Database (2-of-3 XOR Parity + WebRTC + Warm Cache)

Recovery requires enough reachable fragments; relay storage is optional

What this evidence means

After peers join or change, select exact retained bytes and repair. Missing or expired fragments need fresh receipts. Optional replacement keeps the old holder until the new receipt commits, then requests exact release. A timeout never proves deletion.

No retained verified object selected.

Text is encoded as UTF-8, at most 128 KiB. The label is a convenience alias, not identity. New objects are shared with the guest only when guest object sharing is enabled.

Object commitment (SHA-256) Label (/mnt) Size Verified Source Payload Preview
No local object bytes.
Export and restore recovery evidence

Keep a separate backup before clearing RAM. Import checks objects and pure jobs in a local recovery vault, without sending packets, mounting files or retrying writes. Closing this tab loses the vault. Signing keys and pending-write journals are not included.

Select 1–32 live entries. Use Ctrl/Command to toggle individual choices or Shift for a range. Reopening refreshes available evidence and retains still-available selections. Imported evidence stays in the separate recovery vault and is not added to live objects or jobs.

At most 32 entries, each object up to the live 128 KiB limit. Default wire allowance includes hex fragments and job overhead. Limits bound this operation, not total browser memory; replay is pure computation, not VM execution.

Review supplied pointer anchors

Signatures inside a file do not establish trust or freshness. Independently obtain the exact recent pointer digest and writer key. First accept the exact recent anchor here. Then, in “Pin, discover and publish pointers”, independently pin the same query name and writer key. Return here to restore the accepted anchor into that live observer. Import and acceptance alone never change a live head.

Restore only an empty observer or the exact already-retained head. A different live head is never overwritten, even by a newer accepted anchor. This session-only action enables ordinary next-revision admission, not publication, key rotation or proof of global freshness.

No recovery file imported.

Live Distributed Compute Engine (Cross-Tab Checkpoint Failover)

Pure jobs replay before resume; VM effects are outside this contract

What this evidence means

This demonstration constructs a deterministic W64 ring program. Choose 3–60 steps and a 100–3000 ms delay. Pure replay is separate from guest shell execution.

Job ID Progress Owner Node Current W64 Ring Value Status Execution evidence
No pure jobs observed. Use the current journey to start or inspect checkpoint recovery.

In-Browser x86 Linux VM (v86 + 9p /mnt + Ethernet-over-WebRTC)

VM Standby

What this evidence means

Guest limits and stopping

The whole VM stops when its elapsed-time allowance expires, when Cancel is requested after dispatch, or when a filesystem/result limit is exceeded. This includes background commands and console work. Browser scheduling can delay stopping; this is not an instruction-accurate CPU quota. Destroy the instance before changing its allowance.

Guest RAM: 64 MiB. Local 9p /mnt: 16 MiB per buffer, 64 MiB cumulative allocation requests, and 4096 inode/link admissions per instance. Removing files does not refund that allowance. Result reads: 4 MiB per command, 16 MiB retained in total. Other guest filesystems consume configured guest memory; these controls are not a complete host-memory or guest-isolation guarantee.

No guest resource usage observed.

Optional guest networking: offline

Leave blank for offline shell and object work. For Ethernet sharing, choose a different address for every guest on the mesh and compatible subnet prefixes. The example is not an allocation. Display names do not assign addresses. No DHCP, duplicate-address detection, gateway or DNS setup is provided. /31 is for point-to-point links; /32 needs explicit guest routes. Destroy a retained instance before changing configuration.

No static address configured.

Commands run in the guest, not on this host. Stdout and stderr are captured as bytes and shown as text below, including when storing the object fails. After dispatch, Cancel requests a stop of the whole VM, including other guest work. Public relay consent also applies to stored command output.

No guest command submitted.

Cancelling before dispatch prevents the command. After dispatch, cancellation stops the whole VM and leaves prior effects unknown. A short observation timeout keeps the guest running until cancellation or the runtime limit. Unknown commands are never automatically replayed. Stop and destroy revoke grants; failures retain the instance for destroy retry. These controls do not certify guest isolation.

Observed guest command output (text)

No guest output observed.

No guest output observed.

The console below is the emulator display. Shell commands and their captured text above do not require interacting with its canvas. Graphics-only guest applications may have no text equivalent.

Click "Boot Linux VM" to start the in-browser x86 kernel (./images/buildroot-bzimage.bin). Object sharing and Ethernet bridging start off. Grants expose data to the guest or mesh peers. Revocation blocks future transfers; it does not erase guest copies or undo effects.

Layer 5: DNS DoH Resolver, Lightweight DuckDNS TXT Writer & Wire Log

What this evidence means

The DNS name, writer key and Zone ID select an exact publication scope. Changing any of them selects another scope; it does not resolve earlier unknown writes. After reload, pin the original writer, enter its exact name and zone, then load saved publication before reconciling. Reconciliation also needs a scoped token.

Provider publication setup and reconciliation

Use a token with DNS Edit restricted to this exact zone. It is sent only to the Cloudflare API when you publish or reconcile; it is not saved or exported. Replace it here when expired or revoked. A provider acknowledgement is not DNS propagation.

Signing authority, saved trust and storage care

Save or restore a nonextractable Ed25519 key on this origin. Origin scripts can use it; only use a trusted deployment. Local rotation or revocation does not change independently trusted keys, DNS records or remote copies.

Checking saved signing authority…

Independently accepted exact trust anchor

Enter the public key and exact recent pointer digest obtained independently. Save requires this observer's admitted head. Migration uses the complete signed JSON below, and does not change the live pin. Select the new pin and restore separately. Timestamps and signatures alone do not establish trust or global recency.

Quota, eviction and public journal

Storage estimates cover this whole origin. Persistence permission is not a backup. Clearing or eviction can lose keys and unknown-write evidence. Export preserves public anchors, exact candidates and provider identities, never signing keys or API tokens. There is no automatic journal import or unknown-write reset.

No lifecycle operation requested.

Session-only keys and unsaved observer heads last only this session. Save an independently accepted recent trust anchor to restore strict succession after reload. Full pointers use multiple TXT strings, not the legacy 255-byte claim.

Paste complete signed JSON, at most 4096 UTF-8 bytes. Admission checks this exact name, independently pinned key and retained head. Restoring an anchor in the recovery vault does not change this observer.

Initializing live mesh node...