SOURCE SNAPSHOT
Start with provenance and source scope.
INPUT AND EVIDENCE LEDGER
Classify every field before using it.
| Field | Value | Origin |
|---|---|---|
| Water A | Agency publishes a named week | Illustrative official-record pattern |
| Water B | Agency publishes an exact reported date | Illustrative official-record pattern |
| Current date | Known to the application | System input |
| Catch outcome | Unknown | Not observed by the source |
REPRODUCIBLE WORK
Run the quality-control chain.
| Check | Formula or rule | Result |
|---|---|---|
| Classify A | Published week → precision=week | Do not manufacture a day |
| Classify B | Published day → precision=day | Exact-date freshness is calculable |
| Rank | Use conservative recency interval for A | Uncertainty remains visible |
| Interpret | Stocking evidence ≠ fish survival or catch | Research shortlist only |
DECISION READING
The audit finding.
Water A can still have useful recent evidence, but the interface must say “week of” rather than fabricate a precise event date. Precision is part of the evidence, not a display detail.
HUMAN ACCOUNTABILITY + AI USE RECORD
The owner is accountable; the technical checks were AI-assisted.
The TOOOLBOX site owner authorized the publication scope and remains the correction contact. AI assistance was used for drafting, implementation, arithmetic recomputation, and source-link checks. This record does not claim line-by-line human fact-checking or licensed professional review.
- Record ID
- TB-FINVECTOR-07-20260906
- Owner role
- TOOOLBOX site owner and developer
- Technical check date
- 2026-09-06
- Human fact-check
- No separate human fact-check recorded
- AI use
- Drafting, code, arithmetic, and link checks
- Correction channel
- Public contact page
- Tested the classification rule with week-level and exact-day records without assigning a fabricated midpoint.
- Kept planned and reported-completion evidence as separate statuses throughout the example.
- Checked that freshness is not extended into a survival, catch, access, regulation, or safety claim.
BOUNDARIES
What passed data checks still cannot prove.
- This case does not identify a specific trip destination.
- Agencies can revise schedules and reports.
- Users must verify current regulations, closures, and access before departure.
SENSITIVITY
Failure modes to retest.
- Scheduled and completed stocking records should be labelled separately.
- A recent record can be outweighed by closures, unsafe weather, or uncertain access.
- Stocking quantity is not directly comparable when agencies report different life stages or units.
MORE FINVECTOR DECISION NOTES
Test the result yourself.
This note preserves a dated calculation. Change the inputs in the live workspace, or compare another evidence pattern below. Live source availability and results can differ from the dated example.