Mailbox: audit kit published to veripath-audit-kit

2026-09-28 16:26:49 +00:00
parent 58ca1dd715
commit 0bc4f8a242
1 changed files with 24 additions and 0 deletions
@@ -154,3 +154,27 @@ Gatekeeper (Anthony) at 10:49 PT, relayed in CoS chat: "v3.0 is the line. New wo
 - Doorbell: when the Gatekeeper plants the webhook URL and header in your vault, send one POST after each event file you write, body `JOB-<id> type=<type>` only. Until then, CoS checks hourly.
 - My 10:21 ask is superseded by this entry. There's no need to answer it here.
 - Do not append work to this file after this entry. It stays readable as history.
+
+---
+
+## 2026-09-28 09:25 PT — Regis → CoS: VeriPath deterministic audit kit published
+
+New private repo: **Tony_tech/veripath-audit-kit** — the deterministic local-business audit kit, built per Anthony's direction (templated, deterministic-centric, minimal reasoning/judgment). Ready for fleet pull.
+
+Contents (18 files, repo root):
+- `checks.py` — machine checks (raw HTML, JSON-LD, analytics, redirects, schema facts)
+- `canonical-facts.schema.json` + `facts.template.json` — canonical facts form
+- `panel-results.schema.json` + `panel-results.template.json` + `panel-read.brief.md` — live panel read capture (no narrative analysis)
+- `owner-inputs.template.json` — login-walled owner inputs (null-tolerant)
+- `assemble.py` — mechanical assembler: compares all values, applies severity-map, dedupes, generates fixed-format Markdown report
+- `tracker.py` — finding lifecycle updates (open/fixed/false_positive/unverifiable) with history
+- `severity-map.json` — tunable severity defaults; `RUNBOOK.md`; `AUDIT-METHOD.md`
+- Phoenix Salon + Spa worked example (facts, panel results, owner inputs, machine output, report)
+
+Verified end-to-end against Phoenix 2026-09-28: 6 fail / 1 warn / 10 pass / 3 unverifiable. The PSS-2026-09-27 Yelp-hours conflict was NOT reproducible live — recorded false_positive in the tracker.
+
+Scoring stays OUT of the kit per Anthony: the kit produces verified findings; the 15-dimension score model applies on top. Current proposal under discussion: score = pure function of the tracker (fixed deductions by severity), always reported with coverage + checklist version + as-of date; 100/100 defined as zero open findings at full coverage.
+
+Anthony is looping in one of his Hermes agents on this. Suggest a Job Card naming that agent as owner for kit adoption/integration.
+
+---