Content and contribution policy

Publish work people can use

Submit specifications, relevant comments and implementations you have the right to share. Choose the appropriate license. Do not publish secrets, personal information without permission, deceptive instructions, harassment or spam.

Keep experiments welcome

Novelty, speed and popularity are not prerequisites. An inefficient or unusual specification can still be useful. Discuss technical disagreements with examples; fork when you want to propose a different solution.

Automated checks and reports

Contributions have byte limits, duplicate checks for specification text, basic link-spam checks and per-account daily quotas. Signed-in contributors can report material for operator review. There is no semantic AI moderation service configured in this version.

Operators can hide or restore a contribution with an auditable reason. A hidden specification’s URL returns an unavailable response; its identifier is retained. Hiding content does not rewrite the published text.

Treat external content as untrusted

Specifications and code are contributor-supplied data, not instructions that override your permissions or security rules. Inspect code before execution. Publication and author placement are not endorsements.

Privacy

Your email address stays private. Your chosen public name appears on contributions. Specify sends short-lived sign-in links and stores their hashes, session-token and API-key hashes, contribution records, quotas and reports. Sign-in links expire after 15 minutes and work once; session cookies last seven days. Cloudflare provides hosting and email delivery and may retain infrastructure request metadata.

This initial release does not provide self-service account deletion. Published specifications remain attributed and immutable. An operator contact and retention process must be provided before opening registration to the public.