The Harbour Archive

A founding sprint of 435 commits in one month. The app is a read-only tree of Linear tickets — but look closely at the first hundred tickets and the future is already aboard: 28 of 76 titles mention "prompt". This was never just a viewer.

1. 4 Jan

   First light

   The repository opens as a "minimal, CLI-aesthetic web app" — OAuth, a collapsible tree, status glyphs ✓ ◐ ○. The commit is co-authored by Claude Opus 4.5. From minute one, the machine is in the room.

   Specimen · the founding commit

   Initial commit: Linear Roadmap Viewer — A minimal, CLI-aesthetic web app that displays Linear projects and issues as a collapsible tree… Features: OAuth login; hierarchical tree view; status indicators; dark theme, mobile-friendly.

   Harboura82b8758
2. 5 Jan

   The dark-theme betrayal

   The founding commit boasts "dark theme". It survives one night — the next morning's commit switches to light, which remains the default for the rest of history. Dark returns only in late June, humbled, as an opt-in toggle.

   Harbourdabd2a90 → 88c278ee
3. 7 Jan

   The oldest surviving ticket

   LIN-1 through LIN-4 are lost to the archive's trash. The record begins at LIN-5 — "Pwa", forty-nine characters, still in the Backlog seven months later. Every museum has a founding object it never got around to.

   Specimen · LIN-5, complete text

   Pwa — Create manifest so can be an app, link in footer.

   workspaceLIN-5
4. 11 Jan

   The viewer starts generating work

   lib/prompt-templates.js is born. A tool for looking at tasks becomes a tool for writing instructions about tasks — the hinge on which everything later turns.

   Harbouraa65267b
5. 16–17 Jan

   The AI moves in; a rival visits

   OpenRouter OAuth and AI-generated recommendations land in a two-day sprint. The same week, GitHub Copilot makes exactly two commits — and never returns.

   Harboure502e67a · bbfa3dff · 3fa1a53a
6. 19 Jan

   Eighty commits in one day

   The single biggest day in either repository's history: settings, model selection, workflow labels, preference storage, an XSS fix — a feature per commit. The founding energy peaks here and will not be matched until the machines take over the typing in June.

   Harbourgit log 2026-01-19

Ticket creation slows to 0.6 a day. But the quiet months lay every keel the summer will float: the dispatch queue, the agent API, the executor, the autopilot's ancestor — and, in an April branch name, the word that will rename the whole project.

1. 20 Jan

   The dispatch queue — then silence

   "Add dispatch queue feature for prompts" (LIN-66) lands: a place to queue work for external agents that do not yet exist. It is the last commit before seventeen silent days — the project's near-death. February produces 47 commits total.

   Harbourb1681f5d
2. 11 Feb

   A vision filed four months early

   LIN-177 and LIN-178 — the provider abstraction and a GitHub backend — are written twenty seconds apart, then sit untouched until June. The longest gestation in the archive: the idea of being more than a Linear viewer waited for the workforce that could build it.

   workspaceLIN-177 · LIN-178
3. 26 Feb

   The dispatcher is born in one morning

   09:07 to 12:38 — four commits, 5,267 lines, and a maximalist design: three execution substrates (iTerm, headless SDK, web remote-control), a Slack bot, and a Chrome extension in the experiments drawer. Co-authored by Claude Opus 4.6. Then: 97 days of total silence.

   Specimen · the birth commit

   Initial commit: task dispatcher for Claude Code — Polls LinearViewer dispatch API and executes tasks via Claude Code across multiple workspaces… two-phase summarise-then-execute flow; Slack bot integration; comprehensive test suite.

   dispatcher88ba61c
4. 6 Mar

   Agents become users

   The workspace API proxy lands in a single 2,858-line commit (LIN-193): token auth, scopes, audit logging. From here on, the app's most important users are not people.

   Harbour33c94da6
