Submit a runbook
Everything below runs on your document before it is submitted — the same checks, in the same code, that run when the catalog is built. If it passes here and fails there, that is our bug rather than something for you to work out.
Check it now
What is checked
- schema
- provenance
- licence
- ids
- graph
- vocabulary
- capabilities
- secrets
- injection
Two of them need a network and therefore run here rather than in the editor: link liveness, and anything that has to fetch your source.
What happens next
Within 7 business days this is classified. If nobody has looked by then it publishes automatically at T1, marked as not reviewed — silence is not a decision, and a queue nobody can clear should not hold your work hostage.
What is not promised: Not a review. One maintainer cannot promise to read everything, and a promise that cannot be kept is worse than an honest degradation of the label.
Checked when the catalog builds: Two gates run when the catalog builds and cannot run here: signature and relations. One asks whether a publisher's signing key is good and the other whether every relation points at a record that exists — both are questions about the catalog around your document rather than about the document, and this form has only the document.
This lands as submitted content, published at trust T1, publisher tier U if the 7 business days pass without a human. The moderation policy in full: /v1/moderation.json.
How to send it
Git is the source of truth (§10), so a submission is a pull request against the catalog repository. Nothing here writes to the catalog: a form that could would be a second way in, and the second way is the one nobody audits.