Web3 / 04Evidence workspace

Read what exists. Guard what does not.

A public context
for local intent.

Verify an Intentrail run receipt, package only its digests into an unsigned envelope, or inspect an actual transaction receipt through the user's connected wallet.

Connection boundary

Address and active-network reads only. No signature, network switch, approval, payment, or transaction request is available here.

01Observable state

Four states, each kept separate.

Empty information remains empty. A local receipt never becomes a public record merely because a wallet is connected.

AddressNot observed

A user-selected public address, not verified identity.

NetworkNot observed

Active wallet context, without a switch request.

Points / optional paymentSeparate action

Local points remain distinct from the guarded 0.21 BOT review.

Write readinessUnsigned only

No signing or broadcast method ships in this release.

02Receipt to envelope

Local integrity first

Verify the run.
Reference only the digest.

The source mission stays in the selected local file. The envelope carries digest references and optional wallet-observed context; it contains no signature or transaction claim.

01Import run receipt

Choose a local run receipt to begin.

Run state
Waiting
Receipt digest
—
Manifest digest
—
02Prepare reference

Create a chain-neutral envelope after receipt verification. A connected address and active network may be observed as context, never as authorship.

Waiting for a verified receipt.

Mode
—
Envelope digest
—
Signature
None
Anchor
Not submitted
Independent envelope check

Bring the envelope back.

Recompute its digest and confirm that signature, broadcast, confirmation, and anchor fields remain guarded.

Waiting for an envelope.

03Mission anchor inspector

Read-only provider

Inspect a real receipt.
Infer nothing beyond it.

A transaction lookup can show existence, parties, block placement, receipt status, and whether exact digest bytes occur in transaction input. Byte presence alone does not prove semantic anchoring.

No transaction has been inspected.

Transaction
Not inspected
Block
—
Parties
—
Digest byte comparison
Not established
04Lifecycle

Evidence path

Local by default.
Explicit at every boundary.

  1. 01Mission spec

    Grid, constraints, and finite commands.

  2. 02Deterministic trace

    Every attempted and resulting cell.

  3. 03Local receipt

    Replay result and canonical digests.

  4. 04Unsigned envelope

    Digest reference with empty write fields.

  5. 05Future explicit write

    Outside this guarded release.

  6. 06Independent check

    Read actual public evidence without invention.

05Roles

Responsibility stays attached to the role.

No receipt replaces judgment about a physical system.

Design

Mission designer

Defines the synthetic grid, ordered checkpoints, constraints, and commands.

Review

Operator

Checks the intended sequence and stop conditions before local execution.

Recompute

Verifier

Imports the receipt, repeats the run, and checks both canonical digests.

Extend

Builder

Uses the public schemas and core without inheriting a private service.

06Builder assets

Formats that can be inspected outside this interface.

Every linked asset is a static public file. Examples are synthetic and contain no real robot telemetry.

07Release boundary

Works now / stays guarded

No hidden bridge between evidence and execution.

Works now
  • Verify deterministic run receipts
  • Create and verify unsigned envelopes
  • Observe a selected wallet address and network
  • Read block, balance, transaction, and receipt state
  • Compare exact receipt-digest bytes
  • Activate local points after a passed receipt
Stays guarded
  • No signature or typed-data request
  • No network switch or asset approval
  • No payment or transaction broadcast method
  • No claim that byte presence proves meaning
  • No public anchor or physical execution claim
  • No automatic points from connection or simulation

Optional participation state

A passed receipt first.
A separate choice second.

After importing a passed run receipt and connecting a wallet, a user may activate 100 browser-local points for that address and active network. Points are not a token, asset, cash, or promise of future value.

A connected wallet and verified passed receipt are required.

Local stateNot activated

0.21 BOT review only · confirmation guarded

Connection, simulation, points, and optional review are independent actions.
Optional upgrade review

Review without execution.

This release can explain the optional terms, but it cannot request a payment because the recipient and target network are intentionally unavailable.

Purpose
Optional local points upgrade · 100 → 200
Amount
0.21 BOT
Recipient
Unavailable in this release
Target network
Unavailable in this release
Effect on mission
None

Opening this review sends nothing. No transaction method is present.