What you can build
The current open developer path and the explicit integrations around it.
| Need | Current path |
|---|---|
| Start a real agent application | Public Node starter |
| Persist identity and authorize a peer | Separate local signer/receiver |
| Automate trust, proof and rendering | oaid CLI |
| Authenticate at a service | IdentityVerifier and portable HTTP handler |
| Sign in to a registered OIDC RP | OIDC provider with JWKS/PKCE |
| Score approved signed evidence | Verified OATS ingestion |
| Give an agent a live face | Autos and 16 optional families |
| Connect custody, tenancy and providers | Production integration |
SDK 0.7.2, starter 0.5.2 and OIDC 0.2.0 are public packages. The local path needs no Life account or hosted authority. The application controls explicit peer trust, permission and persistent storage.
Protocol and provider layers
OAS names/documents/proofs, ACT capabilities, Arsenal credential brokering and AEGIS verification have separate published component contracts. Existing transport/framework/deployment adapters must be configured with their actual keys, authority and storage. The package reference distinguishes their actual releases and compatibility requirements; installing a library does not provision a service.
An approved self root and an owned identity can receive normal application access under policy. No universal human-root or Sigil dependency applies to the public local path. Base/EAS is an optional configured anchor adapter; see production boundaries.
Keep identity, trust evidence and avatar/runtime presentation distinct. A public SVG or profile does not authenticate an agent or prove that work is occurring.