5. 13 Mar

   Foreman Mode — the autopilot's ancestor

   An "autonomous task runner" appears (LIN-209), with the agent-status log that still underlies everything. Foreman will run the yard for three months before its descendant retires it — in a June commit the curator can only describe as the autopilot eating its ancestor.

   Harbour3ba9e69b · a0ad7310
6. 12 Apr

   "Harbour" enters the lexicon — as the child

   The word first appears in branch claude/harbour-os-lin-243, naming John's in-browser workstation, Harbour OS. The product itself is still "LinearViewer". The child was named first; ten weeks later, the parent takes the family name.

   Harbour13668fc2

Before the machinery, the ideas. In one extraordinary week of late May the project writes its philosophy — drift, grounding, the north star — and everything June builds is an implementation of what May wrote.

1. 28–29 May

   The drift trilogy

   Three documents in two days name the enemy. A real field episode — four tickets each patching the last until a rare 3% error became a 100% hang — is diagnosed as "greedy local correctness accumulating into global structural drift." The prescribed fix-shape organizes the whole later system: "Install a normative reference one altitude up that the local optimizer is forced to score against." One thread is flagged open: epistemic drift — whether to believe the record of what was done. Closing it takes the rest of the project.

   doctrinedocs/drift-at-every-altitude.md · recommender-failure-patterns.md
2. 29 May

   The north star

   One sentence, fixed until a human deliberately revises it — with a guard against the analyzer rewriting it to match observed behaviour, a failure the doc names drift-as-rationalization.

   Specimen · docs/north-star.md

   "Harbour exists to keep human intent in command of AI-accelerated execution."

   doctrinenorth-star.md · e1f3b13a
3. 29 May

   Grounding, staleness, and the distrust of tickets

   "A verdict must cite the actual line or it is speculation." The staleness check — re-ground every ticket against the code at HEAD before trusting it — enters both prompt paths on day one, and will later be applied, with some irony, to the project's own aging backlog.

   doctrine1caab047 · e1f3b13a

The dispatcher wakes after 97 days, the autopilot switches on, and ticket creation jumps to eighteen a day. Three weeks in which nearly every load-bearing idea — honest completion, the Collective, the Observation deck — arrives at flank speed.

1. 4 Jun

   The reawakening

   The dispatcher's first commit since February. Every resumption commit is about one thing: making its reports back to the mothership trustworthy — the Stop hook injected cleanly, feedback carrying evidence, launches watched by a watchdog. It was revived to be the autopilot's arms.

   dispatcher3cb9a47
2. 5–6 Jun

   Autopilot: the thinking before the build

   A design doc written "so that when the build decisions come, there is something to score them against." Its reframing of the human's role becomes the project's most-quoted line — and its Invariant 2, external evidence over self-report, becomes the law every later mechanism enforces. Ten live runs follow within a day.

   Specimen · docs/autopilot.md

   "…the human stops being the loop's clock … and becomes its navigator."

   doctrine395598a5 · autopilot-experiment.md
3. 7–8 Jun

   The premature-“done” crisis

   The Stop hook was declaring victory on any turn-end — a genuine completion arrived 13.8 minutes after its own [done]. The research measures the trap precisely: 46% of background shells (39 of 84) never emit a completion notification at all. The fix is defense-in-depth, and the bug class takes seven weeks of escalating protocol design to fully retire.

   dispatcher53d15b6 · premature-done-research.md
4. 7 Jun

   The manual forks — and the disposition wins

   At 14:18 the first autopilot operating manual lands. At 15:00 a rival version appears, subtitled "disposition, not procedure". At 15:33 the main manual is rewritten in the rival's voice. Seventy-five minutes, one philosophical fork, resolved for good: the autopilot is governed by judgment shaped through stories, not by checklists. "You have exactly two acts: what you choose, and what you accept."

   doctrine6ac765e7 · cf921e0d · 37e6b197
