SCIKIQ · Agent Fabric · Concept

Agents that work inside a governed model of the business

AskUnderstandDecideAnalyseCheckActRecord

Most enterprise agents are connected to data. A SCIKIQ agent operates inside a model of how the business works: which entities exist, how they relate, which rules apply, who may approve what, and what must be recorded. That is what makes its answers explainable and its actions safe to allow.

01 Architecture

Three tiers, one owner of meaning

SCIKIQ business layerWhat makes the answer right
Business contextOntology and knowledge graphDecision modelsPolicy and accessAgent factory

The part that is specific to your enterprise. It defines the question, the facts, the rule and the boundary.

Agent runtimeWhat keeps agents running
Agent sessionsMemoryTool connectionsSub-agents and workflowsDurable execution

Interchangeable: SCIKIQ’s own runtime, or an agent runtime your organisation already operates, reached as a service. The business layer above does not change when the runtime does.

Enterprise systemsWhere actions land
SAPSalesforceSnowflakeERP, CRM and workflow APIs

Actions reach these systems only through the governed path, never directly from a model.

02 The governed path

From a question to an approved action, in eight steps

  1. 1

    Business intent

    A person asks in business language. The question is resolved to a domain, the entities it concerns and the decision it is really asking for.

    Layer 10 · Context Engine
  2. 2

    Business context

    The knowledge graph returns the relevant entities, their relationships, the live KPIs and the rules that apply, already filtered to what this person may see.

    Layer 6 · Enterprise Knowledge Graph
  3. 3

    Decision

    A deterministic decision model evaluates the rule and returns a status, a severity, the reasons and a recommended action. The verdict is the business’s rule, not a model’s guess.

    Layer 12 · Decision & Reasoning Engine
  4. 4

    Specialist agents

    Demand, inventory, supplier and finance agents each examine the same governed context from their own angle and explain what they see.

    Layer 11 · Agent Fabric
  5. 5

    Policy and approval

    Role and policy are checked before anything is written. The result is one of three: allowed, allowed with approval, or not allowed.

    Layer 13 · Governance Gate
  6. 6

    Enterprise action

    An approved action is raised in the target system, for example a purchase requisition in SAP, held as pending until a person approves it.

    Layer 14 · Action Fabric
  7. 7

    Audit and lineage

    Every run leaves a record: the question, who asked, the entities used, the decision and its reasons, the policy result and the actions raised.

    Layer 15 · Outcome & Observability
  8. 8

    Business response

    The person gets the status, the reasons, the recommended action and whether it needs their approval, with every figure traceable to its source.

    Layer 15 · Outcome & Observability

03 Worked example

One question, followed end to end

Illustrative: the supplier, material and figures are invented to show the flow.

The question

“Which suppliers could impact our European Q4 production?”

Asked by a supply chain manager

What the knowledge graph returns

SupplierABC Components, GermanyLead time 45 daysOn-time delivery 82%
MaterialHydraulic valveDemand 120 a dayOn hand 3,200Safety stock 5,000
PlantGermany plant, EuropeUses the hydraulic valve

ABC Components supplies the hydraulic valve, which is used by the Germany plant.

The decision

Rule: Shortage if stock is below safety stock and days of cover are shorter than the supplier’s lead time.

Supply shortageAt riskSeverity: High
  • Stock of 3,200 is below the safety stock of 5,000.
  • About 27 days of cover against a 45-day supplier lead time.

What the specialist agents add

Demand agent

Production needs about 120 valves a day through the quarter.

Inventory agent

Current stock covers roughly 27 days.

Supplier agent

A 45-day lead time and 82% on-time delivery: this supplier needs attention.

Finance agent

Expediting adds logistics cost, to be weighed against the cost of a stopped line.

Policy

Supply chain managers and procurement directors may raise this action. It requires approval.

Action

Purchase requisition for 5,000 valves raised in SAP, status pending approval. Nothing is ordered until a person approves it.

On the record

Execution ID · Question and role · Entities used · Decision and reasons · Policy result · Action raised

04 Across industries

The same path, four more industries

The steps do not change from one industry to the next. What changes is the ontology, the rule and the policy. Each example below ends differently: an action held for a committee, a pause that only an investigator can turn into a decline, an action released automatically within policy, and a consent check before a customer is contacted.

Illustrative: names and figures are invented to show the flow.

Banking

“Which corporate borrowers are drifting toward a covenant breach this quarter?”

Asked by a credit risk manager
Context
  • Borrower: Nordal Logistics, €40m term loan
  • Covenant: net debt to EBITDA no higher than 3.5x
  • Latest ratio 3.3x, rising for three quarters
  • Relationship: refinancing talks due next month
Rule
Early warning if the ratio is within 10% of its covenant limit and has risen for two quarters or more.
Decision
Early warning Severity: Medium
Agents
  • Credit Ratio trajectory crosses 3.5x within two quarters at the current trend.
  • Relationship Refinancing talks are a natural moment to discuss headroom.
  • Collateral Security coverage remains adequate today.
Policy
A risk manager may add a borrower to the watchlist. Any change to the limit needs the credit committee.
Action
Borrower flagged on the watchlist and a review task assigned to the relationship manager. Limit unchanged.

