Causal & Cognitive Intelligence

Understand the mechanism.
Then let reality judge it.

Pythology is building an evidence-grounded reasoning architecture that keeps observation, inference, forecast and counterfactual scenario separate. EarthNet is its first live proving ground; Prometheus commits forecasts; Decision Futures compares consequential choices; Sentinel gives authorised humans a way to interrogate the chain.

EvidenceProvenance first
MechanismCompeting explanations
ProspectiveForecast before outcome
CalibratedReality closes the loop
Pythology causal and cognitive intelligence architecture

Core distinction

Correlation, prediction and causation
are different questions.

A model may forecast an outcome well without knowing whether changing one variable would alter that outcome. Pythology keeps these claim types visibly separate.

CORRELATION

What varies together?

Useful for finding relationships, but vulnerable to confounding, selection effects and hidden common causes.

PREDICTION

What should happen next?

A testable expectation that can later be scored. Accuracy alone does not prove the proposed mechanism.

CAUSATION

What could make the change happen?

Requires explicit mechanisms, assumptions, alternatives, time order, contradictory evidence and tests capable of weakening the explanation.

Shared reasoning architecture

From evidence to mechanism,
choice and learning.

The purpose of the stack is not to make a model sound certain. It is to make the path from evidence to belief inspectable enough that a human can challenge it and later determine whether it deserved confidence.

01 · EVIDENCE

Preserve the state

Source, timestamp, missing information, contradictions and observation quality remain visible.

02 · CAUSAL

Compare mechanisms

Keep plausible explanations and confounders alive instead of quietly selecting the first persuasive story.

03 · PROMETHEUS

Commit the forecast

State what should happen before the answer is known, preserve uncertainty and freeze the original record.

04 · DECISION FUTURES

Compare choices

Where a genuine decision exists, branch from the same frozen evidence and compare conditional downstream consequences.

05 · SENTINEL

Interrogate the reasoning

Ask why branches differ, what is degraded, which assumption is weakest and what evidence could reverse the conclusion.

06 · OUTCOME

Calibrate against reality

Resolve forecasts and the decision actually taken against later evidence without rewriting the original belief.

Prometheus

A forecast becomes useful
when it can be wrong.

Prometheus creates timestamped, falsifiable expectations from the current evidence and causal state. Forecast confidence remains labelled and is only strengthened by accumulated resolved outcomes, not by how convincing the explanation sounds.

CommitRecord the forecast before the outcome is known.
ResolveUse later independent evidence to determine what occurred.
CalibrateMeasure whether confidence matched observed frequency and keep misses in the ledger.
PROMETHEUS / ACCOUNTABLE FORECASTLIVE VALIDATION
Evidence stateFrozen
MechanismInspectable
ForecastTimestamped
OutcomeIndependent later evidence
CalibrationAccumulated record

Decision Futures

What changes if
the choice changes?

Decision Futures extends Prometheus from baseline forecasting into explicit counterfactual branches. It is used only where a meaningful decision can affect a measurable outcome and the comparison can be made responsibly.

BASELINE

What if nothing changes?

Start from the same frozen evidence and causal state used by Prometheus.

ALTERNATIVES

What if we choose differently?

Pre-register a small number of feasible interventions, assumptions and expected consequences before the answer is known.

BOUNDARY

Score only what reality tested.

If humans choose branch B, B can be compared directly with the later outcome. Unchosen A and C remain counterfactual hypotheses until separately supported.

Scenario is not evidence merely because it is detailed. Decision Futures preserves assumptions, uncertainty and the difference between simulated consequences and observed outcomes.

Research and deployment collaboration

Causal systems require domain evidence.

Pythology is interested in discussions with organisations holding well-defined observations, intervention histories, measured outcomes or simulation environments suitable for prospective evaluation.

No sensitive operational, patient or restricted research data should be submitted through this public form.
Pythology will review the problem and respond directly.