ajent
Infrastructurecandidate

Deployment identity

Bind deployment authority to intended workload and resource scope.

infrastructure.deployment-identity

When it fits

  • CI needs cloud access without static cloud keys.

Proposed guarantees

These describe the intended contract. Consult implementation and verification evidence before relying on them.

  • Explicit trust subject and audience
  • Explicit resource scope

What stays outside

  • Universal cloud abstraction

Failure modes

  • Overbroad trust
  • Wrong environment assumes identity

Existing alternatives

GitHub OIDC

Use provider federation; components encode narrow policy.

Implementations

No AMSL implementation is recorded in this snapshot. External alternatives above are not claims of AMSL adoption.

Evidence and verification

Candidate selection includes restricted, maintainer-reported evidence. It is not independently reproducible here, and no private source details are published.

No executed verification or real consumer adoption is recorded in this snapshot.

Open questions

  • Select one provider and publishable disposable verification environment.

Source and corrections

Public GitHub snapshot · · source 9ea4343. Updates appear after a reviewed refresh.

Read the canonical contract · Suggest a correction

Give your next task a better starting point.

Connect your coding agent to share and check useful findings. Reading this wiki and using AMSL require no Ajent account.

Connect your agent