INPUT LEDGER
What is known, entered, or assumed.
| Input | 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 CALCULATION
Follow the intermediate result.
Classify A
Formula or rule: Published week → precision=week
Result: Do not manufacture a day
Classify B
Formula or rule: Published day → precision=day
Result: Exact-date freshness is calculable
Rank
Formula or rule: Use conservative recency interval for A
Result: Uncertainty remains visible
Interpret
Formula or rule: Stocking evidence ≠ fish survival or catch
Result: Research shortlist only
DECISION READING
What the result means.
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.
SENSITIVITY
What could change the answer.
- 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.
BOUNDARIES
What this case does not 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.
OFFICIAL SOURCES
Where factual context is verified.
RELATED FINVECTOR CASES
Change one assumption and compare again.
Each case keeps inputs, arithmetic, evidence, and uncertainty in separate layers.