# Sigmar AOS — Flows > Official guide to governed processes, contracts, payments, HTTP integrations, schedules and the development of Personas, Guilds and DNA. ## What is a Flow? In Sigmar AOS, **a Flow is a governed, long-running process that coordinates actions, decisions, people, services and obligations until its conditions are satisfied**. A simple Flow may describe the steps for preparing a meal. A more advanced Flow can manage an agreement, wait for evidence that work has been completed, arrange payment on a specified date and record the outcome. Flows are the **common execution model across AOS**. They support the work of Personas and Guilds and connect applications to the Sigmar Finance Protocol, which provides foundations for governed execution, contracts, approvals, settlement and auditability. HTQL supports the specialised querying and data operations that Flows use to retrieve facts, evaluate information and work with records. **HTQL, Flows and the Sigmar Finance Protocol have distinct responsibilities; they work together rather than being interchangeable.** A Flow does not have to finish in one session. It can wait for a person, an external service, a scheduled date or an event. It can continue over days, months or years while retaining its progress and the evidence of decisions already made. Flows are also attributes of Persona and Guild DNA. How a person or organisation designs, performs and improves its Flows contributes to its accumulated skills, experience and behaviours. **A Flow does more than describe work: it governs when work can proceed, who can act, which conditions apply and what happens next.** ## How Flows relate to DNA Every Persona and Guild develops attributes through its activities. These include Skills, Memory, Experience, behaviours and Flows. Together, these attributes form compiled DNA. Consider someone who always checks the instructions before starting a task, even when they have done it many times. That habit is part of their characteristic behaviour. A Flow can describe the steps they follow: find the instructions, confirm the current version, check the materials and begin the work. The Flow is not the person's entire DNA. It is one of the attributes that helps define how that person works. When a Persona or Guild gains experience, it can improve the way a Flow is performed. These improvements contribute to the continuing development of its DNA. Compiled DNA can inherit selected characteristics and capabilities from earlier DNA. A descendant can retain an established way of performing a task, adapt it to new circumstances and develop further practices of its own. The lineage of the contributing DNA remains traceable. ## What a Flow contains A Flow brings the parts of a task into a clear sequence. Depending on the task, it can include: - **A purpose:** the outcome the task is intended to achieve. - **Steps:** the activities required to complete it. - **Participants:** the Personas or Guilds responsible for different parts. - **Decisions:** conditions that determine what happens next. - **Information:** the records or instructions needed at each stage. - **Checks and approvals:** the points where someone must confirm that work is correct or authorised. - **Waiting and follow-up:** steps that depend on a response, an event or a later action. - **Completion:** the result of the task and the experience gained from carrying it out. A Flow can be simple or detailed. It can involve one Persona or several participants working together. ## Contracts, terms and conditional payments A Flow can express an agreement between people or organisations and carry it through to completion. Its terms can define the parties, the work to be performed, the evidence required, the amount due, the payment date and the conditions that authorise settlement. For example: > **Pay XYZ $100 on Thursday, provided task XYZ has been completed.** The Flow brings several responsibilities together: 1. **Record the agreement.** The contract identifies the parties, the task, the amount, the agreed Thursday and the evidence required to establish completion. 2. **Track the work.** The Flow waits for task XYZ to be completed and for the agreed proof or acceptance to be provided. 3. **Apply the terms.** Completion alone does not bypass the agreement. The Flow checks whether the evidence and required approvals satisfy the contractual conditions. 4. **Wait for the payment date.** Even if the task is accepted earlier, payment follows the agreed schedule unless the contract provides otherwise. 5. **Authorise and execute settlement.** When the contractual conditions, payment date, permissions and available funds are satisfied, the Flow invokes the authorised payment or settlement capability supported by the Sigmar Finance Protocol and its blockchain-backed mechanisms. 6. **Record the outcome.** The Flow preserves the relevant approvals, settlement reference and result for later review and audit. If task XYZ is incomplete or the required evidence is rejected, **the Flow does not release the payment merely because Thursday has arrived**. It remains subject to the contract's terms, including any provisions for review, correction, dispute or expiry. The blockchain component supports authorised settlement and verifiable records; it does not replace contractual conditions or grant payment authority to an unauthorised Persona. A Flow cannot manufacture funds or override wallet permissions. This same pattern applies to paying a builder after inspection, releasing a supplier's deposit after delivery, or compensating a specialist Guild after accepted work. ## Scheduled and long-running Flows Flows can remain active while waiting for future dates, recurring schedules, external events or human decisions. Waiting is part of the process, not a failure or a reason to restart the task from the beginning. For example: > **Every three months at 9:00 AM, request statistics from `https://stats.com`, evaluate the response and continue according to the results.** The Flow defines the schedule, including the relevant time zone, and the authorised HTTP request. At each scheduled occurrence it can: 1. Wake at the scheduled time. 2. Make an HTTP request to the external service using its configured access permissions. 3. Receive the response and check whether the request succeeded and whether the data is usable. 4. Use HTQL where appropriate to query, compare or calculate values from the authorised data. 5. Follow a conditional path based on the result, such as recording the statistics, preparing a report, notifying a Guild or requesting a review. 6. Record what happened and wait for the next scheduled occurrence. For instance, if the returned figures exceed an agreed threshold, the Flow can request a manager's approval before taking a further action. If the service is unavailable, the Flow can follow its defined error-handling path rather than treating an unsuccessful request as valid statistics. **HTTP responses can change the course of a Flow.** An external call is not simply a notification: returned data can determine subsequent steps, conditions and participants, subject to the Flow's permissions and terms. A recurring Flow can be stopped, changed or replaced according to the authority and rules that govern it. AOS preserves the distinction between an ongoing obligation and each individual execution of that obligation. ## HTQL, the Sigmar Finance Protocol and Flow execution These components work together while serving different purposes: - **Flows** define and coordinate the process: participants, actions, conditions, schedules, external calls, approvals and outcomes. - **HTQL** provides specialised querying and data operations that a Flow can use to obtain and evaluate authorised information. HTQL is not itself the contract, payment authority or entire process. - **The Sigmar Finance Protocol** provides the governed execution foundations for contracts, approvals, treasury, settlements, identity and auditable state changes. Where appropriate, its blockchain-backed capabilities support verifiable ownership or settlement. - **Personas and Guilds** supply the authorised participants and capabilities. Their work through Flows contributes to their evolving DNA. AOS applications use this shared model. For example, **Profit Guard operates as a Flow within AOS**, drawing on HTQL for its finance-oriented data operations while using the platform's broader execution and governance capabilities. Flows are designed around deterministic, replayable and auditable execution. This means AOS distinguishes a decision already made from an action still pending, preserves the evidence relevant to that decision and avoids treating a replay as permission to repeat an irreversible external action such as a payment. The exact safeguards depend on the operation and its authorised integration. ## Example: preparing bread in a bakery A baker has developed a reliable way to prepare bread. Their Flow might be: 1. Check the day's orders and the available ingredients. 2. Measure the ingredients. 3. Mix and knead the dough. 4. Allow the dough to rise. 5. Bake at the required temperature. 6. Check that the bread meets the bakery's quality standards. 7. Package the finished bread for customers. The baker's knowledge of dough, timing, texture and quality forms part of their Persona DNA. The Flow captures the steps used to put that knowledge into practice. As the bakery learns what works best, its Guild can refine the Flow. Those lessons contribute to the bakery's Business DNA. The baker also gains experience, so the development is reciprocal. ## Example: growing vegetables together A community gardening Guild brings together people with different experiences. Some understand soil preparation, others know planting schedules, watering or pest management. The Guild can use Flows for preparing beds, planting seeds, monitoring growth and harvesting produce. Each task has its own steps and responsibilities. A member may discover that a different watering schedule works better for a particular crop. The Guild can incorporate that experience into its practices, while the individual also develops their own Persona DNA. When another gardening Guild receives authorised access to the first Guild's compiled DNA, it can inherit useful practices and adapt them to its own climate, soil and members. It develops distinct DNA rather than becoming a copy of the original Guild. ## Example: a patient and a Doctor Guild A person can use a health-related Persona to record observations such as headaches, muscle pain, sleep, activity and when symptoms occur. They can also record what they think may have triggered a symptom and whether anything seemed to help. These observations contribute to the person's Health DNA over time. AOS can help organise the history and highlight patterns worth discussing with a healthcare professional. An observed pattern is not automatically a medical diagnosis or proof of a cause. With the person's permission, relevant Health DNA can be shared with a Doctor Guild, such as **DRGUILD**, for assessment by qualified professionals. A follow-up Flow might include: 1. Record symptoms and their timing. 2. Share selected observations with the Doctor Guild. 3. Arrange an appointment or professional review. 4. Have a qualified clinician assess the information and decide on appropriate care. 5. Record the clinician's agreed instructions and any follow-up appointments. 6. Continue observing symptoms and report important changes. The Flow helps the patient and clinicians coordinate the steps. The patient remains in control of what they are authorised to share, and the Doctor Guild receives only information it is permitted to access. AOS supports observation and coordination; qualified healthcare professionals remain responsible for clinical assessment, diagnosis and treatment. Serious or urgent symptoms require appropriate medical attention rather than waiting for a Flow to complete. ## Example: supporting staff in a Business Guild An employee may use a work-related Persona to reflect on workload, relationships with colleagues, achievements and recurring stress. Their private observations contribute to their own evolving DNA. A Business Guild can use authorised information and appropriately protected insights to understand workplace conditions. For example, recurring reports of excessive workload may help reveal a need to review staffing, scheduling or management practices. A workplace-support Flow might involve identifying an issue, arranging a confidential conversation, reviewing possible improvements, assigning agreed actions and checking whether conditions improve. Where specialist support would help, the Business Guild can seek an appropriate Guild, such as workplace wellbeing professionals, mediators or organisational advisers. **An employee's private diary or Health DNA does not automatically become visible to HR.** AOS enforces security levels and access permissions. Both the application and the underlying engine reject requests from a requester whose security level is below the required level. The employee develops through their own experiences. The business develops through improvements it is authorised to make and retain. The relationship can strengthen both sides without transferring ownership of private DNA. ## Flows across Personas and Guilds A Flow does not have to belong to one person. It can coordinate tasks across a family, community, team, department or business. For example, organising a community event may involve a planning Guild, volunteers, caterers and a local venue. One group confirms the location, another prepares food, and another manages invitations. Each participant performs the steps for which they are responsible. In a business, a Flow can similarly connect staff Personas, departmental Guilds, independent specialists and external businesses. Participation in the Flow does not make those contributors employees or transfer ownership of their DNA. Guilds contribute their authorised capabilities while retaining their own identities and responsibilities. ## Decisions, approvals and waiting Not every task moves directly from its first step to its last. A Flow can respond to a decision: if supplies are available, continue preparing an order; if supplies are missing, request them first. It can wait for a person to approve an action, for a document to arrive or for a required check to be completed. A Flow can also repeat steps when necessary, such as checking a garden each morning or following up on an unresolved maintenance issue. Approvals and responsibilities remain part of the task. A Flow does not grant someone authority they do not already have. AOS applies the permissions and security rules governing the people, Guilds and information involved. ## Flows, learning and improvement Completing a Flow can produce useful experience. Participants may learn that a step was unnecessary, that a check prevented a mistake or that a different sequence produced a better result. Those observations can contribute to the evolution of Persona or Guild DNA. Over time, a Guild may develop more reliable practices, while its members build their own experience and capabilities. AOS distinguishes between a task being completed and the quality of the result. Completing every step does not automatically mean the outcome was good. Feedback, observations and verified results provide the context for improvement. DNA can therefore reflect successful practices, lessons learned and, where supported by evidence and appropriate review, mistakes or conduct that affect how a capability is assessed. ## Privacy and security in Flows Flows can involve information that is public, private or highly restricted. AOS uses security levels to determine which requests are permitted. The levels are **Public, Standard, Confidential, SensitivePersonal, Financial, HealthGuarded, LegalPrivileged, GovernmentRestricted and SovereignSecret**. Standard is the normal starting level for newly created information. A Persona cannot perform an action or access information requiring a higher security level than they hold. The Flutter application and the AOS engine both reject requests that fail this requirement. Other access permissions continue to apply even when a Persona meets the required security level. For example, a community volunteer may be allowed to see the public steps of an event Flow without being allowed to see another participant's private medical details. Similarly, a member of a Business Guild does not automatically gain access to an employee's personal reflections. When Flows contribute to compiled DNA, their protected information remains subject to the relevant permissions and restrictions. ## Flows and the Marketplace **The Sigmar AOS Marketplace offers compiled DNA, not individual Flows.** A Flow is an attribute of a Persona's or Guild's DNA. It helps describe how that Persona or Guild performs a task, but it is not sold as a separate Marketplace product. For example, a baking Guild may develop compiled DNA that includes its knowledge, experience, quality-checking behaviours and bread-making Flows. Another bakery can obtain authorised access to that compiled DNA under the agreed terms. The receiving bakery can use the permitted capabilities and develop its own practices. The original Guild's DNA continues to exist independently, and the lineage of inherited capabilities remains traceable. Buying or licensing compiled DNA does not automatically provide access to protected memories, personal records or information outside the agreed permissions. ## Flows and the wider AOS platform Flows are one part of Sigmar AOS. Personas and Guilds develop DNA through their Skills, Memory, Experience, behaviours and Flows. Compiled DNA brings those attributes together into a distinct and evolving representation of capability. The Sigmar Finance Protocol supports governed, deterministic execution beneath AOS. HTQL supports specialised querying and data operations. Neither should be confused with the definition of a Flow: **a Flow is a task with defined steps**, regardless of whether that task involves a household, a patient, a community or a business. For a broader introduction, see [What is Sigmar AOS?](../product.md). For related explanations, see [DNA](dna.md), [Personas](personas.md), [Guilds](guilds.md) and [Marketplace](marketplace.md). ## Frequently asked questions ### Is a Flow the same as DNA? No. A Flow defines the steps of a task. It is one of the attributes that contributes to compiled Persona or Guild DNA. DNA also includes knowledge, skills, memory, experience and characteristic behaviours. ### Can a Flow involve more than one person or Guild? Yes. A Flow can coordinate tasks involving individuals, families, teams, departmental Guilds, specialist Guilds and businesses, with each participant acting within their permissions. ### Does AOS sell Flows in the Marketplace? No. The Marketplace offers eligible **compiled DNA**. Flows are attributes within that DNA, not separate Marketplace products. ### Can a Flow change as people learn? Yes. Experience can lead to better steps, new checks and improved practices. These changes can contribute to the continuing evolution of Persona and Guild DNA. ### Can a Flow access private information automatically? No. AOS enforces security levels and access permissions. Participation in a Flow does not grant unrestricted access to another person's or Guild's private information. ### Can a Flow make medical decisions for a patient? A Flow can help organise observations, appointments and follow-up steps. Qualified healthcare professionals remain responsible for clinical assessment, diagnosis and treatment. ## The central idea **Flows make activities repeatable. Experience makes them better. DNA preserves and develops the capabilities behind them.** As Personas and Guilds carry out tasks, learn from results and share authorised compiled DNA, their knowledge can contribute to new generations of capability without losing the distinct identity of its sources.