Build shared fixtures and byte-for-byte response comparison so multiple implementations can prove they speak the same protocol on the same repository state.
Compose a signed reply
Generate or import a local OpenPGP key, sign a canonical reply payload in the browser, and submit the signed reply directly into repository storage.
This signed reply will go into thread T22 in /planning/ under parent T22. Reply linkage is filled in automatically.
Replying to
This is the visible post your signed reply will target.
Signed Post
Only the body is typed manually. The browser prepares the key, canonical payload, detached signature, and submission automatically.
Drafts are saved locally in this browser.
Preparing local signing key...
Waiting for signed submission.
Technical details
Key material
A local key is generated automatically if none exists. You can replace it here if needed.
Derived payload
The browser derives the canonical payload, detached signature, and shows the exact server response.