Skip to content
ERUKA · GOVERNED KNOWLEDGE KERNEL

What an agent is allowed to say.

Eruka assigns one of four states to every fact, with its source, at write time. A low-confidence write never overwrites a confirmed fact. A required fact that is missing comes back as UNKNOWN, and the agent is blocked from inventing it.

BUILTIN PRODUCTION UNDER CLIENT WORKPATENT PENDINGNOT YET SOLD STANDALONE
THE FOUR STATES

Four states, assigned at write time.

Eruka assigns one of four states to every fact, with its source, at write time. It is not a filter applied to output afterwards.

CONFIRMED

Traced to an approved source. Can be stated.

WHAT THE AGENT MAY DO

Cite with confidence.

INFERRED

Derived from confirmed facts, not sourced directly. Flagged as such.

WHAT THE AGENT MAY DO

Use, but say it is inferred.

UNCERTAIN

Weak or conflicting support, or gone stale.

WHAT THE AGENT MAY DO

Hedge, or send to a human for review.

UNKNOWN

A required fact that is missing. Not the absence of data, the presence of a detected gap.

WHAT THE AGENT MAY DO

The system is blocked from inventing an answer.

THE WRITE GATE

The agent proposes. A human or a confirmed source promotes.

Every write goes through one gate. The gate assigns the state, attaches the source and appends the evidence. Nothing an agent generates becomes usable truth on its own.

AGENT PROPOSESONE WRITE GATEGOVERNED STORECONFIRMED · SOURCE ATTACHEDINFERRED · FLAGGED AS INFERREDUNCERTAIN · SENT FOR REVIEWUNKNOWN · REFUSED AT THE GATE, GAP NAMED
  1. CONFIRMED · SOURCE ATTACHED
  2. INFERRED · FLAGGED AS INFERRED
  3. UNCERTAIN · SENT FOR REVIEW
  4. UNKNOWN · REFUSED AT THE GATE, GAP NAMED

Guardrails filter after generation; retrieval fetches context but cannot say what is missing. Eruka refuses before storage and names the gap before generation.

Other tools store facts too, but none assigns a state at write time, and none refuses an ungrounded overwrite.

GAP DETECTION

UNKNOWN is not the absence of data. It is the presence of a detected gap.

Eruka identifies missing context for a task and can emit a specific constraint for each missing field.

WITHOUT ERUKA
You are a content writer for our B2B SaaS company. Write a LinkedIn post about last quarter's results and announce our expansion into European markets.
WITH ERUKA
You are a content writer for our B2B SaaS company.

Governed context from Eruka:

CONFIRMED   company name, industry, target segment, core product
INFERRED    primary operating region — derived from confirmed facts, treat as provisional
MISSING     last quarter's revenue, European market presence, tone-of-voice guide

Do not fabricate the missing fields.

Task: Write a LinkedIn post about last quarter's results and European expansion.

Model, under constraint: I can't write this post as specified. Three of the facts it needs are missing from the governed context. I can write about the confirmed topics instead, or you can supply the missing fields.
GOVERNANCE AS AN ARTEFACT

What the reviewer gets.

A school board or a compliance team gets a record it can inspect, not a promise.

  • Audit trail export

    Every write with its state, actor and evidence reference, per period.

  • Gap report

    What the knowledge base is missing before the agent runs, per task.

  • Review queue

    Quarantined writes wait for a human, who can override with a recorded reason.

  • A written guarantee

    The statement of work says a confirmed fact is never silently overwritten by the AI.

For European buyers, these mechanisms satisfy the technical requirements of EU AI Act Articles 12 to 15 on record-keeping, transparency, human oversight and accuracy. We never say compliant.

The governance add-on
EVIDENCE · WHAT WE PUBLISH

We publish no number we cannot make you reproduce.

Eruka ships with an automated benchmark harness. Until every run is pinned to a fixed model, a fixed seed, and a fixed fixture set, the results stay internal — because a number you cannot re-run is marketing, not evidence.

So there are no percentages on this page. The whole point of Eruka is verifiable reliability, and that has to start with our own claims. Ask us for the methodology and we will walk you through the harness, the fixtures, and exactly what each dimension measures, before you decide whether the number would have meant anything.

THE STANDING RULE
No performance number leaves the company until it reproduces on a pinned test harness.
PATENT PENDING

Provisional application on the Eruka mechanism filed March 2026. Complete specification due March 2027.

Built, live on Dirmacs infrastructure and inside client work. Not sold standalone.

WHERE ERUKA GOES

The same kernel at three ranges.

  1. Phase AIN PROGRESS

    Eruka as it is today, finished

    Hardening what already runs so it can be handed to tenants outside our own walls.

  2. Phase BRESEARCH TODAY

    A public Eruka instance

    A public Eruka instance anyone can connect to over MCP. A research surface and a public good, not a revenue line.

  3. Phase CRESEARCH QUESTIONS

    Verification where claims spread

    Real-time verification of public claims against the sources they cite. Research questions only.

A is the work in hand. B and C are research, and nothing on this page asks anyone to pay for them.