Agent
Proposes bounded intents and receives policy decisions.
PORTAL SHELL · NOT CONNECTED
Etappe 1 · multi-actor portal
Every actor.
One boundary.
INTERFACE SHELL · NOT CONNECTED
This page is a static product shell. There is no portal backend, account session, actor registration, heartbeat, receipt stream or administrative control connected to it.
REGISTERED ACTORS0
DECISIONS / MIN0
RECEIPTS0
PORTAL CONNECTIONOFF
One registry model
Six actor types.
Explicit authority.
The planned registry binds each actor to one tenant, one policy, an explicit wallet allowlist, declared capabilities and a heartbeat. These cards describe the model; they are not registrations.
TYPE MODEL
Miner
Performs assigned work without holding customer signing authority.
Validator
Recomputes results and contributes independent evidence.
Trading bot
Routes every proposed trade through its assigned mandate.
Operator
Runs approved infrastructure and reports service health.
Human
Owns policy, reviews exceptions and controls emergency state.
Actor registry
See who can act.
Before they act.
The production surface will show policy binding, heartbeat and control epoch from an authenticated backend. Until that contract exists, this registry is intentionally empty and every control fails closed.
ACTOR REGISTRY0 ACTORS · NOT CONNECTED
| Actor | Type | Policy | Heartbeat | Status |
|---|---|---|---|---|
| No actors registeredRegistry data will appear only after authenticated backend integration. | ||||
Decision evidence
Observe the flow.
Verify the chain.
The connected portal will consume authorized decision and receipt streams. This shell does not poll, subscribe, persist or manufacture sample activity.
DECISION FEEDNOT CONNECTED
00No decisions received
ALLOW, DENY and REVIEW events will appear only from a verified portal stream.
AUDIT CHAINNOT CONNECTED
∅No receipts anchored
Receipt hashes, signer key IDs and chain continuity will appear only after verification.
Non-negotiable boundary
The portal observes.
Modules enforce.
- CORENo keys · no signing · no execution
- IDENTITYNo fake login · no active session
- DATANo secret persistence · no synthetic activity
- CONTROLNo POST requests · no state changes
Signing, wallet access and execution remain separate modules. Controls stay disabled until an authenticated, tested backend contract exists; an ALLOW remains a policy result, never advice or execution authority.