The node

Who this participant is, and what it refuses to be.

Refresh

—

ALeave → Verify → Rejoin

A real recovered community space, exported through the banked export contract. Verification runs in your browser, against the bytes you received — not because this node says so.

1  Fetch the exported bundle 2  Verify it here in the browser 3  Rejoin the fabric 4  Inspect assets, principals, authority 5  Fetch the asset bytes and re-hash them here 6  Rejoin again (must not duplicate)

—

BBuild → Declare → Sandbox → Install → Invoke → Revoke

A capability published by a builder who is nobody in particular, installed by a member, and refused the moment it reaches past what it declared.

Run the whole sequence

—

CWhat this node does for you — and what it cannot

Four things that were only ever proven by a test suite. A claim you cannot check yourself is a claim you are taking on trust, so each one is a control.

1  Submit an event — watch the contract accept and refuse 2  Verify with the fabric unreachable 3  Prove your own write survived the process 4  Who acted — human, intelligence, or neither

—

The four graphs

Activity is evidence. It does not become a relationship, a belief or a capability without a governed act — and this shows the refusal, not just the success.

Run the boundary test

—

What this node claims, checked against what it answers

The node publishes a profile of every surface it serves. Nothing here trusts it — your browser asks each claimed surface whether it really answers, and asks a few it does not claim whether they answer anyway. A profile is a description: it is not a certification and it grants nobody anything.

Check the node's claims against reality

—

Who may connect, and on what terms

A registration names a ROLE, never a product, and it may not grant itself admission. This submits one and shows the node accepting what the contract allows and refusing what it does not — including a document that tries to declare itself irreplaceable, or preferred.

Submit registrations — watch the terms hold

—

State that names no space belongs to no space

Two spaces, on one node, in front of you. What you write to one must never appear in the other — and a space you have never written to must hold nothing at all, rather than inheriting somebody else's history.

Write to two spaces and check nothing leaks

—

Check that this node has not rewritten its own history

A journal is supposed to only ever grow. Whether the file on disk is append-only is not something you can find out from here — but whether the history this node shows you has been edited underneath you is, provided you take the first reading. That is what this does: reads, writes, reads again, and folds.

Take a reading, write, and check the past is still the past

—

Verify a signed conformance result

A conformance run can be signed and handed to someone who did not watch it. This verifies one in your browser — the signature, the digest over every recorded verdict, and the statement that it confers no authority — then alters it in front of you so you can watch the check fail.

Verify a signed result, then tamper with it

—

Open rulings

Represented in their current gated state. This node will not pretend a decision has been made.

Show

—

What this cannot show you, and who alone can change that

Everything above is something you can make happen yourself. This is the rest of the account: how many capabilities there are, how many can be demonstrated, and every one that cannot — with the gate that holds it. A gate is not a defect and not a promise; it is a decision that belongs to somebody, and that somebody is named.

—