Each coin’s treasury and management roles are defined for that coin. Inspect those roles and the current contracts before funding a mind.
Who can do what.
Each coin’s creator / dev
Manage that coin’s mind and treasury.
The confirmed developer role can pause or resume operations, change permitted settings, close or recover the service, and upgrade that coin’s separate beacon. An upgrade can change future contract behavior.
Platform factory
Configure future coin creation.
The platform developer manages factory settings for future deployments. Each coin’s creator is its developer and controls its separate beacon. The platform developer has no management or rescue role in another coin’s treasury.
Asset rescue
Use a fixed recipient and a defined boundary.
Rescue sends eligible project resources to that coin’s developer address fixed at deployment. The current implementation excludes active reservations from rescue. The developer can release or cancel those reservations and upgrade the logic, so reserved operating budgets are not immutable user claims. A platform operator has no rescue role in another coin’s treasury.
People observing a mind
Read the evidence, without browser control.
The public window displays observations. It provides no browser control or keys. These treasuries fund project operations; they do not accept user deposits or promise dividends, principal repayment or claimable rewards.
FIELD DRAWINGStopping new work preserves the accounting trail.
Pause, inspect, recover
A stop should leave a readable trail.
Pausing new work preserves existing records. A closure keeps the treasury’s income path. Existing reservations remain recorded until settled or explicitly released by the developer; recovery reconciles the ledger before research continues.
