@freetesh/zeno 0.9.1 → 0.10.0

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "zeno",
-  "version": "0.9.1",
+  "version": "0.10.0",
   "description": "Keeps your domain knowledge and AI rules local and enforces them, so Claude hallucinates less.",
   "author": {
     "name": "Ritesh Firodiya",

package/README.md

@@ -36,7 +36,8 @@ It has two halves that read the same config:
   constitution, your wiki and decision records, existing features and tasks,
   cost vs value, and the write-less ladder, then answers **DO IT**, **DO IT
   DIFFERENTLY** or **PUSH BACK** with citations. Push back stops work until you
-  give a reason; overrides are logged and feed `zeno learn`.
+  give a reason. Every verdict is logged; `zeno learn` shows how often the gate
+  stops you and turns repeated overrides into proposals.
 - **No assumptions.** A request is not a fact. Each claim in it ("users want
   this", "it is slow") is checked against the repo and its data sources and
   marked backed or not. Work that rests on an assumption stops until you agree
@@ -202,7 +203,7 @@ hooks/            session start: constitution titles, qmd refresh
 standards/        default standards
 packs/            vendor doc packs
 templates/        files init writes: dependency-cruiser base (synced) and starters
-scripts/          log-verdict.mjs — append-only override log
+scripts/          log-verdict.mjs — append-only verdict log
 cli/              the zeno CLI (TypeScript, vitest; built to cli/dist for npm)
 evals/            plugin evals and the fixture product
 ```

package/cli/dist/commands/learn.js

@@ -1,11 +1,11 @@
-import { proposals, readDecisions, readVerdicts, recordDecision } from "../learn.js";
+import { proposals, readDecisions, readVerdicts, recordDecision, summarise } from "../learn.js";
 import { findProducts } from "../run.js";
 import { requireEstate } from "./env.js";
 const DEFAULT_THRESHOLD = 3;
 export function registerLearn(program, env) {
     program
         .command("learn")
-        .description("turn overridden verdicts across products into proposals to change the rules")
+        .description("show how often the gate stops work, and turn overrides across products into proposals to change the rules")
         .option("--threshold <n>", "overrides of one principle before it is proposed", String(DEFAULT_THRESHOLD))
         .option("--approve <id>", "mark a proposal approved (then edit the standard)")
         .option("--reject <id>", "mark a proposal rejected; it returns only with new evidence")
@@ -23,7 +23,8 @@ export function registerLearn(program, env) {
             console.log(`${options.approve ? "approved" : "rejected"} ${target}`);
             return;
         }
-        console.log(`${entries.length} overridden verdict(s) logged across the estate`);
+        const s = summarise(entries);
+        console.log(`${s.total} verdict(s) logged: ${s.proceeded} went ahead, ${s.stopped} stopped, ${s.overridden} overridden, ${s.dropped} dropped`);
         if (found.length === 0)
             console.log("no proposals");
         for (const proposal of found) {

package/cli/dist/learn.js

@@ -1,5 +1,14 @@
 import { appendFileSync, existsSync, mkdirSync, readFileSync } from "node:fs";
 import { basename, join } from "node:path";
+export const OUTCOMES = ["proceeded", "stopped", "overridden", "dropped"];
+const outcomeOf = (entry) => entry.outcome ?? "overridden";
+/** How often the gate let work through, stopped it, or was overridden. */
+export function summarise(entries) {
+    const counts = Object.fromEntries(OUTCOMES.map((o) => [o, 0]));
+    for (const entry of entries)
+        counts[outcomeOf(entry)] += 1;
+    return { total: entries.length, ...counts };
+}
 const LOG = join(".context", "raw", "zeno", "verdicts.jsonl");
 const MAX_REASONS = 5;
 function readJsonLines(path) {
@@ -41,7 +50,9 @@ function toProposal(id, summary, entries) {
  * times, or one reason given in two or more products. A decided proposal comes
  * back only when its count has grown past what it was when decided.
  */
-export function proposals(entries, options) {
+export function proposals(all, options) {
+    // Only an override says a rule may be wrong; a verdict the user followed says nothing about it.
+    const entries = all.filter((entry) => outcomeOf(entry) === "overridden");
     const found = [];
     for (const [principle, group_] of group(entries, (e) => e.principles)) {
         if (group_.length >= options.threshold) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@freetesh/zeno",
-  "version": "0.9.1",
+  "version": "0.10.0",
   "description": "zeno CLI: keep your domain knowledge and AI rules in your repo, and enforce them.",
   "license": "MIT",
   "author": "Ritesh Firodiya",

package/skills/weigh/SKILL.md

@@ -134,17 +134,27 @@ Proceed only after the user agrees in writing ("agree", or "agree to 1–4").
 "Go ahead" to a verdict is not agreement to terms that were never shown. Work
 covers only the terms agreed to.
 
-## Logging (push back and overrides)
+## Logging (every verdict)
 
-When the user overrides a PUSH BACK, rejects a DO IT DIFFERENTLY or agrees to
-terms, append one line to the product's log so zeno can learn from it later.
-Pass each agreed term with its own `--term`:
+Log every verdict once, when you know what happened next. A trivial request
+that skipped the gate is not logged. `--outcome` is one of:
+
+- `proceeded` — work went ahead as the verdict said (DO IT, or an accepted
+  *Instead*).
+- `stopped` — you stopped and asked, and the user has not answered yet. Log it
+  when you stop; if the user later overrides, log a second line.
+- `overridden` — the user went on against a PUSH BACK, rejected a DO IT
+  DIFFERENTLY, or agreed to terms. `--reason` is required: the user's reason,
+  verbatim. Pass each agreed term with its own `--term`.
+- `dropped` — the user chose to drop the request.
 
 ```bash
-node ../../scripts/log-verdict.mjs --verdict push-back --principles C-04,C-14 \
-  --request "<one line>" --reason "<the user's reason, verbatim>" \
-  --term "<term 1>" --term "<term 2>"
+node ../../scripts/log-verdict.mjs --verdict push-back --outcome overridden \
+  --principles C-04,C-14 --request "<one line>" \
+  --reason "<the user's reason, verbatim>" --term "<term 1>" --term "<term 2>"
 ```
 
 (path relative to this skill). It writes to `.context/raw/zeno/verdicts.jsonl`
-in the current repo. Never edit or delete existing lines.
+in the current repo. Never edit or delete existing lines. `zeno learn` reads
+the log across products: how often the gate stops work, and which rules keep
+being overridden.