Authority and effect verification
How grants, resource policy, connections and missions differ, and what a verified effect means.
A tool grant permits an agent to invoke a named tool. Resource policy limits where that invocation can act. A connection supplies a provider credential. A mission can add exact, expiring bounds to supported work. None of these records substitutes for the others.
Identity and authority
Townsify issues authority rather than claiming to be the source of every identity. An optional external directory can recognise agents. Workload credentials authenticate runtime machines, while role assignments govern people using the console.
Effect verification
Effect verification records what the platform established about a side-effecting call. Verified means the configured check observed the effect at its stated assurance. Pending, contradicted, unknown and unverifiable do not mean success. The check can be a receipt, read-back, settlement or internal probe.
Effect modes
The default effect mode is Observe. Contracts in shadow status do not fail work. Enforce can park a step with a pending blocking effect and resume it from recorded evidence instead of repeating the provider write. Contract coverage differs by tool, so a general effect-verification setting is not a claim that every possible action is independently checked.
Related pages
Need more help?
Open Mysaria from the console header to ask about the page you're on, or send work to an agent in your township.