Where your team needs the same foundation again

Two tasks to start with

Illustrative examples, not customer references.

• Develop a feature using project policies

  The coding agent requests the applicable export policy. The team reviews the implementation and records its decision with the source. A similar task can later build on that foundation.

  Understand agent integration ↗

• Prepare an answer with business context

  An employee answers a pricing question using the approved policy. They see when an exception needs a decision. The rationale remains available for similar cases.

  Explore the business example ↗

Use current policies for each request

Using AI in these workflows requires answers to three questions.

• Which foundation applies?

  The current approved source is available with its version and accountable owner.

• What may happen?

  Policies and permissions determine whether a step is allowed, requires approval or must be blocked.

• What happened as a result?

  Proposal, decision, action and effect remain traceably connected.

Seven use cases where missing context has consequences.

The examples show how the same NomOS impact graph supports different professional domains. Open a use case for its workflow and regulatory context.

The scenarios below are illustrative examples, not customer references. Sources and policies require subject-matter approval. Technical controls apply to connected paths and depend on the control level achieved.

1. Banks and insurers Prepare product information using current internal directives.

   Advisory preparation, product information and compliance questions require the currently approved internal directives. Public or superseded sources must not be given the same standing.

   Typical workflow

   Before a client meeting, an advisor asks for the rules of a product. NomOS provides the applicable internal directive with source, version and validity date. If the foundation is unclear or contradictory, the conflict is surfaced before it becomes client advice.

   What matters

   Clear responsibilities, a risk-classified inventory, effective controls and ongoing monitoring. NomOS creates evidence for the context and policies used in governed interactions. The institution remains responsible for its overall risk management.

   Regulatory context: FINMA supervision and supervisory notice 08/2024 on the use of AI, Swiss banking secrecy, revFADP and GDPR, plus DORA and the EU AI Act for EU business.

2. Airlines and aviation Find the applicable procedures and exceptions during operational disruptions.

   Flight operations, ground handling, passenger service and maintenance rely on extensive operating instructions, procedures and exceptions. People and agents must know which version and accountable function apply to each case.

   Typical workflow

   After a flight cancellation, a service employee asks about rebooking, care and compensation for a specific case. NomOS provides the approved rules for the route, fare and situation with their source and version. An exception is escalated to the accountable team before it becomes an action.

   What matters

   NomOS does not replace safety-critical or legally required decisions. It provides the currently approved foundation. Technical control of actions requires a corresponding integration.

   Regulatory context: Requirements from FOCA and EASA, ICAO standards, passenger rights, revFADP and GDPR, plus NIS2 and the EU AI Act for organisations within their scope.

3. Public administration Record the legal basis for information provided.

   Citizen enquiries, internal legal information and the preparation of rulings must retain a clear link to the legal basis that applies.

   Typical workflow

   A case worker asks about responsibility and procedure for an application. NomOS provides the applicable legislation with version and reference. When the legal situation changes, the foundation of the next answer changes while previous responses remain traceable.

   What matters

   Every response must map to a legal basis. Responsibility, validity and the human decision must remain traceable years later.

   Regulatory context: The legality principle, federal and cantonal data protection laws, the Information Security Act and the transparency principle, plus the AI Act duties for public bodies in the EU.

4. Healthcare Find approved procedures for care and administration.

   Care processes, hygiene instructions and administrative workflows can become faster with AI. What matters is that only the approved, current version is used.

   Typical workflow

   A nurse asks for the correct sequence of a process step. NomOS answers from the approved version of the instruction. If two documents contradict each other, the system reports the conflict instead of silently choosing one.

   What matters

   Patient data must stay within the controlled environment. Clinical instructions require a clear version, access protection and an accountable owner.

   Regulatory context: Professional secrecy under the Criminal Code, revFADP for sensitive personal data and the electronic patient record act. If software affects the treatment path, the MDR may also become relevant.

5. Law firms, fiduciaries and family offices Keep knowledge and access separate for each client matter.

   Small teams work with highly sensitive knowledge. Matters must stay separated, access clearly attributed, and models and data operated in the appropriate environment.

   Typical workflow

   A lawyer researches within one client matter. NomOS only provides knowledge from that matter’s room. Every access remains attributed to the person and matter; content from other matters is not considered.

   What matters

   Professional secrecy, client separation, access controls and the location of models and data determine the technical setup. NomOS can therefore also run in the organisation’s own infrastructure.

   Regulatory context: Lawyers’ professional secrecy under the Lawyers Act and Criminal Code, the Anti-Money Laundering Act for financial intermediaries, plus revFADP and GDPR.

6. Pharma and medtech Document versions and approvals for inspections.

   Registration, quality management and study documentation require maintained frameworks, clear version status and traceable approvals.

   Typical workflow

   A regulatory team asks about market-access requirements. NomOS assembles the relevant approved frameworks with version status and accountable owner. The sources and approvals used remain available for a later inspection.

   What matters

   Depending on the process, electronic records must meet requirements for attribution, integrity, completeness and retention. An AI answer without a reliable foundation does not help in an inspection.

   Regulatory context: GxP frameworks, MDR and IVDR in the EU, plus Swissmedic and FDA data-integrity requirements including ALCOA+ and 21 CFR Part 11.

7. Software and IT service providers Support agents with project knowledge and reviewed decisions.

   Coding agents write code, change configurations and trigger technical workflows. Their actions therefore need the same policies and approvals as human changes.

   Typical workflow

   An agent plans a database migration. It retrieves applicable architecture decisions, requests an action assessment and submits a decision proposal. The accountable person decides in NomOS. Executing the migration requires a separately controlled path.

   What matters

   Customers increasingly expect evidence of how AI was used in the development process. Production access, approvals and supply-chain policies must apply technically to agents as well.

   Regulatory context: The EU AI Act depending on the organisation’s role as provider or deployer, NIS2 for affected service providers, plus customer requirements such as ISO 27001 and SOC 2 along the software supply chain.

Turn completed work into reusable knowledge

The agent can submit its finding through MCP as a knowledge or decision proposal. The responsible person reviews it in NomOS. On the next similar task, another agent can retrieve the approved basis and check its applicability.