feat: Add Hemingway Bridge semantic anchor (#92)

Agent-Logs-Url: https://github.com/LLM-Coding/Semantic-Anchors/sessions/722d6689-1d8f-44b8-93d2-b8340a17796f

Co-authored-by: rdmueller <1856308+rdmueller@users.noreply.github.com>

Author: Copilot

docs/anchors/hemingway-bridge.adoc

@@ -0,0 +1,48 @@
+= Hemingway Bridge
+:categories: knowledge-management
+:roles: software-developer, technical-writer, educator, consultant
+:related: gtd, para-method
+:proponents: Ernest Hemingway
+:tags: productivity, session-management, creative-flow, re-entry, momentum, writer-block
+:tier: 3
+
+[%collapsible]
+====
+Full Name:: Hemingway Bridge
+
+Also known as:: Stop Mid-Sentence Technique, Re-entry Point Strategy
+
+[discrete]
+== *Core Concepts*:
+
+Stop Before You Are Finished:: End each work session deliberately before reaching a natural stopping point, while you still know exactly what comes next — preserving momentum for the next session
+
+Re-entry Point:: Leave a clear "bridge" to the next session: an unfinished sentence, a comment, a TODO note, or a short summary of the next steps so you can re-engage immediately without warm-up
+
+Creative Energy Management:: Avoid depleting all creative or cognitive energy in one session; stopping when energy is still high makes it easier to start again
+
+Reduce Blank-Page Anxiety:: By never fully stopping, you eliminate the paralysing "blank page" moment at the start of the next session
+
+Momentum Preservation:: The psychological state of "knowing what comes next" is transferred across time boundaries, keeping flow intact across interruptions
+
+Session Notes:: A brief note written at the end of a session ("next: implement X, blocked by Y") acts as an explicit Hemingway Bridge — a ready-made launchpad
+
+Key Proponent:: Ernest Hemingway (interviewed in George Plimpton (ed.), "The Paris Review Interviews"; practical elaboration by Steven Pressfield and others in the context of creative work)
+
+[discrete]
+== *When to Use*:
+
+* Ending a coding, writing, or design session mid-task to ensure smooth re-entry next time
+* Managing long-horizon creative or analytical projects across multiple sessions
+* Combating procrastination and "blank page" paralysis at the start of work
+* Pair programming or team handovers — leaving an explicit next-action note in comments or a ticket
+* Daily work planning: close the day by writing tomorrow's first action
+* Any knowledge work where cognitive warm-up cost is high
+
+[discrete]
+== *Related Anchors*:
+
+* <<gtd,GTD — Getting Things Done>>
+* <<para-method,P.A.R.A. Method>>
+* <<todotxt-flavoured-markdown,todo.txt-flavoured Markdown>>
+====

docs/anchors/hemingway-bridge.de.adoc

@@ -0,0 +1,45 @@
+= Hemingway Bridge
+:categories: knowledge-management
+:roles: software-developer, technical-writer, educator, consultant
+:proponents: Ernest Hemingway
+
+[%collapsible]
+====
+Vollständiger Name:: Hemingway Bridge
+
+Auch bekannt als:: Mitten-im-Satz-Stopp-Technik, Wiedereinstiegspunkt-Strategie
+
+[discrete]
+== *Kernkonzepte*:
+
+Vor dem Abschluss aufhören:: Beende jede Arbeitssession bewusst, bevor du einen natürlichen Haltepunkt erreichst — solange du noch genau weißt, was als Nächstes kommt. So bleibt der Schwung für die nächste Session erhalten.
+
+Wiedereinstiegspunkt:: Hinterlasse eine klare „Brücke" zur nächsten Session: ein unvollendeter Satz, ein Kommentar, eine TODO-Notiz oder eine kurze Zusammenfassung der nächsten Schritte, damit du sofort wieder einsteigen kannst.
+
+Management kreativer Energie:: Vermeide es, alle kreative oder kognitive Energie in einer einzigen Session zu verbrauchen; wenn du aufhörst, während die Energie noch hoch ist, fällt der Neustart leichter.
+
+Leere-Seite-Angst reduzieren:: Da du nie vollständig aufhörst, eliminierst du den lähmenden „leere-Seite"-Moment zu Beginn der nächsten Session.
+
+Momentum erhalten:: Der psychologische Zustand des „Wissens, was als Nächstes kommt" wird über Zeitgrenzen hinweg übertragen und hält den Flow trotz Unterbrechungen aufrecht.
+
+Sessionnotizen:: Eine kurze Notiz am Ende einer Session („als Nächstes: X implementieren, blockiert durch Y") ist eine explizite Hemingway Bridge — ein fertiger Startpunkt.
+
+Schlüsselvertreter:: Ernest Hemingway (Interview in George Plimpton (Hrsg.), „The Paris Review Interviews"; praktische Ausführung von Steven Pressfield u. a. im Kontext kreativer Arbeit)
+
+[discrete]
+== *Wann zu verwenden*:
+
+* Eine Programmier-, Schreib- oder Designsession mitten in einer Aufgabe beenden, um einen reibungslosen Wiedereinstieg sicherzustellen
+* Langfristige kreative oder analytische Projekte über mehrere Sessions hinweg managen
+* Prokrastination und „leere-Seite"-Lähmung zu Beginn der Arbeit bekämpfen
+* Pair Programming oder Team-Übergaben — einen expliziten Nächste-Aktion-Hinweis in Kommentaren oder einem Ticket hinterlassen
+* Tagesplanung: Den Tag damit abschließen, die erste Aufgabe des nächsten Tages zu notieren
+* Jede Wissensarbeit, bei der der kognitive Aufwärmaufwand hoch ist
+
+[discrete]
+== *Verwandte Anker*:
+
+* <<gtd,GTD — Getting Things Done>>
+* <<para-method,P.A.R.A. Method>>
+* <<todotxt-flavoured-markdown,todo.txt-flavoured Markdown>>
+====

skill/semantic-anchor-translator/references/catalog.md

@@ -351,6 +351,11 @@ Source: https://github.com/LLM-Coding/Semantic-Anchors
 ### todo.txt-flavoured Markdown
 - **Core:** GitHub task lists + todo.txt priorities/contexts/projects
 
+### Hemingway Bridge
+- **Also known as:** Stop Mid-Sentence Technique, Re-entry Point Strategy
+- **Proponents:** Ernest Hemingway
+- **Core:** End each work session before a natural stopping point while you still know what comes next; leave an explicit re-entry note (unfinished sentence, comment, TODO) to eliminate "blank page" paralysis, preserve momentum, and manage creative energy across sessions
+
 ## Statistical Methods
 
 ### SPC (Statistical Process Control)

website/public/data/anchors.json

@@ -1468,6 +1468,36 @@
     "filePath": "docs/anchors/gutes-deutsch-wolf-schneider.adoc",
     "tier": 3
   },
+  {
+    "id": "hemingway-bridge",
+    "title": "Hemingway Bridge",
+    "categories": [
+      "knowledge-management"
+    ],
+    "roles": [
+      "software-developer",
+      "technical-writer",
+      "educator",
+      "consultant"
+    ],
+    "related": [
+      "gtd",
+      "para-method"
+    ],
+    "proponents": [
+      "Ernest Hemingway"
+    ],
+    "tags": [
+      "productivity",
+      "session-management",
+      "creative-flow",
+      "re-entry",
+      "momentum",
+      "writer-block"
+    ],
+    "filePath": "docs/anchors/hemingway-bridge.adoc",
+    "tier": 3
+  },
   {
     "id": "hexagonal-architecture",
     "title": "Hexagonal Architecture (Ports & Adapters)",

website/public/data/categories.json

@@ -89,6 +89,7 @@
     "name": "Knowledge Management",
     "anchors": [
       "gtd",
+      "hemingway-bridge",
       "para-method",
       "todotxt-flavoured-markdown"
     ]

website/public/data/metadata.json

@@ -1,15 +1,15 @@
 {
-  "generatedAt": "2026-03-27T10:14:08.551Z",
+  "generatedAt": "2026-03-29T15:12:45.196Z",
   "version": "1.0.0",
   "counts": {
-    "anchors": 112,
+    "anchors": 113,
     "categories": 13,
     "roles": 12
   },
   "statistics": {
-    "averageRolesPerAnchor": "3.14",
+    "averageRolesPerAnchor": "3.15",
     "averageCategoriesPerAnchor": "1.01",
-    "anchorsWithTags": 72,
-    "anchorsWithRelated": 43
+    "anchorsWithTags": 73,
+    "anchorsWithRelated": 44
   }
 }

website/public/data/roles.json

@@ -39,7 +39,9 @@
       "devils-advocate",
       "feynman-technique",
       "gom",
+      "grasp",
       "gutes-deutsch-wolf-schneider",
+      "hemingway-bridge",
       "iec-61508-sil-levels",
       "impact-mapping",
       "kiss-principle",
@@ -109,10 +111,14 @@
       "diataxis-framework",
       "feynman-technique",
       "gof-design-patterns",
+      "grasp",
+      "gtd",
       "gutes-deutsch-wolf-schneider",
+      "hemingway-bridge",
       "kiss-principle",
       "mental-model-according-to-naur",
       "myers-briggs-type-indicator",
+      "para-method",
       "pert",
       "plain-english-strunk-white",
       "socratic-method",
@@ -131,6 +137,7 @@
       "cynefin-framework",
       "definition-of-done",
       "gherkin",
+      "gtd",
       "impact-mapping",
       "invest",
       "iso-25010",
@@ -221,6 +228,7 @@
       "gof-template-method-pattern",
       "gof-visitor-pattern",
       "gom",
+      "grasp",
       "hexagonal-architecture",
       "iec-61508-sil-levels",
       "iso-25010",
@@ -296,6 +304,9 @@
       "gof-strategy-pattern",
       "gof-template-method-pattern",
       "gof-visitor-pattern",
+      "grasp",
+      "gtd",
+      "hemingway-bridge",
       "hexagonal-architecture",
       "iec-61508-sil-levels",
       "invest",
@@ -309,6 +320,7 @@
       "morphological-box",
       "mutation-testing",
       "owasp-top-10",
+      "para-method",
       "plain-english-strunk-white",
       "prd",
       "property-based-testing",
@@ -357,6 +369,7 @@
       "fowler-patterns",
       "github-flow",
       "gom",
+      "gtd",
       "impact-mapping",
       "invest",
       "iso-25010",
@@ -367,6 +380,7 @@
       "moscow",
       "myers-briggs-type-indicator",
       "owasp-top-10",
+      "para-method",
       "pert",
       "prd",
       "problem-space-nvc",
@@ -394,7 +408,9 @@
       "docs-as-code",
       "ears-requirements",
       "gutes-deutsch-wolf-schneider",
+      "hemingway-bridge",
       "lasr",
+      "para-method",
       "plain-english-strunk-white",
       "pyramid-principle",
       "todotxt-flavoured-markdown"