Contribution guide

Contribute evidence

Propose the smallest truthful compatibility statement. Maintainers review source wording, exact surface identity, conditions, and whether the statement is stronger than its evidence.

1. 01

   Define the capability

   Use a stable, vendor-neutral ID; name the specification revision, role, authority, source, parent, children, and aliases.

2. 02

   Name the target

   Identify one exact web, desktop, IDE, CLI, or cloud surface. Use a release/build where available or a dated hosted observation.

3. 03

   Record the environment

   Select an environment profile and retain plan, policy, region, authorization, transport, runtime, preview, and feature-flag conditions.

4. 04

   Attach evidence

   Add a stable resource ID, public HTTPS source, evidence class, review date, locator where useful, and a concise factual note.

5. 05

   Validate and preview

   Run schema, referential-integrity, formatting, test, build, and browser checks. Review the generated feature and harness views.

6. 06

   Publish without rewriting history

   Future changes should supersede a statement and create a dated change event. Vendor attestation remains distinct from independent reproduction.