Your first study
The fast path in Quickstart produces a synthetic study. This page explains what to read and what not to infer from it.
Read the run in this order
The run manifest identifies the run type, status, data version, model versions, seed, and artifact index.
The compiled dataset is the decision-unit table: corridor segments and their site, vegetation, treatment, access, and observation attributes.
A plan artifact — when the workflow produces one — lists selected segment-year-method actions with costs, hours, assumptions, and risk notes.
The simulation run replays the plan or schedule through growth and treatment transitions. The synthetic prototype writes a
schedule.csv.The summary report is a human-readable digest, not an additional source of truth.
The contracts behind these files are in Artifact contracts and Contract index. If a field is absent, do not infer a default from a report.
What the synthetic example demonstrates
the fixture → compile → plan/replay → report path;
a deterministic, inspectable dataset and plan;
cost and service accounting against a declared budget;
exact replay of a plan;
artifact contracts that fail loudly on malformed input.
What it does not demonstrate
a field-calibrated growth model;
a real asset owner’s access, outage, safety, or clearance standard;
a globally optimal treatment schedule;
a public release of any private network data.
Continue with The model, The planning stack, and Limitations and boundaries.