Skip to content
Hook the HorizonTackle Link Analyst
Autosave on

Hook the Horizon · field tool

One chain.
The weakest supported link
decides.

Start with the job — the water, the fish, the flow, the landing problem — then work backward through rod, reel, line, leader, connection and presentation. Declared ratings govern. Heuristics stay labelled. Missing specifications stay unknown.

Local-first · no locations collected · educational evaluation only

  • River

    Current load, precision, abrasion, landing in flow

  • Lake

    Depth change, vegetation, wind, search vs static

  • Ocean · Inshore

    Salt corrosion, tide, structure abrasion, stronger fish

  • Deep-sea · Offshore

    Continuous drag, capacity, depth, big-game loads

Quick-start situations

Example setups fill the job and the chain. Every figure remains editable — expand the review to see exactly what changed.

Most common starts

All situations

Step 01 — the job

The job

Start with the job, not the gear. What you enter here re-orders which links and which risks surface first.

Water type

No exact locations are requested or stored. Everything stays in this browser.

Step 02 — fast path

Major components

The finding, why it matters, and the fix

Ready to start

Start with the water and the main line

Add water type and line strength, or load an example setup. The check waits until those two are in. Missing ratings stay blank — nothing is invented to fill them.

Next: load an example lake setup, or see a worked start.

Browse example setups
  • · Water type
  • · Main line strength
  • · Rod power or published line rating
  • · Published max drag

Saved checks (0)

Saving a check freezes the current job and chain so it can be replayed and compared later. The full ledger, the step-through walk and batch checking all live on the check page.

Open the full check →

Hook the Horizon · decision chain

Where this goes next

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.