2AYE
Guides, reference & supportCapability status

Documentation

Connect a protected receiver

Configure trust, resource bindings and a sole protected mutation path, then exercise refusal and recovery.

Choose the execution boundary

Name the target resource, environment, tool, action and accountable operator. Keep identity-provider credentials separate from action authority. The agent must not choose a weaker redemption mode.

Configure trust explicitly

Provision stable issuer trust, pinned receiver verification material, service identity and TLS. Private keys and service credentials belong in operator-managed secret storage. Public documentation cannot provision these values for you.

Prove refusals and rightful success

Test forged or expired grants, wrong tenant, changed parameters, replay, concurrent execution and unavailable storage. After refusal, demonstrate legitimate success with valid unspent authority. Reusing a spent grant does not test parameter binding.

Reconcile uncertain effects

For remote providers, persist execution identity and attempt state. A timeout may follow a committed effect. Read authoritative provider state before retrying or declaring failure; keep unresolved outcomes visible.

Your governed workflow

Bring the next consequential action under control.

Show us the actor, protected resource, and action that must never execute without exact authority. We’ll map the decision and evidence path with you.

Discuss your workflow Read the implementation guide
Connect a protected receiver | 2AYE Documentation