Synthetic corridor fixture
The synthetic corridor fixture is a public-safe, deterministic test case. It covers two corridors, five segments, mixed functional groups, one access gap, one monitoring gap, one structure, a plan, a Pareto archive, an operations timeline, a demo manifest, and a tiny known-optimum case.
Location: examples/synthetic-corridor/.
Generate
brushline fixture --out examples/synthetic-corridor
brushline fixture --out examples/synthetic-corridor --force
The generator is brushline.fixtures.synthetic.generate_fixture. It uses a fixed seed and a fixed
creation time, so the committed fixture and a fresh build produce the same artifact digests.
Contents
Path |
Meaning |
|---|---|
|
The compiled dataset contract and the segment table. |
|
The corridor graph: two corridors, five segments, two spans, two treatment units, two access points, one structure, and two service standards. |
|
Five states, three treatment actions, one transition, and four observations. |
|
The 2026 plan with five actions and a CAD 5,300 total. |
|
The three archive plans. |
|
Three non-dominated cost/risk members and one balanced scalarization. |
|
Five timestamped crew events. |
|
The public demo manifest. |
|
The tiny known-optimum instance. |
|
The fixture manifest: seed, expected counts, artifact digests, and content digest. |
Expected values
Key |
Value |
|---|---|
Corridors |
2 |
Segments |
5 |
States |
5 |
Treatment actions |
3 |
Observations |
4 |
Structures |
1 |
Access gaps |
1 |
Monitoring gaps |
1 |
Plan actions |
5 |
Pareto members |
3 |
Timeline events |
5 |
Known optimum |
|
Known optimum penalty |
|
Warnings
The fixture is valid, but it deliberately records two warnings:
segment
s3has no access point;observation
o2covers only 40 percent of segments2.
The unknown state on s3 and the absence of an observation for s3 are the monitoring gap.
Tiny known optimum
tiny_optimum.json defines a one-segment choice between no treatment, mowing in 2026, and mowing in
2027. The objective is
penalty = 0.4 * (cost / 1000) + 0.6 * risk
The options are:
Option |
Cost |
Risk |
Penalty |
|---|---|---|---|
|
0 |
0.8 |
0.48 |
|
1000 |
0.1 |
0.46 |
|
900 |
0.2 |
0.48 |
The optimum is mow-2026. The search validation uses this case to check that an exact solver and the
metaheuristic adapter agree on a known answer.
Validation
brushline validate --dataset examples/synthetic-corridor/dataset
The test suite also validates the corridor, state, plan, archive, timeline, run, and demo contracts, and
rebuilds the fixture to compare its digests with fixture.json.
Determinism
The fixture uses a fixed seed and a fixed 2026-11-14T00:00:00Z creation time. JSON is written with
sorted keys and two-space indentation. The dataset table is CSV, not Parquet, so the table checksum does
not depend on a Parquet library version. A change to the generator changes the content digest; regenerate
the committed fixture and update the test expectation in the same change set.