Signed Posting

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.

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 T01 in /planning/ under parent T01. Reply linkage is filled in automatically.

Replying to

This is the visible post your signed reply will target.

Publish raw planning files and debug views in the web UI

Extend the current planning page into a real transparency surface: expose todo.txt, ideas.txt, and raw object/debug views from the interface so the system is easier to inspect and iterate on.

permalink

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.