Permit verification

Access is by permit. Paste the token from your email — or click the link from your email and the page detects it automatically. Capabilities ship via permit; the surface composes itself at view time from what the bearer is permitted to see.

verificationchecking…

principal—

rung—

permit—

verifier—

Present your token

Paste the 64-character hex value from your email and press verify. Or click the link in your email — this page reads ?t= and stores the token automatically.

token

The token lives only in your browser (localStorage.espd_token). Its public counterpart and a private value sit in the register; the private never leaves the server.

How it works

Receipt by email. The architect issues a token permit in the register, then emails you the public value. The matching private stays on the server.
Two ways to present. Click the link — the page captures the token into localStorage.espd_token. Or paste manually above.
Verification at view time. The page asks /permits/active.json for active permits and matches your token. PUBLIC direct-match first; sha256 TOKEN_SHA256 fallback for legacy.
Capabilities ship with permits. Once verified, the page fetches a capability_package permit and inlines only those entries permitted at your rung. No package permit, no leader area — the toggle is the permit's presence.
If your token doesn't match. Reach out to the architect; a self-service request path is queued.

Permit-gated surface. Capabilities are List-shaped entries inside a capability_package permit; without that permit in the register, the leader area is empty regardless of your rung. The current active mode is shown in the top-right when sandboxed.

Permit verification

Team

Announcements

Leader actions

Rename history