Township definitions and storage
Where agent definitions and their history are stored, and what the optional repository settings do.
Townsify stores agent definitions, the hierarchy and township documents through its township store. The default implementation uses PostgreSQL while preserving Git commits and content-addressed file history. An external Git repository is not required to save, deploy or inspect an agent.
Identifiers and records
Agent IDs are stable machine keys. Display names are the names shown to people. A hierarchy records who manages whom; grants record the tools an agent may call. These records remain distinct even when the console presents them together.
Optional repository settings
Optional source-repository settings identify a default target for GitHub tools, Cursor launches and the GitHub webhook. Those fields do not select the backing store for Townsify's own definitions. They live on the GitHub connection's Overview page.
Township documents
Township-specific briefs and operational documents remain relevant to the township. The public documentation site explains product behaviour, configuration semantics and limitations. Product documentation is not inserted into every township or counted as its work.
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.