Synthetic demonstration scenario
A fictional scenario, shown end to end. The page is rendered by the real product code, so the structure is exactly what a real evidence package would produce. Everything filling that structure is invented.
Every detail on this page is fictional
All organizations, dates, datasets, participants, findings, and scenario outcomes on this page are fictional demonstration content created solely to show product structure.
Demonstration workspace. This is sample content and does not represent an institutional review, validation, endorsement or municipal decision.
No city, department or organization has evaluated Canopulse. No validation study, municipal pilot or institutional review described here took place.
Scenario record: what an engagement captures
- Name
- Shade siting evaluation, sample engagement
- Organization
- organization-9a114cf85d2d
- Type
- combined
- State
- Completed
- Screening release
- CA_2026.07_CES5
- Methodology
- UCRI-CA v2026.07
- Opened
- 2026-03-02
- Completed
- 2026-06-28
The organization shows as an identifier rather than a name because this sample recorded a decision not to publish. An organization is named in an artifact only while its own written consent says so, and withdrawing that consent removes the name from every surface at once, including packages generated afterwards.
People appear as pseudonyms here and in every generated file. Canopulse holds the mapping and no artifact ever contains it, so a package can be shared without naming the individuals who took part.
Scenario charter: what is agreed before any work
- Purpose
- Establish whether a canopy screening index is usable as one input to shade siting, and record where it is not.
- Research question
- Does the canopy component agree with an independently collected canopy measure over the same tracts, and where does it disagree?
- Accepted
- 2026-03-14
- Amendments
- 1
What the charter forbids: This engagement does not establish that the screening release is correct, does not approve any siting decision, and must not be cited as validation of the index.
The charter is digested when it is accepted, and every amendment produces a new digest. Both appear in the verification record, so a reader can tell whether the document they hold matches the agreement the work was done under.
Scenario datasets: how independence is derived
| File | Independent | Why |
|---|---|---|
| canopy-reference-sample.csv | Yes | Canopulse did not produce, transform, select or label this data. |
| internal-tree-inventory-sample.csv | No | Canopulse transformed the target outcome. |
Independence is derived from four declared facts about what Canopulse did and did not do with a dataset. It is never a box somebody ticks. A comparison against a dataset that is not independent is a consistency check, and the package says so rather than counting it as validation.
Scenario result: how a screening comparison is recorded
- Validation status
- Completed, inconclusive
- Independent validation completed
- No
- Canopy component against an external reference
- Inconclusive
The two measures agree over most of the sampled tracts and disagree over a cluster of low-density tracts where the reference survey recorded canopy the screening layer does not. The sample is too small to say whether that is a systematic difference or a property of these tracts, so the honest answer is that this does not settle the question.
The protocol was frozen and digested before the comparison was run, so the success criteria could not be adjusted after the answer was known. An inconclusive result is recorded as inconclusive and appears unchanged in every artifact.
Scenario deployment: how a departmental trial is recorded
- Department
- Sample City Public Works
- Outcome
- Requires modification
- Evaluation period
- May to June 2026, one planting season
Known confounders: The shortlist was also shaped by which streets were already scheduled for resurfacing, which is not recorded in any of the three inputs.
A pilot outcome is one of four words and none of them is a score. Confounders are recorded because a pilot that does not name them is a story rather than evidence.
Scenario limitations: every one a package declares
- Origin of this material. Demonstration workspace. This is sample content and does not represent an institutional review, validation, endorsement or municipal decision.
- What this package is. A record of a controlled institutional engagement. It is not a validation of the screening release, not an endorsement by any organization named in it, and not evidence of causal impact.
- Participation. An organization taking part is not agreeing with the result, and completing an engagement is not approval of the tool for any purpose.
- Association and effect. Validation compares two datasets under stated rules and reports where they agree. Agreement is not causation, and nothing here identifies an effect.
- Screening, not assessment. UCRI is a screening index over census tracts. It does not determine eligibility, does not replace a site assessment, and does not describe any individual property, ZIP code or parcel.
- Usage and outcome. Downloads, page views and completed steps describe activity. They are not outcomes, and no impact figure is derived from them.
- Reproducibility. Per-file digests are stable across runs. The ZIP container is not byte-identical between processes, so check the contents against verification/checksums.sha256 rather than comparing archives.
- Charter limitations. Screening is not a site assessment and does not describe any individual property, ZIP code or parcel.
- Prohibited interpretations. This engagement does not establish that the screening release is correct, does not approve any siting decision, and must not be cited as validation of the index.
- Dataset: canopy-reference-sample.csv. Collected in two passes eleven months apart, so growth between passes is not distinguishable from measurement difference.
- Dataset: internal-tree-inventory-sample.csv. Counts street trees only. Canopy on private land is not represented at all, and in this sample that is most of it.
- Dataset independence: internal-tree-inventory-sample.csv. This dataset is not independent, so a comparison against it is a consistency check rather than a validation. Canopulse transformed the target outcome.
- Pilot: Sample City Public Works. One season, one department, one city. Nothing here generalises.
- Pilot confounders: Sample City Public Works. The shortlist was also shaped by which streets were already scheduled for resurfacing, which is not recorded in any of the three inputs.
- Final limitations. This engagement did not establish that the screening release is correct. It established that a structured review could be run against it and recorded what the reviewers found.
This list is assembled from the charter, every dataset, every recorded deployment and the standing limitations that apply to all engagements. It appears in every PDF, the workbook and the package README. Required limitations cannot be removed, while presentation and ordering may be adapted without changing their meaning.
What you actually work from
Four things do the work: a written summary of what was done and concluded, the tract table behind it, the method and source appendix, and the underlying data as CSV so you can take it elsewhere.
Everything else in the archive exists so a reader can check those four. A manifest naming every file and every file deliberately not generated, SHA-256 checksums covering all of it, the contract as JSON, and a verification record. You should not need to open them; they are there so somebody sceptical can.
Every file in a package generated from an evaluation or demonstration workspace carries the origin notice, including the public verification page that the QR code on each cover points at.
Try it with your own work
An evaluation workspace is free and gives you every surface shown here.
Create a free workspace