@cr8rcho/alkahest 0.1.74 → 0.1.75

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cr8rcho/alkahest",
-  "version": "0.1.74",
+  "version": "0.1.75",
   "publishConfig": {
     "access": "public"
   },

package/presets/as-built/scaffold/docs/decisions/README.md

@@ -10,3 +10,15 @@ Quick rules:
 - Append-only: a changed decision gets a NEW ADR with `Supersedes:`; the old one keeps its
   body and gets `Status: Superseded by …`.
 - Start the practice with **ADR-001 — architecture snapshot** of the current code.
+
+## Tag vocabulary
+
+Every ADR opens with `tags:` frontmatter, and **this table is the vocabulary** — pick from
+it; extend it deliberately (add the row in the same commit as the ADR that needs it). On the
+hosted `adr` note map each tag becomes a hub node, so the vocabulary's shape IS the map's
+shape: one **surface** tag per ADR (the product/code area it touches) plus at most two
+**arc** tags (a storyline several ADRs share), and keep each tag attached to roughly 3–12
+ADRs. The first documentation pass seeds the surface rows from the codebase's actual areas.
+
+| Tag | Kind | Meaning |
+|---|---|---|

package/presets/as-built/skills/adr.md

@@ -38,6 +38,13 @@ one **surface** tag (the area of the product it touches) plus at most two **arc*
 node — keep every tag attached to roughly 3–12 ADRs so the map stays legible, and prefer
 reusing an existing tag over inventing a new one.
 
+**The vocabulary lives in `docs/decisions/README.md`'s tag table, and the repo owns it.**
+On the bootstrap pass, seed it: derive 3–7 surface tags from the codebase's *actual* areas
+(the folders/verticals you just documented), record them in the table, and tag ADR-001 from
+that set. Afterwards, every ADR picks from the table; a genuinely new tag means adding its
+row in the same commit. Arc tags are not invented up front — they emerge when several ADRs
+turn out to share a storyline.
+
 ## Template
 
 ```markdown