5. 7–10 Jun

   The February vision comes due

   The provider abstraction — filed in February as LIN-177 — finally builds: canonical state model, interface, and a writable local provider pulled ahead of GitHub to prove the write path, done in a single day. The app stops being a Linear viewer in its bones.

   Harbour5c6c2201 · 42b6724a · LIN-356
6. 13 Jun

   The Collective becomes a product overnight

   The day after the chat-room session (see the central exhibit below), LIN-450 industrializes it: "I've found interesting things happen when agents are in a chat room together." Hand-pasted prompts become a feature with routes, personas, and a channel proxy — in one day.

   Harbour2b7ad939 · LIN-450
7. 16 Jun

   The structural big bang

   In one day the dispatcher's god-module splits into phases.js · queue.js · executors.js, and follow-ups arrive — the ability to resume a finished session and continue the conversation. The same day, across the water, Harbour retires Foreman. The old order ends on both shores at once.

   dispatcher152df13 · 23c776a · 048f95f
8. 21 Jun

   The honest-completion protocol

   The premature-done saga reaches doctrine: completion may only be asserted by an explicit sentinel, never inferred from a session going quiet. The commit message is the epitaph of an entire bug class.

   Specimen · commit 7c83c84 (LIN-549)

   honest completion protocol — assert [done], never infer it

   dispatcher7c83c84
9. 22 Jun

   The Observation deck

   "A top-level page where a user sits back and watches autopilot work." Specified without a mockup and shipped first-class the same day. The harbour master gets a window.

   Harbourfdd80e13 · LIN-595

Peak swarm: forty-two tickets a day, faster than a human could read them. The project takes its true name, suffers its defining crisis, and answers with its constitution — a ledger of what green CI cannot prove.

1. 25 Jun

   Rebrand day

   "LIN-646: Rebrand to Harbour." The same day carries six autonomous periodical reviews (security, code quality, test gaps, dependencies, comprehension debt, design) — plus a rescue commit recovering four reports that failed to persist. The project renames itself while marking its own homework, and needing help with the filing.

   Harbour51a90689 · f08afa61
2. 26 Jun

   The LIN-735 crisis — the human voice at full volume

   The archive's most consequential failure: work that was grounded, tested, reviewed, approved — and shipped broken anyway. The exasperated ticket below triggered the retro that produced the close-out ledger, the project's constitutional answer to epistemic drift.

   Specimen · LIN-735, in the owner's voice

   "Three 'fixes' landed, and are wrong or incomplete… I had a workspace which was github issues, I added Linear, it removed GitHub."

   workspaceLIN-735
3. 29 Jun

   The ledger of What CI Did Not Prove

   Review splits from close-out. Every review must now enumerate the claims green CI does not exercise; the irreversible acts — merge, Done — are gated on discharging that ledger with cited evidence or a named human acceptance. A missing ledger blocks; green CI alone discharges nothing. Epistemic drift, the open thread of May, finally has a lock on it.

   doctrineba6ec27e · LIN-550
4. 1 Jul

   The swarm learns to subtract

   The Pipeline view — a working, shipped feature — is deleted in three tidy beats: "a good experiment but has now been superseded." Proof the machine can renounce, not merely accrete.

   HarbourLIN-877
5. 2 Jul

   The identity purge

   Twenty-seven commits in one day delete the SDK substrate, the Slack bot, and the dash target — the maximalist birth design of February collapsed to the single hook substrate that the dispatcher's own documentation now calls "the one fact that explains everything." The confession is in the ticket: "we patched to fix issues as they came up. Now, it's time to simplify."

   dispatcher4ffe830 · LIN-900–912
6. 3 Jul

   The humbling session

   The second Collective convenes and gravely re-derives an elaborate safety architecture — concluding almost none of it exists. John corrects the room three times with the live system: "the engine runs." Coined that day: live-grounding is anti-monoculture — shared docs make the agents sound alike; their real running systems make them diverge, and the divergence is the point.

   workspacecollective-session-2026-07-03.md
