Editor's contact page
How to reach the editor.
How the editor reads incoming work, what gets answered first, and what does not get a written reply. If your question is answered in v0.1 or the v0.2 RFC, it is already answered.
Three ways in
GitHub issues ›
Anyone with a reproducible problem in a reference implementation, a conformance vector that fails, or a concrete spec ambiguity. This is the front door.
Latency · 3–10 days, rolling.
Ignored · feature wishlists, vendor pitches, "have you considered…" without a vector.
Label rfc-v0.2
Comments on the open RFC. Use the issue template. One concern per issue. The editor reads every comment on this label during the window.
Latency · under 14 days during the comment window; otherwise rolling.
Ignored · comments filed after 2026-05-22 23:59 UTC. Those wait for v0.3.
For things that genuinely cannot be public: confidential review of a clause before disclosure, institutional procurement, EU AI Act notified-body queries, and paid Studio 11 work.
Latency · 7–21 days. No same-week guarantees.
Ignored · partnership intros, growth pitches, link-trade requests, "quick call?" without a one-paragraph brief.
Editor's calendar
Office hours open weekly post-freeze. Applications via Tally form (link TBD).
Written-question reply turnaround for non-office-hours questions: 30 minutes.
Office hours are scheduled through the application form. There is no direct booking link.
What we are not doing this quarter
- We will not review your hash function.
- We will not endorse, certify, or "bless" a product, model, or eval harness.
- We will not add a field because one vendor needs it. File an RFC with two independent implementers behind it.
- We will not debug your CI. The four reference implementations pass 20/20 vectors; start there.
- We will not sign NDAs to look at a deck.
- Advisory engagements are quoted off-list. Write from an institutional address with a docket reference.
Press, institutional, podcasts
Press. Quotes and background are given to journalists with a published byline at an outlet that runs corrections. Send the angle and the deadline in the first email. If the deadline is shorter than 72 hours, the answer is no.
Institutional. Notified bodies, regulators, and procurement teams should write from an institutional address with a docket or reference number. We will reply in writing only. We do not attend exploratory video calls.
Podcasts. We do podcasts twice a year and the next slot is autumn. Don't email; we'll announce. Podcast pitches are answered after the v0.3 freeze.