Report
Prospector Point · the engineer's deliverable and what stands between it and generation
Readiness
- Report candidate
- None designated
- Revisions computed
- 0
A report is generated from one locked revision, never from the working draft.
2 conditions are not met, and 5 cannot be tested until a revision is designated.
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.
Not tested yet. Nothing is designated as the report candidate, and this tests that revision rather than the one last calculated.
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.
Designate an immutable revision as the report candidate.
Every component and the complete assessment reconcile exactly in the designated revision, with remainders allocated deterministically.
Not tested yet. Nothing is designated as the report candidate, and this tests that revision rather than the one last calculated.
No assessment unit in the designated revision is unknown, and every unit below the threshold carries a remedy or an accepted basis.
Not tested yet. Nothing is designated as the report candidate, and this tests that revision rather than the one last calculated.
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.
Not tested yet. Nothing is designated as the report candidate, and this tests that revision rather than the one last calculated.
Engineer-owned changes and basis values are attributable, so a reviewer can ask a person why a number is what it is.
Not tested yet. Nothing is designated as the report candidate, and this tests that revision rather than the one last calculated.
A complete report establishes the structure to generate, and where signature and seal remain external.
No complete engineer report has been supplied, so the document template and its signature workflow are undefined.
Bundle
What generation will produce
- Report
- The engineer's report, from 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.