7. 4–7 Jul

   Faces and papers

   A 55-commit day gives Harbour its bespoke landing page and gives every agent session a URL of its own. The opencode harness makes the execution engine pluggable. And single-use bootstrap tokens roll out across every handoff surface — a credential that is inert the instant it is exchanged, closing a confession the code had carried for a month: "a leaked prompt leaks full workspace write."

   Harbourdispatcherec97c8fb · a5c7714 · fd18afa6

The system watches itself burn fuel, prints its own newspaper, and writes a constitution limiting its own author. History ends mid-sentence — with research into where one system should end and the other begin.

1. 9 Jul

   The Ship's Biscuit

   An in-app newspaper reporting the project's own progress, edition by edition. Later gently edited: "Shorten and de-shout the Ship's Biscuit front page". Even the propaganda organ gets a style review.

   Harbour04df53b9 · 57ec778c
2. 12 Jul

   harbour.cat

   The dispatcher is pointed at the product's own domain. The same day fixes the "DONE self-kill race" — the dispatcher closing its own window mid-finalize. A system now sophisticated enough to trip over its own feet, and to notice.

   dispatcherceeb0f5 · c60e8b1
3. 17 Jul

   The credential broker — a design condemns its predecessor

   Eight days after shipping a token-vending MCP server, the project rebuilds it: the first design had leaked a live bearer token into the session transcript, a shape "indistinguishable to a fast classifier from a credential stealer." The replacement is a localhost broker; the agent never touches a credential at all. The ticket states the law:

   Specimen · LIN-1375

   "The credential must live in the transport, never in the model's context."

   dispatcher5d77839 · 3a48acb
4. 18–19 Jul

   Alarm philosophy from 1999; a fireplace to watch

   The escalation doctrine borrows EEMUA 191 — industrial alarm-management standards for chemical plants — for agent swarms: "that document solved our exact problem forty years early." A day later the Live Console ships: an ambient, breathing feed of the whole swarm. Its design brief may be the most honest sentence in the archive: "Not a cockpit to operate; a surface to enjoy."

   Harbour36fec556 · LIN-1436
5. 19 Jul

   The Charter

   Seven weeks after the north star, a constitution — written "while the project is tiny and there's no money to bias the author." Seven acts are reserved for humans alone: the irreversible, the financial, the licence, the release, the maintainer's own pay, and amendment of the charter itself. Reports may never say "all clear" — a report that claims no blind spots is itself a violation.

   Specimen · charter.md v0.2

   "Our trustworthiness is meant to come from transparency and pre-commitment, not from anyone's character."

   doctrinedocs/charter/charter.md
6. 20 Jul

   A test suite in a day

   Thirty-five commits — Phase A through Phase L — build a full-system hermetic suite: a real Harbour booted inside the dispatcher's tests, real dispatcher driven in-process, only the two LLM boundaries faked. Plus a mutation-testing gate that injects curated bugs to prove the suite would catch them. The swarm builds the un-authorable judge for itself.

   dispatcher495b4cf … 27e39b2 · feba6b6
7. 23–25 Jul

   Two late shocks

   LIN-1539: headless workers die whenever John's login session lapses — the swarm discovers it depends on whether one human is logged in. Then LIN-1580, the audit finding that lands like a confession: "no pull request in this repository has ever had an automated check" — six months of autonomous development in the dispatcher repo, merged on manually-cited test runs. CI lands the next day.

   workspaceLIN-1539 · LIN-1580
8. 27 Jul

   History ends mid-sentence

   The newest ticket, LIN-1674, is a four-thousand-character agent essay on salvaging truncated JSON, with a provenance chain three tickets deep. The dispatcher's final commits are research into where the Harbour/dispatcher control-plane split should sit. The boundary question — where does one system end and the other begin — is live as the record closes. Fitting, for a project whose whole subject is boundaries.

   workspaceLIN-1674 · b4d77bc