# Sigmar AOS — Security, Privacy and Trust > Official guide to how Sigmar AOS protects people, Personas, Guilds, DNA, information and governed activities. ## Security begins with the person Sigmar AOS is built around a simple principle: **participating in a shared activity does not mean giving up control of personal information or identity.** People use AOS through Personas. A Persona represents a particular part of someone's life or work, such as My.Health, My.Career or My.Finances. Each Persona develops its own DNA from knowledge, skills, memory, experience, behaviour and Flows. AOS protects these parts of a person's life separately. Joining a workplace Guild does not automatically open a private health diary to an employer. Sharing selected information with a doctor does not give an entire medical practice unrestricted access to the patient's Persona. Purchasing access to compiled DNA does not transfer ownership of the source Persona or reveal every memory that helped it develop. AOS combines **security levels, permissions, ownership, purpose and governed execution**. Each has a different role. A security level determines whether a request meets the required sensitivity threshold; permissions and ownership determine whether the requester is actually allowed to access or act on the information. ## Nine security levels AOS uses one ordered set of nine security levels. They apply consistently to information and the activities that involve it. | Level | Name | What it generally protects | |---|---|---| | 0 | **Public** | Information deliberately made available to everyone, such as a published description of a Guild. | | 1 | **Standard** | Ordinary AOS information and everyday activities that are not public. | | 2 | **Confidential** | Information intended for a limited group, such as internal business plans or private project discussions. | | 3 | **SensitivePersonal** | More sensitive personal details and observations that require greater care. | | 4 | **Financial** | Financial records, obligations, transactions and related protected information. | | 5 | **HealthGuarded** | Personal health observations, medical histories and other protected health information. | | 6 | **LegalPrivileged** | Information subject to heightened legal confidentiality or privilege protections. | | 7 | **GovernmentRestricted** | Restricted government information and associated activities. | | 8 | **SovereignSecret** | The highest category of protected information in the AOS classification model. | These levels are ordered, but **a higher level is not a universal pass**. A person who meets the level required for a record still needs permission to see it. Likewise, a person who owns a record cannot bypass a higher classification requirement simply by being its owner. The names describe AOS's classification model. They do not, by themselves, confer a government security clearance, professional qualification or legal privilege. ### The normal starting level **Standard is the default classification for newly created AOS information, Personas and Guilds**, including the initial records AOS creates for someone during onboarding. A person or organisation can use a more protective classification where the nature of the information requires it. The absence of a declared caller security ceiling does not grant unlimited access. AOS applies a default ceiling of **SensitivePersonal** in that case. Requests for higher-classified information require the appropriate declared authority and permissions. Classification influences how AOS applies protections including access, encryption, retention, export, learning eligibility and audit. It is one part of the complete security decision, not a replacement for consent or authorisation. ## How access decisions work AOS evaluates the security of the Persona making a request and the protection required by the destination or activity. If a Persona's security level is below the level required to join a Guild or perform an action, **the AOS application rejects the request and the AOS engine independently rejects it**. The protection does not depend on a screen hiding an option or a user voluntarily following a rule. Meeting the required level is only the first condition. AOS also considers whether the Persona has the relevant membership, ownership rights, permission and authority for the particular activity. For example, two employees may both be authorised to work with Financial-classified information. One may be allowed to prepare a payment, while another may be allowed to approve it. Neither automatically gains access to the other employee's personal financial records. **Classification answers whether the sensitivity threshold is met. Permission answers whether this particular action is allowed.** Both matter. ## Personas keep different parts of life separate A person can use different Personas for different purposes: - **My.Health** records personal health observations and experiences. - **My.Career** develops professional capabilities, working experience and relevant career history. - **My.Finances** manages financial information and related activities. - A family or community Persona can participate in a shared Guild without revealing unrelated personal information. Each Persona has its own context, DNA and applicable protections. An invitation to a Guild is not permission to inspect every other Persona belonging to the same person. When information is shared, AOS applies the permissions and protections relevant to that specific information and purpose. A limited view can be shared without disclosing the entire underlying Persona or DNA. ## Guild membership is not unrestricted access Guilds bring Personas together for a common purpose. They include families, community groups, professional specialists, business departments and Business Guilds that coordinate several teams or organisations. A Guild can require a minimum security level for membership or for particular activities. **Both the app and the engine reject attempts that do not meet the required level.** A valid invitation does not override this check. Even authorised Guild members see and do only what their membership and permissions allow. A receptionist, clinician and practice administrator can belong to the same Doctor Guild while having different responsibilities and access to patient information. Guild participation does not transfer ownership of a member's source DNA. A Guild develops its own DNA through authorised collective work, while members retain their separate identities and rights. ## Healthcare: sharing Health DNA with a Doctor Guild Imagine someone who has been recording recurring headaches and muscle pain through My.Health. They note when symptoms appear, how long they last, how they slept and other circumstances they consider relevant. AOS organises these observations within the person's developing Health DNA. Over time, the history may help reveal patterns worth discussing with a medical professional. A pattern is not proof of a medical cause, and AOS does not replace clinical diagnosis. The person can **explicitly authorise a relevant, limited view of Health DNA** to be shared with a Doctor Guild (`DRGUILD`). Qualified clinicians can then review the information they are permitted to see, ask questions and decide on examinations, treatment or further investigation. Health information is protected at the **HealthGuarded** level. A request that fails the security threshold is rejected. Meeting the threshold still does not grant every Guild member access to the patient's entire medical history. The Doctor Guild can develop its professional practices through permitted experience, but **the patient's private observations do not automatically become Guild-owned DNA or material available for unrestricted learning**. Sharing, retention and learning remain subject to the patient's permissions and applicable protections. ## Employee wellbeing: a Business Guild learns without reading private diaries An employee might use My.Career to reflect on workload, collaboration, achievements and difficult relationships at work. They might separately record personal stress or health observations through My.Health. These experiences contribute to the employee's own DNA. They do not become unrestricted employer records simply because the employee belongs to a Business Guild. Where employees have authorised appropriate use of their observations, AOS can help a business recognise wider workplace concerns. For example, recurring reports of exhausting weekend shifts may support a recommendation to review staffing or seek advice from a workplace wellbeing Guild. **HR receives only insights or information it is authorised to receive.** Private diary entries and personal Health DNA remain protected. Group-level insights require care as well: a small team or distinctive circumstances can make someone identifiable even when their name is omitted. AOS supports improvements to working conditions without turning personal reflection into hidden employee surveillance. Sensitive observations are not an automatic basis for disciplinary decisions or claims about a person's competence. ## Hiring and professional DNA A candidate may authorise a limited view of My.CareerDNA for a particular recruitment process. A business can use that authorised view to understand relevant experience, capabilities and how a candidate may contribute to the role and Business DNA. The employer does not acquire ownership of the candidate's Career DNA. The view is purpose-limited, and unrelated personal information is not part of the hiring permission. During employment, the employee's Persona and the Business Guild can both develop through legitimate shared experience. When employment ends, Guild access can end without erasing skills and experience the person genuinely acquired. The business retains only information and capabilities it is entitled to retain or use. ## Flows enforce the rules while work happens AOS Flows are governed, potentially long-running processes. They can involve approvals, contracts, terms, schedules, HTTP requests, conditional payments and settlement through the Sigmar Finance Protocol. Security applies throughout a Flow, not only when it begins. A Flow may wait for a later date, receive new information from an external service or require another Persona to approve the next action. Each protected action remains subject to the applicable authority and permissions. Consider this instruction: > Pay XYZ $100 on Thursday, provided task XYZ has been completed. The Flow can coordinate the agreed terms, evidence of task completion, scheduled payment date, required authorisation and settlement. A person who can submit evidence does not automatically have authority to approve or release money. A payment condition becoming true does not remove the need for a valid payment authority. A second Flow might request statistics from an external service every three months at 9:00 AM, inspect the response and decide what to do next. The HTTP response supplies information, **not permission to bypass security checks or perform an otherwise unauthorised action**. The Sigmar Finance Protocol supports governed execution, while HTQL supports specialised querying and data operations. They work with Flows but have distinct responsibilities. ## DNA, inheritance and the Marketplace DNA in AOS is a structured, evolving representation of a Persona's or Guild's knowledge, skills, memory, experience, behaviour and Flows. It is not a person's genetic information. As in the analogy of biological inheritance, descendant DNA can develop from characteristics of earlier DNA while becoming distinct in its own right. The parent DNA remains intact and its lineage remains traceable. **Inheritance does not mean unrestricted disclosure.** A descendant receives only characteristics and capabilities that are authorised to be passed on. Private memories, health observations and other protected information are not automatically included simply because they contributed to a parent's experience. The AOS Marketplace offers **compiled DNA**, not isolated Skills, Memory, Experience or Flows. Access to compiled DNA is governed by the applicable terms, ownership rights, security levels and permissions. Purchasing or licensing compiled DNA does not automatically transfer ownership of its source DNA or expose the private information of its contributors. ## Ownership, consent and purpose AOS distinguishes several questions that are sometimes incorrectly treated as one: | Question | What AOS protects | |---|---| | **Who owns it?** | The identity and rights of the person, Guild or organisation associated with the information or DNA. | | **Who can see it?** | Access limited by security level and specific permissions. | | **Who can use it?** | The authorised purpose, activity and applicable terms. | | **Who can share it?** | The authority to disclose a defined portion to a defined recipient. | | **Who can learn from it?** | Whether the information is eligible to contribute to learning or compiled DNA under the relevant permissions. | | **Who can keep it?** | Retention rights and obligations that continue or end as circumstances change. | Permission to view information is not automatically permission to publish it, export it, use it for training or incorporate it into another Guild's DNA. The same distinction applies to external specialists and contractors. Their participation can strengthen a Business Guild without automatically transferring ownership of their independent source DNA. ## Export, retention and audit AOS treats export, retention and audit as security-sensitive activities. The classification and permissions of information influence whether it can be exported, how it is protected, how long it may be retained and which actions require an auditable record. An export permission is distinct from ordinary viewing access. Removing someone from a Guild ends their future membership access, but it does not by itself settle every question about records legitimately created, shared or retained under an earlier agreement. Governed Flows preserve the evidence needed to understand relevant decisions and actions. For contracts and payments, this includes who was authorised to act, which conditions were evaluated and what outcome was recorded. Auditability does not mean that every participant can read every protected record. ## What AOS security does not imply AOS's security model is deliberately precise: - **A high classification level is not unrestricted access.** Specific permission is still required. - **Guild membership is not ownership.** A member retains their Persona and source DNA. - **Sharing is not blanket consent.** Access to one relevant view does not open an entire Persona. - **Learning is not automatic.** Information contributes to other DNA only where authorised. - **A Flow is not a security bypass.** Conditions, schedules and external responses do not create authority by themselves. - **AOS classification names are not external certifications.** A `GovernmentRestricted` or `SovereignSecret` label does not establish government accreditation. ## Frequently asked questions ### Can my employer read everything in My.Career or My.Health? No. Business Guild membership does not give an employer unrestricted access to personal Personas or their DNA. AOS applies security levels and permissions to the specific information and activity. ### Can a Doctor Guild see my entire Health DNA? Not merely because you join or share something with it. You authorise the relevant information for the relevant purpose, and the required security and access checks still apply. ### Can a Guild invite a Persona whose security level is too low? An invitation does not bypass the requirement. The AOS application and engine independently reject requests that fail the required security level. ### Does a higher security level let me read all lower-level information? No. A sufficient level satisfies only the classification threshold. Ownership, membership, permissions and purpose still govern access. ### Does buying DNA from the Marketplace give me its creator's memories? No. The Marketplace offers compiled DNA under agreed terms. It does not automatically disclose private memories or transfer ownership of the source Persona or Guild DNA. ### Can a scheduled Flow make a payment without permission? No. A schedule or completed task can satisfy a contractual condition, but payment still requires the applicable authority and governed execution checks. ### Is AOS a medical diagnosis or employee-monitoring service? No. AOS helps people organise observations and collaborate with authorised professionals. Medical decisions remain with qualified clinicians. Private staff reflections are not unrestricted HR records. ## Related documentation - [Sigmar AOS overview](./product.md) - [Personas](./personas.md) - [DNA](./dna.md) - [Guilds](./guilds.md) - [Flows](./flows.md) - [Marketplace](./marketplace.md) For the broader platform, visit [Sigmar](https://sigmar.au/).