Skip to content
gluon

One decision point

Every question and every action passes the same four checks, in the same order, before AI answers or acts.

Who is asking

Choose who asks. The four engines run the same checks in the same order, and each person gets what applies to them.

Who asks
The question

“Which protocol applies on ward 4?”

Asked by a nurse on ward 4
Asked by a physician on ward 4
Asked by an agent acting for the nurse
The answer
Ward 4 protocolAdopted · deployed to ward 4

The ward 4 protocol applies, in the version deployed to your ward. You can read §1 and §2. §3 is for physicians, so it is withheld.

The ward 4 protocol applies, in the version deployed to your ward. You can read all three sections.

The ward 4 protocol applies. The agent acts for the nurse, so it gets §1 and §2, like the nurse. §3 is withheld.

  • §1 AdmissionEveryone on the ward
    Included
    WithheldRequest access
  • §2 MedicationEveryone on the ward
    Included
    WithheldRequest access
  • §3 PhysiciansPhysicians only
    Included
    WithheldRequest access

Every access on the recordNEN 7513

Who may see what
Who asks§1 Admission§2 Medication§3 Physicians
A nurseWard 4AllowedAllowedWithheld
A physicianWard 4AllowedAllowedAllowed
An agentActing for the nurseAllowedAllowedWithheld
The four checks, in order
  1. Which source has authority

    Authority Graph

    AdoptedThe adopted protocol counts. A draft never does.

    AdoptedThe adopted protocol counts. A draft never does.

    AdoptedThe adopted protocol counts. A draft never does.

    How the Authority Graph works

    Knows which source is current and authoritative. Every source carries a trust level, and every value keeps its evidence. When two sources disagree, the one with authority prevails and the conflict stays visible.

    • A trust level per source: authoritative, curated, conversational or unverified.
    • Which source prevails when two disagree: an approved policy outranks a discussion.
    • Conflicts and gaps are shown, never smoothed over.
  2. Who may see it

    Permission Engine

    §3 withheld§1 and §2. §3 is for physicians only, so it shows as withheld.

    All threeAll three sections, §3 included.

    §3 withheldThe nurse’s rights, never more: §1 and §2. §3 shows as withheld.

    How the Permission Engine works

    The same permissions for people and agents, checked on every request. Rights from your source systems apply, with your own policies and markings on top. The same decision point serves chat, API, MCP and the designer.

    • Rights from your source systems are mirrored, with their age checked.
    • Your policies and markings apply on top, and sensitive fields are masked.
    • An agent gets the rights of the person it acts for. Never more.
  3. What applies here and now

    Applicability Engine

    Ward 4The version deployed to ward 4, not another site’s.

    Ward 4The version deployed to ward 4, not another site’s.

    Ward 4The version deployed to ward 4, not another site’s.

    How the Applicability Engine works

    Relevant is not the same as applicable. Your model records status, version, scope and validity. Gluon uses them to hand AI only what applies to this person, this team and this moment.

    • The right scope: knowledge is deployed per group, department and team.
    • The right status: proposed and draft knowledge never reaches an answer.
    • The right moment: validity dates are part of the model.
  4. What the record says afterwards

    Evidence Engine

    LoggedWho asked and what was read, on the record as NEN 7513 asks.

    LoggedWho asked and what was read, on the record as NEN 7513 asks.

    LoggedThe agent, the nurse it acts for and what was read, on the record.

    How the Evidence Engine works

    Every answer and action can be explained. Each answer shows how it was reached, and every decision lands in an append-only, hash-chained audit trail that you can export to your SIEM.

    • Which source applied, and which version.
    • Which permissions were checked.
    • What was left out: versions by name, withheld sources only as a count.

A worked example on the product as it is, with invented names and figures. Not a customer story.Read the example in full

What we believe

We’d rather say “we don’t know” than invent an answer.

A gap that is shown is safer than a guess that sounds right.

Actions

Before an agent sends, pays or changes anything, Gluon gives a verdict and records why. Try it with the finance agent of the worked example.

The finance agent wants to
EUR 40,000
EUR 500Mandate up to EUR 10,000EUR 60,000
From the example

The amount does not count here: a bank change is blocked whatever the amount.

Kill switchStops any action at once, without a new version.
Decision · actionAgent · finance

Within the mandate. The invoice of EUR 60,000 is queued for payment.

Payment of EUR 40,000 put on hold until a second approver signs.

Refused. Only the supplier team changes bank details, after a call-back check.

Switched off. No action runs while the kill switch is on, whatever the amount.

Switched off. No action runs while the kill switch is on, whatever the amount.

Action
Action
Action
Action
Action
Queue an invoice for payment · EUR 60,000
Queue an invoice for payment · EUR 40,000
Change a supplier’s bank account
Queue an invoice for payment · EUR 60,000
Change a supplier’s bank account
Rule
Rule
Rule
Rule
Rule
Procedure 2026 · §3.1
Procedure 2026 · §3.1
Procedure 2026 · bank details
Kill switch · on
Kill switch · on
Mandate
Mandate
Mandate
Mandate
Mandate
Finance agent · up to EUR 10,000
Finance agent · up to EUR 10,000
Finance agent · not for bank details
Not checked · the action is off
Not checked · the action is off
Approver
Approver
Reason
Reason
Reason
None needed · within the mandate
Finance controller · asked
Supplier team only, after a call-back check
Stopped at once, without a new version · who and why audited
Stopped at once, without a new version · who and why audited
Verdict
Allowed
Approval required
Blocked
Switched off

Recorded in the audit log · append-only, hash-chained

A worked example on the product as it is, with invented names and figures. Not a customer story.Read the example in full

On the real screens

Why access was granted or refused, what an action changes before it runs, and the switch that stops it.

Answers · Access explainer

Why someone can or cannot see it.

Every check that passed or refused, and what was withheld or masked. An officer can view the answer as the person would.

Explain a person’s access
Actions · Preview

What an action changes, before it runs.

The parameters, the checks that passed, the approval it needs and what it sets in motion.

Preview an action and decide an approval
Actions · Kill switch

Stop any action at once.

Without a new version. Who did it and why are audited.

The kill switch

Questions

How is Gluon different from RAG?

RAG finds passages that look like the question. Gluon first checks which sources have authority, which version applies and whether this person may see it. Retrieval then works only on that context.

Is Gluon a language model or a search engine?

Neither. Your model writes the answers and your search finds the documents. Gluon decides what the model may use and what your agents may do, and records each decision.

Do agents get more rights than people?

No. An agent gets the rights of the person it acts for, never more, checked on every request.

Who approves an action?

The approvers your model names for the action, with quorum and expiry. Gluon asks them and records their decision.

Can we stop an action at once?

Yes. The kill switch stops any action at once, without publishing a new version.

Does Gluon run long processes itself?

No. Gluon decides and executes single actions. Long-running processes belong to the agent platform you use, which receives an approved action.

Where it is used