Institutional control
Aetheria operates inside the institution's identity, data, security, policy, infrastructure, and recovery boundary—not as an opaque shared control plane.
Supported profiles
Each profile includes clean installation, configuration, durable storage, backup and restore, upgrade, rollback, repair, removal, and an explicit offline boundary.
A complete local system for a governed operator environment on an independently managed computer.
An organizational deployment serving governed users across a controlled private network.
Deployment topology
Local users reach Aetheria through the institution's controlled edge. Provider and connector access is configured, credentialed, and observable. Local workflows never switch silently to a public provider.
Operational ownership
A supported installation remains operable beyond first boot. Administration, provider controls, backup, restore, upgrade, rollback, health, evidence export, and removal are part of the deployed system.
Accounts, roles, delegations, and revocation remain inside the institutional trust boundary.
Ingestion, OCR, retrieval, citations, holds, retention, and redaction preserve their source relationships.
Approved model providers use declared credentials and network paths without hidden fallback.
Governance records and assurance evidence survive the operational workflow that produced them.
Reconciliation, rollback, repair, restore, and revocation are explicit operating procedures.
The institution retains a defined path to export, remove, and verify the installed system.
Municipal operations
Municipal records become a governed working memory: source-grounded, permission-aware, citation-first, and subordinate to the people responsible for adoption and action.
Documents, scans, minutes, policies, procedures, and attachments enter with provenance.
OCR and document processing preserve page and source relationships.
Answers carry citations, conflicts, and abstention when the record does not support a claim.
The responsible municipal role resolves policy, records, legal, and operational authority.
Approved work enters the authorized workflow with a governance receipt.
Governed domains
Each domain brings distinct policy, evidence, confidentiality, retention, and human- authority requirements onto the same Aetheria control spine.
Records, policy, minutes, workflow, and accountable adoption.
Deployment boundaryCompartmented support with explicit human command authority.
Deployment boundaryGoverned advisory and operations with licensed human authority preserved.
Deployment boundaryDocument, research, and workflow support under attorney and client authority.
Deployment boundaryGoverned intake, evidence, underwriting, and claims workflows.
Deployment boundaryConsequential action requires accountable authority.