2AYE
Developer center

Build the first governed workflow with working contracts.

Use repository-backed JavaScript, .NET, Python, Go, and Java SDK implementations, API references, quickstarts, and architecture guidance. Package-registry publication remains separate release work.

  • Quickstarts
  • SDK implementations
  • API reference
What you can evaluate

A clear path from concept to integration.

01

Quickstarts

Follow a task-oriented governed-action sequence.

02

SDK implementations

Use JavaScript, .NET, Python, Go, or Java against the same authorization contract.

03

API reference

Understand runtime evaluation and receipt contracts.

04

Architecture guides

Design enforcement and failure behavior deliberately.

The enforcement path

Follow Developer center 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.

  1. 01IdentityWho or what is acting
  2. 02IntentSigned purpose and limits
  3. 03PolicyDeterministic evaluation
  4. 04ApprovalA named human when required
  5. 05ExecutionSingle-use grant, redeemed at the resource
  6. 06EvidenceReceipt joined to the audit chain
Deterministic decisionsSingle-use, exact-action grantsHash-linked evidence
A practical adoption path

Start with one consequential workflow. Prove the boundary before expanding.

01

Learn

Understand tenant, identity, intent, and decision concepts.

02

Run

Execute the local reference workflow.

03

Integrate

Connect a real service boundary.

04

Verify

Test denial, approval, revocation, and evidence paths.

Review the trust architecture
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
Developers | 2AYE