INDEPENDENT POLICY & RESEARCHConceptual framework Edition 0.16.4
Methods and public accountability

A result should survive
independent scrutiny.

Method version ${METHOD_VERSION}. Older 0.1.0 input files can be imported and are recalculated using the current method. All calculations run locally; optional public-data retrieval is separate from the calculation engine. Unknown results remain null with warnings.

Five evidence classes

Input origins and missing data

Exports distinguish synthetic examples, manual assumptions and public-source observations. Locally uploaded data retains a source record and should be reviewed before classification. Empty fields, undefined values and null are not zero. Nonfinite numbers, inconsistent units and impossible dates fail validation. Counts cannot be negative; signed fiscal changes remain permitted where the formula allows them.

Computation versus empirical validity

Independent fixtures check conservation, hand-calculated values, edge cases and rejected invalid inputs. They do not establish that an input is accurate, an effect is causal or an approach works in the real world. A simple minimum-capacity model supports a single-path series; a branching or feedback network needs a separate flow model. Linear sensitivity supports a declared expression, not arbitrary causal relationships.

Provenance and audit

Every metric retains its input sources and transformation equations. JSON exports include method version, full inputs, output, assumptions and SHA-256 checksums. Imports recalculate from the inputs. Hashes establish content equality, not truth, identity or source authenticity. Editing source metadata remains a human responsibility.

Comparison and authority

Declare equal resources, budgets, staffing, release dates, evaluation periods and criteria. Material declared differences return not_comparable. No country multiplier, general safety score or war probability exists. A blocked or pending authority gate stops a transaction-dependent evaluation. Supplied approval is never independently certified by the software.

What still requires research?

Domain-specific specializations are marked core-backed exercise or planned. Forecasting, causal claims and recommendations require independent datasets and validation beyond these calculations. No live API import updates a scenario automatically. The original research hypotheses and Scenario Studio remain separate and unchanged.