Coverage
One setup. Several jobs.
The compare page asks which of your systems fits one job. This asks the opposite, and it is the question you actually face when packing: does this rod cover the river day and the lake day, or are you carrying two? Same engine, run once per job. Nothing is averaged across them — a job without enough evidence stays unassessed on its own terms.
The finding, why it matters, and the fix
The system under test
Jobs it would have to cover (0 selected)
Your trips
0 of 24 kept
The days you actually fish, kept by name. Set a job up in the console, then keep it here; coverage runs the setup against every trip you select. Trips stay in this session, in this browser, and travel only inside a session export.
Nothing to keep yet — state a water type or a target class in the setup.
No trips kept yet. Until there are, coverage can only be run against the job in your setup and the worked examples below — which is a demonstration rather than an answer about your own season.
Choose the jobs this setup would have to cover.
The whole bag
Two setups and two days is where this starts saying anything. Save another and name a second trip.
Rack Passport
Carry the rack decision as evidence
Exports the setups on file, the selected named jobs and the same removal-simulation resilience report shown in Whole Bag. No product recommendations or inferred inventory are added to the file.
Hook the Horizon · decision chain
Once you know what it covers
Field Ops owns the active trip. Water → Species → Forage when needed → Presentation → Tackle → Knot when the connection is unresolved → Field Ops → Debrief. Rig Signal is an optional device/electronics validation sidecar, not a required stage. Context travels only when you follow a link, and coordinates are stripped in both directions. Tackle Link keeps a local receipt of packet metadata and field paths when a packet-carrying handoff is actually followed.
Knot Analyst
Which connection joins these materials and how that connection can fail
If the connection itself is still unresolved, Knot Analyst owns that decision rather than Tackle Link guessing a knot.
Field Ops Desk
Keep the active trip, carry confirmed context, and turn the day into learning
Return the confirmed system result to Field Ops so the active trip — and the later debrief — keeps the same context.
Rig Signal
Whether a device or electronics claim is supported by the evidence behind it
If part of this setup rests on a claim printed on a box — a drag figure, a depth rating, a sensitivity number — Rig Signal checks what evidence sits behind it. Nothing here waits on that answer.