Public warning / geospatial evidence / consequence priority

Disaster Risk & Decision Intelligence

Evidence-controlled disaster-risk software that can ingest live official warning data while refusing to treat a warning as proof of every downstream local consequence.

LIVE SOURCE EXECUTION / EXTERNAL EVALUATION PROGRAM ACTIVE
01 / PROBLEM

A public warning is authoritative for the warning. It is not automatically proof of local impact.

The system separates official hazard state from downstream consequence, feasibility, responder danger and local action. That boundary is central to the product rather than an afterthought.

What the system does

The source fabric connects current public-warning and historical hazard evidence to lifecycle/provenance state before any richer consequence or decision claim is permitted to travel.

The evaluation program then tests bounded consequence-priority behavior against explicitly defined comparators rather than claiming to replace official warning operations.

02 / CURRENT EVIDENCE

What has actually been demonstrated.

Each item below is deliberately narrower than a product-readiness or superiority claim.

Live NWS ingestion

Actual product path executed in AWS

A bounded August 2026 run used the product-owned National Weather Service connector to retrieve current Alabama active alerts and emit new warning lifecycle changes with provenance.

LIVE SOURCE / AWS / PRODUCT-OWNED CONNECTOR
Claim boundary

Warning ≠ local consequence

The public-warning path is allowed to carry the official warning state while local consequence/action remains separately evidenced.

AUTHORITY SEPARATION / PUBLIC WARNING CEILING
Historical/live source fabric

Replay and current source bodies

The product has source catalog, historical replay and live-source validation surfaces rather than a single demo endpoint.

SOURCE FABRIC / REPLAY / PROVENANCE
External qualification

Llama-first evidence → current Mistral judge route

Earlier AWS evaluation work established the external-judge path with Llama. As current Bedrock custom-metric support changed, the active qualification route moved to Mistral Large. Judge output remains calibration/evaluation evidence and does not override deterministic invariants, live product receipts or confirmatory gates.

AWS BEDROCK / MISTRAL JUDGE / EVALUATOR-MIGRATION ROBUSTNESS
03 / CLAIM CEILING

What this page does not claim.

It does not claim equivalence to the National Weather Service, warning-issuance authority, autonomous emergency action, confirmed local impact from CAP alone, completed confirmatory superiority, or production public-safety readiness.

Current development

The current research/engineering path is closing canonical live-state composition and externally controlled evaluation geometry so consequence-priority claims can be tested without leaking future truth or borrowing authority from the warning source.

Kingan Logic systems

Evidence first.
Then movement.