Turn a useful observation into a contribution.

Choose a focused problem, explain the evidence, and prepare a brief that another reader or maintainer can assess.

Clarify a page

Identify the passage, describe what is confusing, and suggest a precise revision.

Documentation guide

Review an assumption

Show the method, inputs, expected result, and what a different interpretation would change.

Evidence guide

Test an implementation

Include a release identifier, reproducible steps, actual output, and the behavior you expected.

Implementation criteria

Prepare a contribution brief

This tool creates a Markdown file on your device. It does not send a submission or store your draft on the server.

Type of contribution

Related resource

Related resource: general project contribution.

A short, specific title Problem and who it affectsProposed improvementEvidence and verification

Enable JavaScript to generate a brief, or follow the written contribution guide.

Apply, review or submit

Read the Society review rules, apply for reviewer or administrative responsibilities, and find calls for standards evidence and every journal section.

Participation & submission calls

What happens next?

Review your brief
Check its scope, references, and examples. Keep an exact revision for any standard you discuss.
Use the available source channel
Visit the repository page. Repository participation may require access; downloading a brief does not submit it.
Keep decisions traceable
Methodology and governance changes follow the RFC process. A proposal is separate from an approved change.

For time, infrastructure, and other support, read the Foundation support guide.