Skip to content
Decision-state infrastructure
ende

PLATFORM / DECISION ARCHITECTURE

Exploration must not become the final decision by itself.

For liability-exposed enterprise decisions, analysis results must not be carried forward unchecked. Epistemis separates investigation, controlled transfer and recording the decision state as final.

Each task has defined powers and boundaries. These defined responsibilities and powers are what Epistemis calls authority.

THREE AUTHORITY SPHERES

Three tasks. One controlled path.

Results are checked at each boundary. No step takes over the authority of the next.

  1. 01SIMULATION

    EXPLORES

    HANDOFF TO BRIDGE
  2. 02BRIDGE

    CHECKS AND TRANSFERS

    HANDOFF FOR SEAL REVIEW
  3. 03SEAL

    HOLDS OR BLOCKS

Results from SIMULATION reach SEAL review only through BRIDGE.

AUTHORITY BOUNDARIES

What each sphere may do — and where its authority stops.

  1. 01

    SIMULATION

    TASK

    Examines what is missing, conflicting or uncertain in the decision space.

    MAY

    Analyse evidence and requirements, explore alternatives, localize uncertainty and make possible changes visible.

    MUST NOT

    Approve the enterprise decision, create a binding conclusion or create a SEAL.

    RESULT

    Exploratory states and preparatory results for controlled review by BRIDGE.

  2. 02

    BRIDGE

    TASK

    Checks whether SIMULATION results meet the defined requirements for a traceable transfer.

    MAY

    Check provenance, version, defined requirements, selection and rejection reasons, preserve open blockers, and transfer only suitable results.

    MUST NOT

    Approve the enterprise decision, make blockers disappear, create finality or create a SEAL.

    RESULT

    A controlled, traceable transition into SEAL review — or an explicitly blocked transition.

  3. 03

    SEAL

    TASK

    Checks whether the conditions defined for the Decision Space allow a binding conclusion.

    MAY

    Check evidence, rules, roles, controls and blockers. Record the state as final within Epistemis only when the defined conclusion conditions are met.

    MUST NOT

    Provide legal advice, guarantee compliance, judge commercial success or assume human responsibility.

    RESULT

    A decision state held as binding within Epistemis — or a blocked conclusion while required conditions remain open.

AUTHORITY BEFORE AUTOMATION

Analysis can influence the decision without owning its authority.

AI results can vary. Defined requirements and blockers are instead checked by the same rules for the same inputs.

AI / ANALYSIS

AI may analyse, structure and flag gaps. It does not hold final decision or evidence authority.

AUTHORITY BOUNDARY

NO FINAL AUTHORITY

DETERMINISTIC CHECKS

This makes the checks reproducible. The absence of a visible blocker is not itself an approval.

HUMAN RESPONSIBILITY

Required decisions or approvals remain with the accountable person assigned to them.

Automation can support scrutiny. It cannot replace authority.

SYSTEM POSITION

Epistemis complements existing systems.

Source systems remain authoritative for their own data, records and processes. Epistemis connects only the outputs and references selected for a liability-exposed decision space.

EPISTEMIS · DECISION-STATE LAYER

Selected decision inputs are bound to the decision state.

Selected outputs and references

ILLUSTRATIVE SOURCES AND REVIEW PROCESSES

  • ERP
  • Workflow
  • Document management
  • GRC
  • Model governance
  • Risk systems
  • Legal review

SOURCE AUTHORITY

This authority of the originating systems over their records is called Source Authority.

CONTROLLED READER VIEWS

One preserved state. Different reader views.

A SEAL Evidence Pack makes the preserved decision state accessible to a particular reader for a defined review purpose. This role- and purpose-bound presentation is called a Reader View.

PRESERVED DECISION STATE

The basis is the state at the time of the decision (T0), including its rules, authority and history.

  • ROLE AND PURPOSE

    A reader receives the information authorized and relevant for the defined review purpose.

  • DISCLOSURE AND REDACTION

    Visible detail may differ by reader. Omitted or redacted content does not rewrite the underlying decision state.

  • REVIEW, NOT REWRITE

    A Reader View supports examination of the decision basis. It does not let the reader alter the decision state, the Epistemis standard or its authority.

ILLUSTRATIVE READERS

  • Board
  • Legal
  • Risk
  • Audit
  • Insurer
  • External verifier
  • Regulator

ENTERPRISE DECISION-STATE PILOT

Which liability-exposed enterprise decision would you like to structure with Epistemis?

The Enterprise Pilot applies this architecture to your specific decision space.

Scope a Pilot