2AYE
Guides, reference & supportCapability status

Community guidance

Community guidelines

Contribute clear evidence, treat people respectfully and keep sensitive information out of shared examples.

Choose an available participation path

Use the contributor guide to propose documentation, specification, SDK or verification improvements. Public discussion publishing and moderation are not currently available. Contact 2AYE to discuss a contribution or request repository access.

Read the contributor guide

Keep discussion useful and respectful

Focus on the technical behavior and evidence. Explain the affected version, expected behavior, actual behavior and environment without personal attacks, harassment, spam or misleading claims. Distinguish a proposed design from an implemented or independently verified capability.

Protect people and organizations

Share only sanitized examples you are authorized to disclose. Remove credentials, tokens, private keys, recovery codes, verification links, employee information and customer records. Use disposable identities and resources when preparing a reproduction.

Report vulnerabilities confidentially

Do not publish suspected bypasses, exploit details or live system identifiers in a contribution or public channel. Start with confidential disclosure so the affected boundary can be investigated safely.

Open security disclosure

Make improvements reviewable

Explain the authorization invariant being preserved, include a reproducible refusal case and keep compatibility and capability claims accurate. A green test suite does not justify weaker enforcement. Maintainers review contributions through the agreed repository process.

Request verification material