Evidence before conclusion

What does your evidence actually support?

Give Loosehead a defined question and the documents or data available to answer it. Loosehead determines what the supplied evidence supports, what it does not, and where proceeding would require missing evidence, meaning, authority or an unsupported assumption.

Deterministic evaluation. No invented evidence. No automated business decision.

What it does

A question. The available evidence. A bounded determination.

Organisations already hold large amounts of information in documents and data. The difficult question is often whether that information actually supports the conclusion someone — or some system — is being asked to reach.

What is supported

Loosehead identifies where the supplied evidence satisfies the conditions required by the defined question.

What is not supported

Missing or inadequate evidence is surfaced rather than silently repaired, enriched or converted into an assumption.

What is still required

Where the question depends on missing evidence, meaning or authority, Loosehead makes that boundary explicit.

How it works

Question + evidence → Loosehead → what the evidence supports.

Loosehead evaluates a defined question against the evidence that was actually supplied. It preserves the distinction between what is present, what is absent and what cannot legitimately be inferred.

Why Loosehead

The evaluator does less — deliberately.

Many systems score, enrich, repair, infer, optimise or recommend. Loosehead preserves a narrower boundary: determine what supplied evidence supports without converting that determination into authority or action.

Deterministic core

The same bounded evidence, declared conditions and rules are intended to produce the same evaluative result. Probabilistic AI is not required for the core determination.

Non-inventing

Missing evidence, meaning or authority is surfaced. It is not silently filled in simply to allow evaluation to continue.

Non-authoritative

Loosehead determines what the evidence supports. The organisation remains responsible for policy, authority, interpretation and consequence.

Evidence before conclusion.
Determination before decision.

Where it can be applied

Wherever an answer depends on evidence.

The subject can change while the underlying problem remains the same: a defined conclusion is being asked of documents, data or both, and the organisation needs to know whether the available evidence actually supports it.

Policy & contractual material

Evaluate a defined question against terms, policies, standards, requirements or other controlled documents.

Operational decisions

Determine whether the records available at a decision point support the stated conclusion or required conditions.

Data & model inputs

Establish whether supplied data carries the evidence and meaning a proposed downstream use expects.

Transformation & integration

Determine whether required meaning survived mapping, translation, system boundaries or representation change.

Automation & AI

Establish the evidential basis available before automated reasoning, recommendation or consequential action begins.

Audit & review

Preserve an attributable record of what could and could not be established from the evidence available at the time.

Browser demo

See Loosehead work.

We are preparing a browser-based demonstration of Loosehead using bounded synthetic cases.

Demo coming soon
01

Start with a defined question

The demonstration begins with a specific conclusion or use to be tested rather than an open-ended request for an answer.

02

Supply bounded evidence

Documents, structured information and declared conditions are kept within an explicit evidence boundary.

03

Inspect the determination

See what is supported, what is not, what is missing and the basis for the result.

04

See where AI stops

AI can assist at defined boundaries. It does not get to invent the evidence, meaning or authority required for the deterministic determination.

Bounded proof of concept

Bring one real question.

A first engagement can be deliberately small: one defined question and the documents or data your organisation currently uses to answer it.

A null result is valid. The purpose is to establish what the supplied evidence supports, not to force a predetermined answer.

01

You bring the question

Choose a bounded problem where the answer depends on evidence your organisation already holds.

02

You supply the permitted evidence

Documents, data or both. The boundary is agreed before evaluation.

03

Loosehead evaluates it

The evaluation remains bounded to what was supplied and to the declared conditions relevant to the question.

04

You receive the basis

A transparent record of what is supported, not supported or cannot be established — and why.

Development evidence

Built through governed experimentation.

Loosehead has been developed by separating product meaning from implementation choice, testing the same underlying evidential boundary across different technical and operational settings, and preserving evidence from each pass.

Determinism Repeated execution is used to test whether bounded inputs, declared conditions and rules produce stable results.
Multiple placements The architecture has been examined across API, workflow, batch, orchestration and other placement patterns.
Evidence boundaries Experiments distinguish what is supplied, what is absent and what cannot legitimately be inferred.
Product discipline The core capability is defined independently of a required vendor, platform, transport or implementation technology.
Work with us

Have a question whose answer depends on evidence?

Bring us one defined question and the documents or data you currently use to answer it. We are looking for organisations willing to test Loosehead against tightly bounded real-world problems.