Locality · no implied transmission

A person can be reachable only through a real relationship path.

Installing, reading, or authoring locally does not notify Aaron, create a duty to respond, or move a claim beyond your Temple.

Conversation

Ask Aaron about Claimipedia

A broad human conversation after you have formed and locally reviewed your question. A reply is correspondence—not truth, admission, endorsement, or authority over your Temple.

Prepare a message → · Retrieve a response

Open · explicit send only
Remedy

Request remedy from the release steward

A narrow path for a misleading assurance page, unsafe release artifact, or boundary failure. Aaron has accepted the release-steward role with a 24-hour response target. If flood reaches 10 people per day over three days, an alternative mechanism will be provided.

Accepted · 24-hour target

What an honest path must do

1 · Local draftYour words remain on your device. Drafting creates no relationship or notice.
2 · Transmission previewShow the human recipient, Claimipedia custody, Discord metadata, exact fields, retention, and expected response.
3 · Explicit sendOnly a separate human action may place the message in the Claimipedia steward inbox.
4 · Received, pendingThe inbox returns a private receipt. A Discord notification is not reading, agreement, or a promise to act.
5 · Human responseA response must identify whether it is Aaron personally, a delegated steward, or an automated service.
6 · Local decisionYou may accept, reject, revise, or retain the response as correspondence. It never enters your Temple automatically.

The admitted boundary

This page passes kenotic assurance. It admits the exact first-party inbox and metadata-only notification boundary without admitting Claimipedia production or granting authority beyond steward correspondence.
Sourcery menuShow Aster