@nurix/etna 0.20.8 → 0.20.9

package/data/harness-index.json

@@ -1,5 +1,5 @@
 {
-    "fingerprint": "bcf04d8d525c",
+    "fingerprint": "7d1e7785bd0c",
     "harnesses": {
         "code": {
             "plugin": "code",

package/data/harnesses/code/harness.json

@@ -1,7 +1,7 @@
 {
   "harness": "code",
   "name": "code",
-  "version": "3.14.6",
+  "version": "3.14.7",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
@@ -25,5 +25,5 @@
     }
   ],
   "docsRoot": "docs",
-  "digest": "ec29198342ff"
+  "digest": "80ccc743454e"
 }

package/data/harnesses/code/skills/brainstorm/references/doctrine.md

@@ -118,3 +118,30 @@ Measured on live sessions; each is the rule, distilled.
 - **When a ledger entry's `Why` contains "already", verify it before the manifest.** A commitment
   that declines to build something because it already exists rests on a fact, not a judgment, and
   the stop gate is the last place that fact is checkable — after the folder moves it is not.
+- **Verify a doctrine claim against disk before building an argument on it.** Truth docs outrun
+  package rebuilds: a guardrail can assert a guard path that exists nowhere, inside a suppression
+  wrapper naming packages already deleted. When a session's centre is a recorded prohibition, `ls`
+  the guard path, read the owning package's config, and confirm the package is still in the tree.
+- **Read the decision records before framing a session around a pillar contradiction.** An AD
+  accepted last week can already contradict the pillars; a session convened to *decide* a reversal
+  may be *ratifying* one that shipped — a materially different conversation.
+- **Give the opening map at least one aspect organised by seam.** A map organised by system layer
+  owns none of the questions that land on the boundary between two planes or two phases, which is
+  where the real design questions sit.
+- **Ledger only the user's half of a re-derivation turn.** When the user states a segregation and
+  the facilitator re-derives a whole architecture from it in the same entry, only the first half is
+  ledgerable; a re-derivation that re-reads an existing commitment into a new shape is a fork with a
+  named amendment, never an edit.
+- **Check the ledger prefix against the product's vocabulary.** `D#` reads two ways in a product
+  whose state lives in a database called D1; add a disambiguation line to the ledger header and
+  write the colliding term in full inside entries.
+- **The repo's rule files are a first-class blindspot source.** They carry platform facts a design
+  can contradict unnoticed — a registry answering `404`, not `401`, to a restricted read turned a
+  celebrated "containers hold no credentials" property into an open question. Read the rules that
+  touch the session's substrate against the new commitments, not only the basis.
+- **Absence in this repo is not absence.** Evidence for a premise often lives in a sibling
+  repository; grep finding nothing proves only that this repo does not own the fact. Check the
+  owning repo before filing a fork as unevidenced, and when the fact is confirmed there, the
+  harvested record cites the external doc rather than restating it. A doc saying "this surface
+  reports, it does not enforce" does not contradict "the platform enforces" — different layers,
+  both true, neither edited.

package/data/harnesses/code/skills/brainstorm/references/harvest.md

@@ -118,3 +118,31 @@ Measured on live harvests; each is the rule, distilled.
   and nothing else** — a claim stated in nine places and fixed in three leaves the doc worse; a
   one-paragraph note saying what moved and what did not keeps the amendment legible to the doc's
   author.
+- **A suppression marker is a dated assertion about code, and it decays faster than the docs
+  around it.** A harvest that deletes doctrine rows corrects their wrappers first — a false wrapper
+  is a correction row in the manifest, never collateral of a delete. A phantom guard propagates by
+  citation: grep the guard *path*, not its name, and count live docs separately from frozen ones,
+  which record what was believed and are not edited.
+- **Retiring a guardrail row edits three artifacts.** The row is cited by ID from feature docs and
+  frozen plans, wrapped in a marker asserting where its code lives, and restated in the
+  out-of-scope register at the foot of the same file: keep the ID and mark the row retired with a
+  pointer, correct the wrapper, and replace the register bullet with a pointer — otherwise the file
+  contradicts itself twenty lines apart.
+- **Size the decision records to the repo's AD doctrine before writing them.** One decision per
+  subject argued feels natural and produces micro-ADs where the rule is one overarching AD per
+  architectural subject; the test at manifest time is whether a reader would ever need one record
+  without the others. The safe shape is one AD per plane with a section per settled subject — each
+  keeping its Decision, Why and Declined table — and a separate AD only for a genuinely different
+  subject. Link with section anchors where a bare pointer loses precision, and verify anchors by
+  hand: the link checker strips them before resolving.
+- **At manifest time, read every existing AD's Decision and Open Questions against the new
+  commitments.** A harvest routes only through the docs its commitments name, and grep finds
+  nothing because the ledger never names the others; report the unimpacted verdicts with their
+  evidence too.
+- **A manifest row names one site; the file you open holds more.** Fix the same-doctrine sites
+  inside a file the manifest already opens, but never wander into an unnamed file — that becomes a
+  backlog row, because a canonical doc is not rewritten outside an approved scope. Say which you did,
+  per row, in the application record.
+- **The per-file lint hook reads intermediate states.** It appends queue rows from mid-edit files;
+  run the linter over the whole edited set before declaring the apply done, and leave the stale
+  rows for the facilitator rather than draining them.

package/data/harnesses/delivery/harness.json

@@ -1,7 +1,7 @@
 {
   "harness": "delivery",
   "name": "delivery",
-  "version": "0.2.27",
+  "version": "0.2.28",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
@@ -10,5 +10,5 @@
   "seeds": [],
   "tools": [],
   "docsRoot": "docs",
-  "digest": "b36abb3f2f60"
+  "digest": "432c8344e384"
 }

package/data/harnesses/delivery/skills/brainstorm/references/doctrine.md

@@ -118,3 +118,30 @@ Measured on live sessions; each is the rule, distilled.
 - **When a ledger entry's `Why` contains "already", verify it before the manifest.** A commitment
   that declines to build something because it already exists rests on a fact, not a judgment, and
   the stop gate is the last place that fact is checkable — after the folder moves it is not.
+- **Verify a doctrine claim against disk before building an argument on it.** Truth docs outrun
+  package rebuilds: a guardrail can assert a guard path that exists nowhere, inside a suppression
+  wrapper naming packages already deleted. When a session's centre is a recorded prohibition, `ls`
+  the guard path, read the owning package's config, and confirm the package is still in the tree.
+- **Read the decision records before framing a session around a pillar contradiction.** An AD
+  accepted last week can already contradict the pillars; a session convened to *decide* a reversal
+  may be *ratifying* one that shipped — a materially different conversation.
+- **Give the opening map at least one aspect organised by seam.** A map organised by system layer
+  owns none of the questions that land on the boundary between two planes or two phases, which is
+  where the real design questions sit.
+- **Ledger only the user's half of a re-derivation turn.** When the user states a segregation and
+  the facilitator re-derives a whole architecture from it in the same entry, only the first half is
+  ledgerable; a re-derivation that re-reads an existing commitment into a new shape is a fork with a
+  named amendment, never an edit.
+- **Check the ledger prefix against the product's vocabulary.** `D#` reads two ways in a product
+  whose state lives in a database called D1; add a disambiguation line to the ledger header and
+  write the colliding term in full inside entries.
+- **The repo's rule files are a first-class blindspot source.** They carry platform facts a design
+  can contradict unnoticed — a registry answering `404`, not `401`, to a restricted read turned a
+  celebrated "containers hold no credentials" property into an open question. Read the rules that
+  touch the session's substrate against the new commitments, not only the basis.
+- **Absence in this repo is not absence.** Evidence for a premise often lives in a sibling
+  repository; grep finding nothing proves only that this repo does not own the fact. Check the
+  owning repo before filing a fork as unevidenced, and when the fact is confirmed there, the
+  harvested record cites the external doc rather than restating it. A doc saying "this surface
+  reports, it does not enforce" does not contradict "the platform enforces" — different layers,
+  both true, neither edited.

package/data/harnesses/delivery/skills/brainstorm/references/harvest.md

@@ -118,3 +118,31 @@ Measured on live harvests; each is the rule, distilled.
   and nothing else** — a claim stated in nine places and fixed in three leaves the doc worse; a
   one-paragraph note saying what moved and what did not keeps the amendment legible to the doc's
   author.
+- **A suppression marker is a dated assertion about code, and it decays faster than the docs
+  around it.** A harvest that deletes doctrine rows corrects their wrappers first — a false wrapper
+  is a correction row in the manifest, never collateral of a delete. A phantom guard propagates by
+  citation: grep the guard *path*, not its name, and count live docs separately from frozen ones,
+  which record what was believed and are not edited.
+- **Retiring a guardrail row edits three artifacts.** The row is cited by ID from feature docs and
+  frozen plans, wrapped in a marker asserting where its code lives, and restated in the
+  out-of-scope register at the foot of the same file: keep the ID and mark the row retired with a
+  pointer, correct the wrapper, and replace the register bullet with a pointer — otherwise the file
+  contradicts itself twenty lines apart.
+- **Size the decision records to the repo's AD doctrine before writing them.** One decision per
+  subject argued feels natural and produces micro-ADs where the rule is one overarching AD per
+  architectural subject; the test at manifest time is whether a reader would ever need one record
+  without the others. The safe shape is one AD per plane with a section per settled subject — each
+  keeping its Decision, Why and Declined table — and a separate AD only for a genuinely different
+  subject. Link with section anchors where a bare pointer loses precision, and verify anchors by
+  hand: the link checker strips them before resolving.
+- **At manifest time, read every existing AD's Decision and Open Questions against the new
+  commitments.** A harvest routes only through the docs its commitments name, and grep finds
+  nothing because the ledger never names the others; report the unimpacted verdicts with their
+  evidence too.
+- **A manifest row names one site; the file you open holds more.** Fix the same-doctrine sites
+  inside a file the manifest already opens, but never wander into an unnamed file — that becomes a
+  backlog row, because a canonical doc is not rewritten outside an approved scope. Say which you did,
+  per row, in the application record.
+- **The per-file lint hook reads intermediate states.** It appends queue rows from mid-edit files;
+  run the linter over the whole edited set before declaring the apply done, and leave the stale
+  rows for the facilitator rather than draining them.

package/data/harnesses/etna/harness.json

@@ -1,7 +1,7 @@
 {
   "harness": "etna",
   "name": "etna",
-  "version": "1.5.16",
+  "version": "1.5.17",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
@@ -10,5 +10,5 @@
   "seeds": [],
   "tools": [],
   "docsRoot": "docs",
-  "digest": "f836486a6ca4"
+  "digest": "24530584ce9d"
 }

package/data/harnesses/etna/skills/brainstorm/references/doctrine.md

@@ -118,3 +118,30 @@ Measured on live sessions; each is the rule, distilled.
 - **When a ledger entry's `Why` contains "already", verify it before the manifest.** A commitment
   that declines to build something because it already exists rests on a fact, not a judgment, and
   the stop gate is the last place that fact is checkable — after the folder moves it is not.
+- **Verify a doctrine claim against disk before building an argument on it.** Truth docs outrun
+  package rebuilds: a guardrail can assert a guard path that exists nowhere, inside a suppression
+  wrapper naming packages already deleted. When a session's centre is a recorded prohibition, `ls`
+  the guard path, read the owning package's config, and confirm the package is still in the tree.
+- **Read the decision records before framing a session around a pillar contradiction.** An AD
+  accepted last week can already contradict the pillars; a session convened to *decide* a reversal
+  may be *ratifying* one that shipped — a materially different conversation.
+- **Give the opening map at least one aspect organised by seam.** A map organised by system layer
+  owns none of the questions that land on the boundary between two planes or two phases, which is
+  where the real design questions sit.
+- **Ledger only the user's half of a re-derivation turn.** When the user states a segregation and
+  the facilitator re-derives a whole architecture from it in the same entry, only the first half is
+  ledgerable; a re-derivation that re-reads an existing commitment into a new shape is a fork with a
+  named amendment, never an edit.
+- **Check the ledger prefix against the product's vocabulary.** `D#` reads two ways in a product
+  whose state lives in a database called D1; add a disambiguation line to the ledger header and
+  write the colliding term in full inside entries.
+- **The repo's rule files are a first-class blindspot source.** They carry platform facts a design
+  can contradict unnoticed — a registry answering `404`, not `401`, to a restricted read turned a
+  celebrated "containers hold no credentials" property into an open question. Read the rules that
+  touch the session's substrate against the new commitments, not only the basis.
+- **Absence in this repo is not absence.** Evidence for a premise often lives in a sibling
+  repository; grep finding nothing proves only that this repo does not own the fact. Check the
+  owning repo before filing a fork as unevidenced, and when the fact is confirmed there, the
+  harvested record cites the external doc rather than restating it. A doc saying "this surface
+  reports, it does not enforce" does not contradict "the platform enforces" — different layers,
+  both true, neither edited.

package/data/harnesses/etna/skills/brainstorm/references/harvest.md

@@ -118,3 +118,31 @@ Measured on live harvests; each is the rule, distilled.
   and nothing else** — a claim stated in nine places and fixed in three leaves the doc worse; a
   one-paragraph note saying what moved and what did not keeps the amendment legible to the doc's
   author.
+- **A suppression marker is a dated assertion about code, and it decays faster than the docs
+  around it.** A harvest that deletes doctrine rows corrects their wrappers first — a false wrapper
+  is a correction row in the manifest, never collateral of a delete. A phantom guard propagates by
+  citation: grep the guard *path*, not its name, and count live docs separately from frozen ones,
+  which record what was believed and are not edited.
+- **Retiring a guardrail row edits three artifacts.** The row is cited by ID from feature docs and
+  frozen plans, wrapped in a marker asserting where its code lives, and restated in the
+  out-of-scope register at the foot of the same file: keep the ID and mark the row retired with a
+  pointer, correct the wrapper, and replace the register bullet with a pointer — otherwise the file
+  contradicts itself twenty lines apart.
+- **Size the decision records to the repo's AD doctrine before writing them.** One decision per
+  subject argued feels natural and produces micro-ADs where the rule is one overarching AD per
+  architectural subject; the test at manifest time is whether a reader would ever need one record
+  without the others. The safe shape is one AD per plane with a section per settled subject — each
+  keeping its Decision, Why and Declined table — and a separate AD only for a genuinely different
+  subject. Link with section anchors where a bare pointer loses precision, and verify anchors by
+  hand: the link checker strips them before resolving.
+- **At manifest time, read every existing AD's Decision and Open Questions against the new
+  commitments.** A harvest routes only through the docs its commitments name, and grep finds
+  nothing because the ledger never names the others; report the unimpacted verdicts with their
+  evidence too.
+- **A manifest row names one site; the file you open holds more.** Fix the same-doctrine sites
+  inside a file the manifest already opens, but never wander into an unnamed file — that becomes a
+  backlog row, because a canonical doc is not rewritten outside an approved scope. Say which you did,
+  per row, in the application record.
+- **The per-file lint hook reads intermediate states.** It appends queue rows from mid-edit files;
+  run the linter over the whole edited set before declaring the apply done, and leave the stale
+  rows for the facilitator rather than draining them.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nurix/etna",
-  "version": "0.20.8",
+  "version": "0.20.9",
   "description": "Bootstrap a project with a Nurix harness — copies the harness's CLAUDE.md, skills, agents, rules, and hooks directly into the project from a bundled payload (no marketplace fetch, no network).",
   "type": "module",
   "bin": {
@@ -42,5 +42,5 @@
     "agent",
     "plugin"
   ],
-  "etnaFingerprint": "bcf04d8d525c"
+  "etnaFingerprint": "7d1e7785bd0c"
 }