Vessel Quest

The boat is the game engine. The sea is the level designer. The logbook is the quest log.

Vessel Quest makes the scoring system visible on working fishing vessels. Captains were always accumulating XP in the form of local knowledge, sea hours, and hard-won data. The only thing missing was the scoreboard.

This is not a fishing simulator. This is real fishing, with the data layer made visible.

---

The Core Insight

A fishing vessel already satisfies the literal definition of a game engine:

• Inputs: fuel, bait, crew labor, weather
• Outputs: fish, data, wear, stories
• Constraints: fuel capacity, hold capacity, crew endurance, weather windows
• State tracked: engine hours, GPS position, catch totals, maintenance
• Rewards skillful play: more fish, less fuel, better data, safer crew
• Punishes mistakes: broken gear, injured crew, empty hold, sunk vessel

The game was always being played. Vessel Quest is the scoreboard.

---

The Two Problems We Solve

Problem 1: The Most Valuable Asset Is Unrecorded

The difference between a good fisherman and a great one is data. Water temperature on the day the sockeye came through. Moon phase when the halibut moved shallow. The exact bottom contour where black cod were found fifteen years ago.

This dataset lives in the most expensive, most fragile storage medium ever invented: a human brain. A brain that gets tired, sick, retires, moves away, or dies.

The logbook is the backup drive for the captain's brain.

Problem 2: Nobody Likes Writing in Logbooks

Writing in a logbook feels like bureaucracy, and bureaucracy is the opposite of why people go to sea. Captains start strong, then the fishing gets good and entries get sparse. By mid-season the logbook is a museum of good intentions.

Vessel Quest solves this by making the form feel like a game. The entry still says 0347, position 56.8N 135.3W, 400 lbs sockeye, 12 fathoms, flood tide — but now it comes with +15 XP, a progress bar, and the satisfying knowledge that you are 30 FishCoin closer to earning your crew a round of beers at port.

The ethics of gamification depend entirely on what behavior is being gamified. Gamifying data entry on a fishing boat is not exploitative. It gives the captain a tool that makes the tedious part of the job feel like the fun part.

---

The XP Is Attention Logged

XP is not a reward for completing tasks. XP is attention logged.

When you write in the logbook, you are not recording what happened. You are solidifying the act of having paid attention. The entry is the proof. The number is the measure.

This is the same qualitative change that separates:

• A novice from a craftsman
• A tourist from a local
• A reader from a writer
• A passenger from a captain

A Level 6 Captain is not someone who has done more work. They are someone who has paid more attention. The work was how they paid it.

---

Project Status

Phase 0 — Ideation and Schema Definition

• Core insight articulated (docs/01_the_boat_is_the_game_engine.md)
• XP-as-attention theory documented (docs/02_attention_ledger.md)
• Negative-space compounding documented (docs/03_negative_space_compounding.md)
• Quest design (docs/04_quest_design.md)
• Achievement design (docs/05_achievement_design.md)
• FishCoin economy specification (docs/06_fishcoin_economy.md)
• MVP scoring engine architecture (docs/07_mvp_scoring_engine.md)
• Schemas: LogEntry, Achievement, Quest, FishCoin (schema/)
• MVP scoring engine (Python reference implementation)
• CLI for log entry with XP feedback
• Achievement definitions pack
• Quest catalog data files

Target: A captain with a CLI on their laptop can log an entry, see their XP bar advance, unlock achievements, and accumulate FishCoin — all from real fishing data, no simulation.

---

Repository Layout

vessel-quest/
├── docs/                    # Ideation and design
│   ├── 01_the_boat_is_the_game_engine.md
│   ├── 02_attention_ledger.md
│   ├── 03_negative_space_compounding.md
│   ├── 04_quest_design.md
│   ├── 05_achievement_design.md
│   ├── 06_fishcoin_economy.md
│   └── 07_mvp_scoring_engine.md
├── schema/                  # JSON Schema definitions (Draft 2020-12)
│   ├── log_entry.schema.json
│   ├── achievement.schema.json
│   ├── quest.schema.json
│   └── fishcoin.schema.json
├── src/                     # Reference implementation (pending)
│   └── vessel_quest/
├── examples/                # Example logs, quests, achievements
├── tests/                   # Test suite
└── README.md

---

Design Principles

1. The game was always being played. We make it visible, we do not invent it.
2. Authentic gamification only. XP for attention actually paid, not for grinding. The system knows the difference because you know the difference.
3. The vessel is the source of truth. Real GPS, real catch, real weather. No simulation.
4. The logbook is sacred. An entry recorded is attention solidified. Never delete, only annotate.
5. The captain is the player. The crew are party members. The harbor is the save point.
6. Slow software for slow craft. Reliable over novel. Tested over feature-rich.

---

Lineage

Vessel Quest grew out of two parallel bodies of work:

• vessel-agent — the data capture system (NMEA, GPS, sounder) running aboard F/V EILEEN
• ai-writings — the ideation corpus where the boat-as-game-engine insight emerged

The first seed was THE_BOAT_IS_THE_GAME_ENGINE.md, written at 05:15 UTC with the hold full and the coffee good. The second seed was THE_ATTENTION_LEDGER.md, which recognized that XP is not experience points but attention logged.

---

Vessel

F/V EILEEN — 51' commercial fishing vessel Home Port: Southeast Alaska Primary Fishery: Power trolling (salmon), longlining (halibut/black cod) Captain: Casey

---

Vessel Quest v0.1.0 — Ideation Phase Last Updated: 2026-07-25