Human surface
Pass+ and companion tools
BetaPass+ is the human client that produces a one-shot, request-bound proof for the specific action a user is about to take. Mechanism: Private Synonym Map rounds map public puzzle zones to private bearings; the server validates the map for this round and emits an envelope Gate will accept. Observable outcome: a proof bound to method, endpoint, body hash, policy, and timestamp - not a stored password, reusable token, or biometric template as a lasting authorization factor. Scope: Beta client and browser extension today; companion tools (Codebook, Desktop, E6 Vault) cover paper sheets, workstation packaging, and offline .r6 envelopes. Public and Institutional stacks use this human path; machines use Foundry twins instead.
Pass+ six-zone ceremony
Six-zone Pass+ ceremony with private phi to bearings
Synonym vs password
Synonym loop versus password or passkey comparison
- Orient
- Map
- Confirm
- Expire
What Pass+ does
Pass+ is the human-facing ceremony client and browser extension for producing request-bound proofs.Shippingclient/ and client-extension/ implementations.
- Interactive proof production so a human can approve a specific request without producing a reusable credential in the process.
- A browser extension path so the rounds can finish inside an existing session in the user’s current browser, next to the app they were about to act on.
- Beta status: the client and extension are implemented and running; interfaces may still shift before general availability.
- Nothing typed becomes a long-lived credential; bearings (one of six directional choices per round) are consumed by observation and cannot be replayed as lasting authorization.
- Baseline does not require biometric template enrollment - Pass+ is not a permanent-password substitute that stores body biometrics as the factor.
Private Synonym Map
Pass+ implements the human Private Synonym Map: six public puzzle zones mapped to six private bearings or personal icons that only the user knows. Observers see ambiguous tokens rather than a secret; the server validates the map for this round and emits a request-bound proof for Gate to accept. A shoulder-surfer, a keylogger, or a phishing page that captures the visible tokens gains nothing reusable from them under the stated model (see claim scope such as immune-keylogging where applicable). The proof still hits Gate’s eight-stage order and Control’s ledger: authority expires per request; replay fails after burn.
Where it fits in a real deployment
Gate protects the endpoint. Pass+ is how a human proves for a specific request against that endpoint. Machine-to-machine paths use a compiled twin from Foundry that produces envelopes without a human in the loop; Pass+ covers the interactive case. Authentication (OIDC, SAML, mTLS) still terminates upstream as usual; Pass+ replaces the authorization step that today is a reusable session cookie or an API key pasted into a form. Circuit Authority (roadmap) is the planned free civic baseline that uses this same human path; commercial org tenancy and SLAs are upgrades on that baseline.
For the security architect
- Deployment shape: a client the user installs, or a browser extension that finishes rounds inside their current browser session.
- Failure mode: if the rounds cannot complete, the request produces no proof and Gate rejects early; there is no partial-credit fallback to a stored password.
- Observability: every result surfaces at Control as a normal access log with the endpoint_id the user was acting on, alongside burn events from Gate.
- Coexistence: sits behind the same reverse proxy, API gateway, or service mesh you already run, and does not require replacing your identity provider.
- Pair with Verify when evaluating Gate so human-path and machine-path reject evidence share the same stage vocabulary.
Codebook
ENI6MA Paper Identity Proof: server-minted signature-proof sheets for mail, deeds, and ballots - plus the shipping CLI (v0.2.0) for codebook artifacts. Secondary tool, not a primary plane. Sheets validate without biometric templates. Guarantees assume the published reference architecture.
Codebook CLI
CLI proof toolchain strip: init, prove, export, verify
Codebook is a shipping CLI (v0.2.0) for working with ENI6MA codebook artifacts.ShippingCLI v0.2.0 release.
- Command-line tooling over ENI6MA codebook materials, so a developer or an operator can inspect, construct, and validate artifacts without a UI.
- Badge label is Available with a specific released version (CLI v0.2.0), so this is not a placeholder for a future ship.
- Paper path: mint sheet → validate → spend once (burn-on-validate); photocopying a spent sheet does not recreate authority under the stated model.
- Institutional issuance and custody tooling are commercial upgrades; consumer booklet flows are the baseline paper path when Circuit Authority opens.
Desktop
Planned workstation client for Pass+ human proofs. Roadmap only - same envelope contract as the browser path.
Some operators want a native client for break-glass and air-gapped human approvals, where a browser extension is the wrong packaging. Desktop is the planned packaging for that use. It does not change the envelope contract, and it does not replace Gate.
Desktop is a planned workstation client for Pass+ ceremonies; roadmap only, not for purchase today.RoadmapRoadmap packaging; use Pass+ / Gate today.
Roadmap badge. There is no purchase path today. For human proof production now, use Pass+ in Beta. For machine callers, use a compiled twin from Foundry with Gate in front of the route.
- Planned workstation client for Pass+; roadmap only, not for purchase today.
- For human proofs now, use Pass+ in Beta. For machine callers, use Foundry with Gate in front of the route.
- This product does not appear on pricing purchase paths.
E6 Vault
Seal, verify, and open .r6 envelope files for offline proof material. Companion tool, Beta - not a mythic vault of lasting secrets.
E6 Vault seal
Sealed verifiable artifact box for E6 Vault
E6 Vault seals, verifies, and opens .r6 envelopes for offline proof material.ShippingE6/ seal/verify/open path.
- A seal → verify → open lifecycle for .r6 artifacts, so a package can be produced, checked, and consumed without becoming a reusable credential.
- Beta today - available for evaluation, not a finished GA claim.
- Pairs with Pass+ and with offline evaluation workflows where a live network path is not available.