How HUBL reasons and where responsibility remains

HUBL reasoning should be inspectable. A user should be able to see how evidence, context, assumptions, challenge, alternatives and uncertainty lead to a Current HUBL View, a Recommendation where justified and a next action.

The reasoning chain

A public way to understand HUBL's reasoning is:

Evidence + context + assumptions + challenge + alternatives + uncertainty -> Current HUBL View -> Recommendation where justified -> next action.

This is conceptual rather than an internal engine diagram. It describes the product behaviour users should be able to inspect.

A claim is not automatically established fact

A claim made during an investigation is not automatically accepted as established fact. HUBL may need to investigate it, qualify it, challenge it, treat it as an assumption or leave it unresolved.

This matters when a supplied claim is important to the outcome. If the case depends on it, the claim should not disappear into the reasoning unnoticed.

Evidence supports a claim within a scope

Evidence does not prove everything. It supports specific propositions within a scope.

One good source can support a factual claim without validating the entire Recommendation. HUBL should preserve that distinction so the user can see what the evidence actually carries.

A recommendation is an inference

A HUBL Recommendation is a reasoned inference based on evidence, assumptions, context, alternatives and uncertainty. It is not itself a source fact.

A recommendation is not a source fact. It is HUBL's action-oriented conclusion from the investigation when the available basis supports one.

This distinction helps keep a Recommendation useful without making it look more certain than the underlying case allows.

Inspectability

The user should be able to understand what evidence mattered, what assumptions mattered, what changed the view, what uncertainty remains, why alternatives were weaker or stronger and why the Recommendation follows.

Inspectability does not mean every detail is equally important. It means the material basis of the conclusion should be visible enough to question, correct or act on.

When the case changes

A conclusion may change when the underlying evidence or circumstances change. New evidence, corrected context, changed constraints or a real-world test can alter the Current HUBL View or Recommendation.

That is desirable when the case genuinely changes. It should not be confused with inconsistency.

Where HUBL should stop

HUBL should not force certainty when the evidence does not support it. Valid outcomes include a Current HUBL View only, a conditional Recommendation, more investigation needed, a real-world test required, escalation or deferral.

The right output depends on what the investigation can responsibly support.

The decision owner

The decision owner is the person or authorised group responsible for the final decision. HUBL can inform, investigate, challenge and recommend. The decision owner retains authority and accountability.

Some decisions involve values, authority, timing, risk ownership or organisational context that HUBL may not fully possess.

Organisational review

In organisational use, some decisions may require additional review or governance before commitment. That is a responsibility boundary, not a configuration guide.

This page does not document Enterprise administration, access controls or operational governance settings.

Checked, validated and escalated

Some organisational workflows may distinguish checks performed, standards met or additional review required. Validated should never mean guaranteed correct.

Those ideas are referenced here only as responsibility concepts. Detailed governed workflows should be documented separately when the product contract is established.

The responsibility boundary

Evidence can be incomplete. Circumstances can change. HUBL may not have all organisational context. Some decisions involve values, authority or risk ownership outside HUBL.

HUBL recommends. The authorised person decides.

That is not a generic disclaimer. It is the practical boundary that lets HUBL be useful for serious decisions without pretending to hold authority it does not have.

---

Related pages

To understand the evidence basis behind this reasoning, see Understanding evidence and uncertainty.