2AYE
Guides, reference & supportCapability status
Contributor guide

Make authority harder to bypass—and easier to verify.

The community scope covers the specification, SDKs, examples and adapters. Hosted operations remain a separate product responsibility.

Where to contribute

Choose one reviewable boundary.

Small, evidence-rich changes are safer to evaluate and faster to merge than broad capability claims.

Specification and schemas

Propose predicate vocabulary, compatibility analysis, or precise corrections to the Living Intent Contract.

Security and rejection tests

Demonstrate a bypass privately when needed, then preserve the fix with malformed-input, replay, delegation, isolation, or parameter-binding tests.

SDKs and enforcement adapters

Implement verification at the protected resource. Tool-side execution must reject missing, forged, expired, replayed, or mismatched authority.

Documentation and evidence

Clarify trust boundaries, examples, status evidence, and deployment gaps without converting planned work into shipped claims.

Required evidence

The contribution contract is fail-closed.

A passing suite never excuses weaker authorization. Reviewers evaluate the invariant, rejection evidence, compatibility, and public status together.

  1. 01Name the invariant or acceptance criterion the change preserves.
  2. 02Include a useful happy path and at least one rejection path proving the bypass remains closed.
  3. 03Fail closed for malformed input and unavailable deterministic dependencies.
  4. 04Update the public specification and compatibility evidence when a contract changes.
  5. 05Never include secrets, real customer data, or unsupported partnership, certification, or availability claims.
Compatibility checks

Test your implementation against the 2AYE formats.

Formats, verification examples and rejection vectors are shared on request under NDA. Include the version tested, expected results and any environment limitations with your submission.

Request verification material
Security reports

Never publish a suspected vulnerability as a discussion or pull request.

Use the private disclosure path and include the affected component, reproduction steps, expected impact, and suggested mitigation.

Open disclosure guidance