@antoneeo/kb-agentic-skill 1.26.1 → 1.31.0

package/skills/kb-agentic-skill/templates.md

@@ -35,7 +35,10 @@ a fidelity marker: `[source: <snapshot-file>#<anchor-or-line>]` for covered cont
 (doubling as the detail-lookup pointer into the book), or a literal
 `[not covered by source]` for gaps. Sections are CHOSEN from the repertoire below —
 only those the source actually supports; never force empty ones. A guide approaching
-the source's own length is a paraphrase, not a synthesis.
+the source's own length is a paraphrase, not a synthesis. **With a corpus**, a
+`source_kind: document` guide's book is its `corpus/given/` artifact instead of a
+snapshot: `distilled_from:` and the markers name it, and `source_hash` is its
+line-ending-normalized digest (`distillation.md` §1).
 
 ```markdown
 ---
@@ -555,7 +558,8 @@ columns: Standalone adds `reviewer`, a Hybrid row adds `instrument` and
 and `closure` (Standalone); `deep`, `light`, `code`, `guide`, `vision` (devPNT gates
 and the Vision blind check). `model` is a different question about the same review: `tier` says WHICH GATE ran,
 `model` says WHAT CAPABILITY ran it (`deep`, `light`, `economy`,
-`single (client exposes no choice)`, `below floor: <reason>` — the floor and its
+`single (client exposes no choice)`, `below floor: <reason>`, `none (not due)` on a
+NOT DUE row — the floor and its
 arbitration are `review.md` §The capability floor). The two columns share the words
 `deep`/`light` and mean different things by them, which is why they are read by
 header and never by position. The validator reads this column by its header name, so
@@ -580,6 +584,7 @@ round verifies them (`review.md` §Receiving) — and 3 is the ceiling, past whi
 residue goes to the user rather than into a fourth round. `verdict` carries the
 round-1 verdict and the final one when they differ (`FAIL → PASS`): collapsing a
 first-round FAIL into a bare `PASS` erases the evidence this log exists to keep.
+A restating delta ruled not due (`review.md` §When a review is due) is still a row: `tier` `closure`, `model` `none (not due)`, findings and rounds `0`, verdict `NOT DUE: <the kinds; the check that ran and its result>`; `benefit` counts it apart.
 Concurrent reviews: `init` writes a `.gitattributes` stanza giving this file
 `merge=union` — a **built-in** driver (no per-clone `git config`, unlike
 `merge=ours`, which silently does nothing until every clone configures it).
@@ -744,7 +749,7 @@ status: CURRENT
   belong to reconciliation.
 - `qty`: `<value> <unit> <kind>` — effort in person-days (h/d/w/mo/fte-mo; 8h=1d, 1w=5d,
   1mo=21d), duration in calendar days (h/d/w/mo), cost within one currency, count unit-matched.
-- `about`: `<predicate> -> <slug>` for relationship claims; stored once, under the subject.
+- `about`: `<predicate> -> <slug>` for relationship claims; stored once, under the subject. Several share one cell, separated by `; `; `not-yet-honored-by -> ANALYSIS_<name>` (Hybrid: `SHADOW_<doc_key>`) marks a claim the code does not yet honor (`distillation.md` §2).
 - `state`: `OK` | `CONTESTED <id>[,..]` | `SUPERSEDED <id>[,..]` — per claim, never per
   node; a split bundle (`reconciliation.md` §Splitting) names all its successors.
 - A tombstone (merged/renamed topic): `status: SUPERSEDED` + `redirect_to: <slug>`, body empty.
@@ -812,6 +817,25 @@ how a dangling pointer survives a green run:
 Write these two values with **no trailing `# comment`**: the frontmatter reader does
 not strip inline comments, so the comment lands inside the value.
 
+**Intake hygiene fields** (`distillation.md` §1 owns the rules):
+
+```markdown
+redacted_at_intake: [password, personal-data]
+credential_scan: reviewed — vendor manual's sample value, not a live credential
+original_ref: wiki://team-space/app-config
+```
+
+- `redacted_at_intake:` — the kinds replaced by `[REDACTED: <kind>]` before storing.
+  When present, the sidecar carries **no `original_sha256:`** and no non-text original
+  is copied beside the extraction.
+- `credential_scan: reviewed — <reason>` — a human cleared a flagged line as a false
+  positive. Only this clears the check; a reason is required.
+- `original_ref:` — a non-local identifier of the original; recorded, never resolved.
+
+A **tombstone** (a withdrawn artifact) is renamed `<stem>-withdrawn-<YYYYMMDD>.<ext>.meta.md`
+and keeps `date:`, `provenance:`, `supersedes:` and `withdrawn: <reason>` — and **no
+`sha256:` or `original_sha256:`**. Its bytes are gone.
+
 `provenance:` has a consumer too: a claim row filed `prov: GIVEN` whose artifact's
 sidecar declares anything else warns. Declare the chain the artifact actually has —
 an OCR, a transcription from an image, a translation are not first-hand evidence, and