Canonical field tools desk

Horizon Desk

One desk for Hook the Horizon field tools — not WordPress to five domains. Decide whether a public water is workable, check your system, plan presentations from owned inventory, save continuity in Field Locker. Ready badges are live-probed; broken routes never advertise Ready.

Named public waters only · no exact coordinates · fail closed

Fish species explorer — streamside context for field tools

Live route verification

Probing launch URLs and health endpoints…

Field Decision Suite

Before you commit gear

Decide whether a public water is currently workable — access, safety, and streamside clues before you commit gear.

Mountain lake at dawn — public-water conditions context
Verifying…
Freshness limits labeled

HTH-HH-001

Honey Hole Intelligence

Check if this public water is currently workable

Public-waters field intelligence for named public destinations only. Access, regulation, closure, hazard, conservation, and conditions readiness — so you can decide whether a water is currently workable.

Does not: Private or secret access details · Exact GPS coordinates

Streamside insect and fly detail — hatch hypothesis context
Verifying…
Local scoring

HTH-HM-001

Hatch Match

Turn streamside insect clues into a supported hypothesis

Local hypothesis tool for streamside insect / biological identification support. Uses reviewed biological and observational evidence. Scoring stays on-device. Designed for a 60-second field flow.

Does not: Verified real-time hatch reports · Location or catch data

Gear & Field Planning Suite

Systems, presentations, claims

Evaluate systems, plan presentations from owned inventory, and separate measurement from marketing on devices.

Verifying…
Local library

HTH-SC-001

Compatibility Builder

Find the weakest link in your rod · reel · line · leader · presentation system

Local-first fishing system compatibility evaluator. Quick mode for a fast check; Advanced for full library work. Identifies hard rating conflicts, weakest supported link, and practical next actions.

Does not: Performance guarantees or catch claims · Inventing manufacturer values

Verifying…
Inherits upstream freshness

HTH-PP-001

Presentation Planner

Decide what to actually fish today from owned inventory

Central orchestration tool. Combines public-safe results from Honey Hole, Compatibility Builder, and optional Hatch Match evidence into best-supported, contrast, and fallback plans — with one-click handoffs.

Does not: Skipping a Hard Stop from access or compatibility · Purchase-first recommendations

Field electronics and sensors — claim evaluation context
Verifying…
Catalog versioned

HTH-RS-001

Rig Signal

Separate documented measurement from marketing on fishing devices

Claim evaluation for fishing devices and sensors. Quick mode for a single claim; Advanced for full evidence work. Separates documented measurement from marketing, prototypes, and non-reproducible output.

Does not: Bite detection · Species identification

Verifying…
On-device catalog + engine

HTH-KK-001

Knot Intelligence

Decide the right connection for you — and diagnose why this one is failing

Personal decide + diagnose for fishing connections. Not a Knot Finder library clone: hard constraints and field-fit ranking answer what you should tie; a symptom-first failure playbook answers why it broke, slipped, or will not seat — with retie guidance.

Does not: Browsing or filtering the teaching library (that is Knot Finder on the blog) · Catch guarantees or marketing “best knot” rankings

Optional guided path

Trip Prep sequence

Honey Hole → Compatibility Builder → Presentation Planner. Tools stay independent — this path sequences the most common field workflow.

Open Trip Prep
  1. 1

    Access & conditions

    Honey Hole Intelligence

    Confirm the public water is open, legal, and safe enough to fish. Fail closed if sources are stale or conflicted.

    Reader chooses when to carry results

  2. 2

    System check

    Compatibility Builder

    Evaluate rod · reel · line · leader · presentation. Clear hard conflicts and note the weakest link before you plan.

    Reader chooses when to carry results

  3. 3

    What to fish

    Presentation Planner

    Carry public-safe results forward. Get best-supported, contrast, and fallback presentations from owned inventory.

    Reader chooses when to carry results

Conditions surface · illustrative

Conditions context

Water temperature · Trend over 72 hours

Illustrative storefront chart. Live gauges and freshness live in Honey Hole Intelligence — this desk only frames the decision job.

Moving water surface — temperature context
Demo series
Not a live gauge

Open Honey Hole for named-public-water gauges, freshness state, and fail-closed access decisions.

Full conditions view

Explicit handoffs only

Carry results forward — never silently

Tools stay independent. When you choose, a public-safe packet can move downstream. Nothing is uploaded; nothing is inferred across apps without your action.

Honey Hole

HTH-HH-001

Public-safe conditions & access packet

Planner

HTH-PP-001

Compatibility

HTH-SC-001

System summary (latest saved or library)

Planner

HTH-PP-001

Hatch Match

HTH-HM-001

Bounded biological clue packet
Optional

Planner

HTH-PP-001

Rig Signal

HTH-RS-001

Public-safe claim packet (horizon.rig-signal) — optional soft watch
Optional

Compatibility

HTH-SC-001

Compatibility

HTH-SC-001

System clear — pick terminal / line-to-line connections
Optional

Knots

HTH-KK-001

Non-negotiable

How the suite stays trustworthy

Fail closed

Access, legality, safety, and hard rating conflicts never default to “looks fine.”

Freshness is first-class

Stored URLs and version labels are not current claims. Consequential outputs carry an explicit freshness state.

No exact location

Review queues, TTLs, and correction logs stay public-safe. Named public waters only.

No catch guarantees

Tools refuse “best water” rankings and “will catch” framing. Hypothesis, supported, incomplete, and Stop stay precise.

Ready means probed

Desk never shows Ready from a static label alone. Launch URLs and health endpoints are verified live.

Shared privacy boundary

Local-first · public-safe · no forced account

  • No exact coordinates collected or stored by the suite
  • No private access details or secret spots
  • Local-first libraries and mastery where declared
  • No forced account for core field tools
  • Explicit handoffs only — nothing moves between tools until you choose
  • Fail closed on access, legality, hazards, and hard rating conflicts
Read the boundary