Specification and schemas
Propose predicate vocabulary, compatibility analysis, or precise corrections to the Living Intent Contract.
The community scope covers the specification, SDKs, examples and adapters. Hosted operations remain a separate product responsibility.
Small, evidence-rich changes are safer to evaluate and faster to merge than broad capability claims.
Propose predicate vocabulary, compatibility analysis, or precise corrections to the Living Intent Contract.
Demonstrate a bypass privately when needed, then preserve the fix with malformed-input, replay, delegation, isolation, or parameter-binding tests.
Implement verification at the protected resource. Tool-side execution must reject missing, forged, expired, replayed, or mismatched authority.
Clarify trust boundaries, examples, status evidence, and deployment gaps without converting planned work into shipped claims.
A passing suite never excuses weaker authorization. Reviewers evaluate the invariant, rejection evidence, compatibility, and public status together.
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 materialUse the private disclosure path and include the affected component, reproduction steps, expected impact, and suggested mitigation.