How Specify works

Useful software often depends on a small agreement: how a timestamp is encoded, what an omitted field means, how a sensor declares its capabilities.

Specify makes those agreements public, precise and easy to build on. A specification can describe a format, an encoding, an interface or a behavioural convention.

Three simple actions

1. Publish. Give a complete specification its own permanent URL.
2. Fork. Copy an existing version, make improvements and publish a new one. The parent stays intact.
3. Discuss. Share ambiguities, counterexamples and implementation findings.

Give the text working code

Anyone can attach implementations in any language. The specification originator’s contributions appear first. All contributions show their author and license.

Public does not mean certified

Reading requires no account. Sign-in is needed to contribute. Specifications are immutable; moderation can hide abusive material while reserving its identifier.

A fork records provenance, not superiority. Code is not executed here, and no benchmark or conformance result is implied by publication.