high-stakes-analytics-decision-lab

Why this exists

High-stakes analysis often fails before the model: the question is underspecified, the data contract is implicit, cleaning choices are hidden, uncertainty is treated as independent, or a recommendation is written because the template expects one.

This repository is a platform-neutral Agent Skill and reproducible research portfolio built around a stricter sequence:

The result is not a fixed report generator. It is an evidence-gated orchestration system that can stop, ask for a named decision, or produce a bounded analytical product without upgrading weak evidence into a stronger claim.

Start in three steps

1. Install the Skill

npx skills add limingrui679-design/high-stakes-analytics-decision-lab -g

The Agent Skills installer discovers the compact package under skills/high-stakes-analytics-decision-lab/: 39 files and about 472 KiB, rather than the full research portfolio. Its machine-readable file and hash contract is in bundle-manifest.json.

Use docs/getting-started.md for Codex-specific, no-install, and direct repository options.

2. Ask for the evidence outcome

$high-stakes-analytics-decision-lab
Run the data-readiness gate on this source, preserve the original file, and
select only the analytical routes the evidence supports. Produce an Evidence
Intelligence Report. Add a Decision Intelligence Brief only if the evidence
and decision context justify one.

Start with the decision or evidence question—not a preferred model. A valid result may be a bounded action, a pilot requirement, targeted diligence, an evidence request, negative validation, or do_not_deploy.

3. Review the evidence package

Every complete project keeps the narrative, machine result, visual evidence, and source lineage together:

report.md                    # primary Evidence Intelligence Report
results.json                 # machine-readable analytical result
chart-map.json               # figure-to-question and source contract
figures/*.svg                # accessible analytical visuals

A justified decision layer adds decision-report.md, decision-results.json, and its own figure contract. It never replaces the primary evidence product.

Direct repository entry points

How it works

The fixed evidence spine remains stable while the case-specific analytical layer changes.

The data gate can stop the workflow

Uploaded row-level data do not go directly into a model. The system preserves the original, establishes a contract, checks grain and keys, profiles quality and privacy, and produces a dry-run remediation plan.

Only safe normalization can run without approval. Deletion, imputation, outlier treatment, category merging, unit conversion, target correction, and grain changes require explicit action IDs. The processed copy never overwrites the source.

Four routes, no mandatory recommendation

Routes may compose, but a later route cannot erase the quality and evidence requirements of an earlier stage. Read the full system design in docs/architecture.md.

Two products, one evidence contract

Every material figure is generated from the shared editorial evidence system, includes a title and description, and is paired with its analytical question, supported interpretation, and claim boundary. The visual system is part of the evidence contract, not decorative reporting.

Fifteen complete evidence paths

The public portfolio contains 15 primary reports and 10 conditional briefs—25 intelligence products in total—plus 119 canonical accessible figures: 50 evidence figures and 69 decision figures.

The cases span operational demand, distribution shift, scarce-capacity pilots, temporal model transport, tail-risk decisions, human-in-the-loop triage, commercial diligence, mitigation allocation, filing review, clustered field experiments, survival evidence, policy evaluation, repeated-measures inference, population transportability, and spatial equity.

They intentionally end differently: some support a bounded decision, some require a pilot or targeted review, and some stop at an evidence request or do_not_deploy.

Verification you can reproduce

The current stable release is v1.1.2. Its versioned source package and SHA-256 checksum are published together; the release identity is also recorded in CITATION.cff, CHANGELOG.md, and RELEASE-MANIFEST.json.

make verify

This runs the standalone regression suite and rebuilds all fifteen projects in