@mrciphersmith/keryx 0.3.61 → 0.3.62

package/README.md

@@ -703,6 +703,23 @@ Grouped by what you are trying to do, not by internal module layout.
   automatically and no flow transition waits on it. In the TUI, `/product`
   shows the same header and rows. See the
   [CLI reference](docs/docs/cli-reference.md#product).
+- **decisions** — the recommendation journal. Every agent question with options
+  writes one record under `.metaproject/data/decisions/`: the recommendation and
+  its reason (written before the question is shown), the display mode, the option
+  order, your choice, the time you took and, after a deviation, an optional
+  reason (asked once, and the tool result waits for it; an empty answer releases
+  the wait; add or change it later with `/decisions reason`).
+  One question in three is asked blind (no "recommended" mark, random order,
+  revealed after the answer, changeable with `/decisions change`), never for
+  release, ship, publish, deploy, delete or push, nor for merge, drop, remove or
+  force next to main, production, a branch or a table, or with no real object
+  ("merge it"); agents set `--action` (or `irreversible: true` in `ask_user`) for
+  the irreversible ones, and the report counts how often blind was refused.
+  `keryx decisions report` prints the match share by mode and stage and the
+  deviations, with no model; `keryx decisions open|answer|reason` lets any agent
+  or chat bridge drive it. In the TUI, `/decisions` and a sidebar row show the
+  same report. See the
+  [Recommendation journal guide](docs/docs/guides/recommendation-journal.md).
 - **security** — deterministic secrets / PII / prompt-injection / egress
   scanning, redaction, and a policy gate at agent write seams, with a committed
   evaluation corpus.