Entimema
Contact us

Entimema Labs / 01 — Research remit

Research for financial and risk systems that must be trusted.

Entimema Labs develops the methods, validation logic and decision architectures behind controlled financial and risk workflows.

We turn recurring practitioner problems into methods that can be inspected, tested and—within a defined scope—operationalised.

Explore the research agenda

02 / The practitioner problem

What makes a financial result usable, reviewable and accountable?

Data, models, reports and automation each provide part of an answer. A controlled workflow must also show which evidence supports a result, which rule verifies it and who decides when uncertainty remains.

Labs investigates those boundaries: interpretation is not validation, and a model output is not yet a decision.

03 / Research agenda

Three domains. One standard of evidence.

Financial controls, AI governance, traceability and human judgement connect every part of the agenda.

Financial Intelligence

How does financial evidence become validated, traceable analysis?

Scope boundary. The research scope is wider than the current Income Statement workflow. Reporting, planning and forecasting topics are not all implemented product capabilities.

What we investigate

  • Canonical schemas, data normalisation and the meaning of periods, currencies and units.
  • Reporting, planning and forecasting logic connected to the decisions they support.
  • Reconciliation, evidence lineage and the point at which interpretation needs human review.

Selected existing work

Credit Risk

How do data, models, policy and monitoring become controlled credit decisions?

Scope boundary. This is methodological research. The publications do not imply that Entimema operates a production lending platform or a live credit-decision engine.

What we investigate

  • Scorecards, probability of default and calibration: what a risk estimate does and does not establish.
  • Portfolio monitoring, decision strategies and early-warning signals across the credit lifecycle.
  • Validation and explainability in relation to the decision a model is intended to support.

Selected existing work

Decision Systems

How do AI interpretation, deterministic controls and human judgement operate in one accountable workflow?

Scope boundary. An architecture defines responsibilities; it does not, by itself, demonstrate accuracy, safe autonomy or empirical validation.

What we investigate

  • The relationships between source evidence, claims, assumptions and unresolved unknowns.
  • Confidence, materiality, exceptions and the conditions for escalation or abstention.
  • How rules and human review constrain AI-assisted workflows while preserving decision lineage.

Selected existing work

04 / How we investigate

From practitioner problem to operational method.

Observe → Structure → Test → Operationalise → Improve

  1. Observe

    Identify a recurring practitioner problem and the operating conditions in which it appears.

  2. Structure

    Separate evidence, definitions, assumptions, calculations and judgement so each can be examined.

  3. Test

    Challenge methodology, calculations and controls through analytical examples and explicit failure modes.

  4. Operationalise

    Translate elements that meet their stated checks into workflows, rules or analytical systems, preserving the limits of those checks.

  5. Improve

    Use observed exceptions and validated corrections to identify where a method or implementation needs refinement.

Methodological position

Models interpret; rules control. Evidence, assumptions and unknowns must remain distinguishable, with consequential ambiguity available for human review.

One boundary applies throughout: implementation does not, by itself, establish empirical validation beyond its tested scope.

Decision architecture

A decision is more than a model output.

Evidence, interpretation, deterministic control and professional judgement have different responsibilities. Follow the relationships; they are not a single automatic chain.

Select or focus a concept to inspect its connections. Every responsibility is visible without interaction.

supports / challenges Claim

may generate Hypothesis

may be investigated through Model

may require clarification or review Human Judgment

may surface a control exception Human Judgment

may surface material ambiguity Human Judgment

informs Decision

Evidence → supports / challenges → Claim
Claim → may generate → Hypothesis
Hypothesis → may be investigated through → Model
Unknown → may require clarification or review → Human Judgment
Rule → may surface a control exception → Human Judgment
Model → may surface material ambiguity → Human Judgment
Human Judgment → informs → Decision

Separate responsibilities.
A model does not validate its own financial controls. An unresolved unknown need not become a hypothesis.

Decision → retains the relevant path

  • evidenceEvidence
  • interpretationModel
  • controlsRule
  • judgementHuman Judgment

These are retained references, not instructions to repeat the process. A model output is not the final decision.

Read the architecture

The upper branch separates a source, an assertion and a testable proposition. Unknowns remain separate. Interpretation and controls can each expose a review need; the decision keeps references to its relevant path.

This is a methodological architecture, not a map of implemented Income Statement v1 features. The applied-system example below defines that workflow’s actual scope.

05 / Applied proof

Implemented example

Traceable Income Statement analysis

Financial Intelligence V1

Research question → Method → Product control → Reviewable output

  1. Research question

    What must be established before an extracted financial value can support analysis?

    Interpretation and control

  2. Methodology

    Preserve accounting meaning through canonical concepts, periods, currency and scale. Keep interpretation separate from proof of arithmetic.

    Financial data normalisation

  3. Implementation

    Income Statement v1 connects extracted values and canonical mappings to source and evidence references that can be inspected.

    Evidence lineage

  4. Control

    Deterministic reconciliation checks financial relationships. Readiness gates identify failed controls, missing evidence and unresolved material issues.

    Validation controls

  5. Human review

    Review tasks expose ambiguity and proposed mappings. Supported review decisions are recorded and the affected checks are recalculated.

    Confidence and review

Implementation boundary. The current workflow is for eligible English Income Statements in XLSX, XLSM, CSV or text-based PDF files. It does not implement the entire Labs agenda, and its existence is not evidence of empirical validation across other financial or credit decisions.

See Financial Intelligence in practice

Secure workspace · sign-in required

06 / Selected methodological work

Methods available for inspection.

Selected research behind financial intelligence, credit risk and controlled decision workflows.

Explore all research

07 / Open questions

What remains unresolved.

These questions guide further investigation. They are research directions, not promised features or claims of completed validation.

  • How much ambiguity can be resolved automatically before a financial interpretation requires human review?
  • How should confidence interact with materiality when a small error can change a consequential decision?
  • How should decision lineage remain inspectable as source data, definitions and models change?
  • How can financial and risk workflows preserve professional judgement while making routine execution repeatable?

08 / Explore

Inspect the method. Explore its application.

Entimema Labs is practitioner-led by Alexander Dimitrov.

Explore Entimema Research
See Financial Intelligence in practice

Secure workspace · sign-in required

About the Founder Start a conversation