Directory lifecycle
Create, suspend, and deprovision tenant identities.
Configure tenants, directory lifecycle, policies, credentials, and evidence safely.
Administrative guidance separates implemented APIs from planned connectors and emphasizes tenant isolation, version checks, and fail-closed behavior.
- Directory lifecycle
- Authentication policy
- Runtime governance
What you can evaluate
Operational guidance for 2AYE administrators.
Authentication policy
Configure passkeys, devices, and step-up.
Runtime governance
Register agents, tools, intents, and approvals.
Evidence review
Inspect audit integrity and execution receipts.
Follow Administrator support from identity to evidence.
Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.
- 01IdentityWho or what is acting
- 02IntentSigned purpose and limits
- 03PolicyDeterministic evaluation
- 04ApprovalA named human when required
- 05ExecutionSingle-use grant, redeemed at the resource
- 06EvidenceReceipt joined to the audit chain
A practical adoption path
Start with one consequential workflow. Prove the boundary before expanding.
Assess
Document the environment, threat model, and integration boundary.
Design
Select protocols, signals, policies, and failure behavior.
Validate
Test vendor-specific APIs, tenant isolation, and abuse paths.
Release
Mark available only after deployed end-to-end verification.