Forest condition report card
WS4 can package already-computed condition indicators into a small Markdown or JSON report card. The card is a reporting surface, not a new condition model and not an operational early-warning system.
Contract
The schema is ws4.forest_condition.report.v1. A report has:
report_id,scenario_id,generated_utc,periodIdentity and reporting window.
review_statusOne of
draft,provisional, orreviewed.indicatorsA list of condition indicators.
alertsAdvisory alert rows. Every alert is explicitly advisory.
provenanceSource and version metadata.
Each indicator carries:
name,value,unitThe measured value.
source,source_versionThe product, model card, or calculation that produced it.
uncertainty,uncertainty_kindOptional error or interval metadata.
applicabilityDomain or abstention statement.
statusok,outside_domain,missing, orreview_required.trendimproving,stable,declining, ornot_available.
From a run
ws4 condition-card \
--run runtime/my-run \
--out runtime/my-run/condition \
--markdown
The command reads account_values.csv and summarizes each feature.*
account. The final value becomes the indicator value; the first-to-final change
sets the trend. Every derived indicator is marked review_required, has no
RMSE, and records ws4.account_values as its source. This is a reporting
view of a run, not an independent condition validation.
The command writes forest_condition_card.json and, with --markdown,
forest_condition_card.md. Missing columns, an empty table, non-numeric or
non-finite values, and a table with no feature accounts are rejected.
Example
python - <<'PY'
from ws4.forest_condition import load_report
report = load_report("examples/forest_condition/card.json")
print(report.to_markdown())
PY
The fixture at examples/forest_condition contains a JSON card and its
rendered Markdown. It combines a BA-only inventory indicator with a DHI
indicator to show the provenance and abstention fields.
Boundaries
The card does not compute indicators, run the simulator, or change the objective, constraints, growth, or solver.
Alerts are advisory. They are not treatment triggers, constraints, or liability-bearing operational warnings.
The card must carry a review status.
draftandprovisionalcards must not be presented as reviewed.Missing or non-finite values are rejected; they are not silently imputed.
DEC-02remains dependent on a real condition/alert source (DIS-03); this contract alone is not an early-warning product.