Report
Cottonwood Bend · the engineer's deliverable and what stands between it and generation
Readiness
- Report candidate
- demo-cottonwood-bend-r1
- Revisions computed
- 1
Every condition is met. Generation writes the schedule and both manifests from the locked revision; the report document itself comes from the template.
Every parcel in the dated source roster has a membership decision, and nothing was rejected into the roster. County or recorded-plat reconciliation remains a separate authority check when the source is a client schedule.
The resolver policy is recorded as an accountable project decision before valuations are relied on.
The named method and its rationale are recorded as an accountable project decision.
The threshold used for every assessment-unit test is recorded as an accountable project decision.
One computed revision is named as the report candidate and still matches the current assessment truth.
Every component and the complete assessment reconcile exactly in the designated revision, with remainders allocated deterministically.
No assessment unit in the designated revision is unknown, and every unit below the threshold carries a remedy or an accepted basis.
Every issue raised for the district manager has a recorded resolution before finalization.
Every value the report relies on resolves to a dated artifact whose hash still matches and which the engineer has accepted.
Engineer-owned changes and basis values are attributable, so a reviewer can ask a person why a number is what it is.
A complete report establishes the structure to generate, and where signature and seal remain external.
Bundle
What generation will produce
- Report
- The engineer's report, from this project's template and the locked revision
- Assessment schedule
- Rows copied from revision results, with no arithmetic in the document layer
- Revision manifest
- The revision's identity, inputs, and reproducible results
- Evidence manifest
- Every supporting artifact, with its hash and capture time
Signature and seal stay outside the product. Correcting a generated report creates a successor revision and a new bundle rather than replacing one, so nothing that has been issued is silently rewritten.