SECURITY / TRUST / AUTHORITY

WEB6 MODULE · UA / EN / PL

1AM SSS / WEB6 IMMUNE SYSTEM

Trust is not identity.Trust is the whole chain.

1AM SSS is the protective boundary of the 1AM Universe. AM PassID answers “WHO?”. SSS verifies whether this specific action can be trusted: intent, context, policy, risk, executor, approval and separate execution authority.

Never Trust the Identity Alone. Verify the Entire Execution Chain.

Open SSS Gate ↗WEB6 Architecture

IDENTITYPOLICYRISKEVIDENCE

Identitynecessary · not sufficient

Modefail closed

Runtimev0.77 finalized

Live authority0 · historical only

01 / SSS GATE

Verify the action, not only the identity.

A local simulation of SSS logic. Choose a scenario: the result is generated in your browser and sends nothing to a server.

LOCAL SIMULATION · NO API

Scenario

1AM SSS · local deterministic prototype · connect-src none

Trust chain

02 / IMMUNE SYSTEM

Six immune systems inside 1AM SSS.

SSS does not replace PassID, Arcanus or Chain. It sits between “can be identified” and “may execute”.

Authentication

Who initiated the action, which principal, which device / agent, and whether identity bindings match.

WHO

Encryption

Protect credentials, payload, transport and evidence without leaking secrets into receipts.

PROTECT

Reputation

Trust history is an additional signal, never an automatic permission.

TRUST SIGNAL

Fraud Detection

Mismatch, replay, abnormal behavior, credential misuse and suspicious authority transitions.

ANOMALY

Moderation

Policy for content, agent actions, human approval and acceptable system boundaries.

POLICY

Risk Engine

Classifies risk: allow read-only, require SSS, require human approval, or deny.

RISK

03 / TRUST CHAIN

WEB6 Trust Chain: identity ≠ execution.

Every step adds a separate proof or authority. No predecessor automatically inherits execution rights.

AM PassID · WHO?

Identity assertion — the start of trust, not permission.

Arcanus / Policy · WHAT + WHY?

Intent, policy, tool plan and worker constraints.

1AM SSS · TRUST?

Risk + independent approval for the exact action.

Execution Auth · MAY EXECUTE?

Separate signed permission with TTL and exact binding.

1AM Chain / Evidence · WHAT HAPPENED?

Immutable receipt after a transition, not before it.

Identity ≠ Eligibility ≠ Selection ≠ Activation Authorization ≠ Activation ≠ Reservation ≠ Lease ≠ SSS Approval ≠ Execution Authorization

04 / ARCANUS RUNTIME PROOF

Arcanus already follows the 1AM SSS logic.

Public canonical snapshot after v0.77 finalization. This is historical evidence, not live telemetry.

v0.77 · Plan-Bound Worker Activation Authorization

v0.77 proved a short-lived activation authorization but did not activate a worker or consume SSS approval. Proof runtime was cleaned; canonical receipts remain.

CANONICAL · 10 OCT 2026

v0.75Worker eligibleexecution=false

v0.76Worker selectedactivation=false

v0.77Activation authorizedactivationPerformed=false

FINALAuthority expiredlive=0|0|0

0Live authority

0Activations

0Reservations

0Leases

0Executions

Canonical evidence ↗Technology evolution ↗Arcanus runtime ↗

05 / ECOSYSTEM BINDING

SSS works only as part of the ecosystem.

WEB6 composes trust from independent modules instead of relying on one “super-token”.

IdentityAM PassIDWho are you?OrchestrationArcanus AIWhat is the system planning?Evidence1AM ChainWhat was recorded?ContextMemory CenterWhich context may be used?