The agent acts within its authority and leaves the bigger decision to the committee.

Insurance

“Which open motor claims should go to investigation before payment?”

Asked by a claims manager
Context
  • Claim: €18,400, loss 21 days after the policy started
  • Benchmark repair cost for this model: about €9,000
  • Repairer linked to three earlier flagged claims in the graph
  • Customer: no previous claims
Rule
Refer if the loss falls within 30 days of inception and the amount exceeds 1.5 times benchmark or links to flagged parties.
Decision
Refer to investigation Severity: High
Agents
  • Claims The amount is about twice the benchmark for this repair.
  • Network The repairer connects to three earlier flagged claims.
  • Customer The customer must be told about the review within the regulated timeline.
Policy
A claims handler may hold payment and open an investigation. Only an investigator may decline a claim.
Action
Payment held, an investigation case opened, and the customer notified that the claim is under review.

The agent can pause and refer, but it can never decline. That boundary sits in policy, not in the prompt.

Retail

“Which stores will run out of the promotion’s hero product before it ends?”

Asked by a merchandise planner
Context
  • Store 214: sunscreen 200ml, 420 on hand
  • Selling 85 a day during the promotion, 10 days left
  • Distribution centre: 6,000 in stock, two-day transfer
  • Same region as the distribution centre
Rule
Replenish if days of cover are shorter than the days left in the promotion and the distribution centre holds stock.
Decision
Stock-out risk Severity: High
Agents
  • Demand The promotion is selling at about 85 a day and holding steady.
  • Inventory About 5 days of cover against 10 days of promotion.
  • Logistics A transfer fits on the next scheduled delivery.
Policy
Transfers under 1,000 units within a region are approved automatically. Larger ones need the planner.
Action
A transfer of 430 units was raised and released automatically, with the planner informed.

Inside policy, the action runs without waiting for a person, and it is still on the record.

Telecom

“Which high-value customers should we contact with a retention offer this week?”

Asked by a retention lead
Context
  • Customer: four years tenure, contract ends in 21 days
  • Three dropped-call complaints in the last 30 days
  • The cell site serving their home has an open fault
  • Consent: opted in to marketing contact
Rule
Retention risk if the contract ends within 30 days and there are two or more network complaints from a high-value customer.
Decision
Retention risk Severity: High
Agents
  • Network The fault at the serving site explains the dropped calls.
  • Offer Eligible for a 10% loyalty discount on renewal.
  • Finance The offer costs less than the margin at risk if the customer leaves.
Policy
Discounts up to 15% need no approval. Outbound contact is allowed only with marketing consent, which is on file.
Action
The site fault was raised in priority, and a call with the 10% offer was queued for the retention team.

The root cause is fixed first, and consent is checked before anyone is contacted.

Ten industries, three use cases each: the tutorials

05 Design principles

Why the answer can be trusted

1

Rules decide, agents explain

The shortage call comes from a rule the business owns and can read. Language models summarise and add perspective; they do not change the verdict.

2

Context before reasoning

An agent only sees entities resolved through the ontology and permitted to the person asking. It reasons over governed facts, not over whatever a search returned.

3

Policy before any write

The governance check sits between the recommendation and the action, so a persuasive answer can never bypass an approval rule.

4

Approval is a state

Sensitive actions are created as pending, visible in the target system, and wait for a person. Automatic execution is reserved for actions inside policy.

5

Every run is on the record

The audit record links the question to the data, the rule, the policy and the action, which is what a reviewer or a regulator will ask to see.

6

The runtime is replaceable

Sessions, memory and tool execution can come from SCIKIQ or from an existing runtime. The business layer, which is the part that is hard to rebuild, stays the same.

06 Creating an agent

What a business team defines

An agent is defined by the business it serves, not by the model behind it. A team names the domain, the context it may use, the decisions it supports, the systems it can reach and the policies that bound it. Every question and every action then runs through the same governed path: ontology → knowledge graph → decision → agents → policy → approval → action → audit.

Domain
Supply chain
Context
Supply chain ontology, enterprise knowledge graph, 360 views
Decisions
Supply risk, inventory risk, supplier risk
Systems
Snowflake, SAP, Salesforce
Policies
Procurement policy, financial approval

07 Keep going

Related reading

See the whole fabric

Where each step of the governed path sits in the Enterprise Intelligence Fabric.

Open the platform map

Frequently asked questions

What is a governed business agent?

An AI agent that works inside a model of the business rather than on raw data. It takes its facts from the knowledge graph, its verdict from a decision rule the business owns, and its permission to act from policy, and it records every run.

Does the language model decide what happens?

No. The decision model evaluates the business rule and returns the status and the recommended action. Agents explain and add perspective. Policy then decides whether the action may be raised and whether it needs approval.

Can we use an agent runtime we already run?

Yes. The runtime that handles sessions, memory and tool execution is a replaceable layer. SCIKIQ provides the business context, decisions, policy and audit above it, and those stay the same whichever runtime sits underneath.

What happens when an action needs approval?

It is created in the target system as pending, for example a purchase requisition awaiting approval, and nothing executes until an authorised person approves it. The approval is part of the audit record.