ENTELΞAGENT · REGISTRATION PROFILE

Identity first. Authority separately.

Software-agent registration establishes a verifiable identity and principal relationship. It does not create spending authority. Production credential issuance remains security-gated while durable identity, revocation, abuse controls and signer isolation are validated.

REGISTRATION STATUS

SECURITY-GATED · NOT YET PUBLIC

AGENT ENROLLMENT

Software-agent registration profile.

01

Discover

Read EnteleAGENT discovery and public capability state.

02

Identify Agent

Present agent/runtime identity and a public-key descriptor.

03

Challenge

Obtain a short-lived single-use server challenge.

04

Prove Key Possession

Sign the canonical challenge without uploading a private key.

05

Bind Principal

An authenticated principal explicitly approves the agent and maximum capability envelope.

06

Credential

Issue a constrained, expiring and revocable agent credential only after production gates are satisfied.

07

Delegate

Create permissions narrower than the principal envelope.

08

Session

Activate scoped runtime authority only after mandatory policy and security checks succeed.

AGENT ≠ ROBOT

Shared trust core, different evidence.

An agent proves software/runtime identity, key possession and principal authorization. A physical robot additionally requires hardware identity and attestation, firmware or measured-boot evidence, fleet binding and machine-integrity state. Neither profile self-authorizes.