kairos-chain 3.65.0 → 3.67.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0b5f8504e1a59fe2e58603f654ad32a747381897a62dba70ba436388c5be3f55
-  data.tar.gz: c4c86ca90fb56858a45c126aca497277846225c1b127549700be1e80484c0755
+  metadata.gz: 0506a7cc642b812cabab1bb2840d928e1a9f550bf2486466741a54b6d71ee74f
+  data.tar.gz: bf1ff56bf44cf13d78c01dedd26d0bdc6188453dea18ca1975027f2b3a6c7f8d
 SHA512:
-  metadata.gz: 3535630f908f30fc87319e960207ea5552de1f29284211cf24e4802171a7699b3ebcde4ebce74875341d368004ea04ccf36211f4b68037755907a1ef77550ae6
-  data.tar.gz: a01fbf7861eac890a2d020ce8a0606970d41a7a9f3d0f1840f1db7a19580c87f77b77af1ffebd4028c538f4535b562db78adff1c847389c2fd6a162dda5fa3f4
+  metadata.gz: 7c4ef69fda47be727f4ba9da5f44ee95d6cf63f5cff559bb3b3b2cc7dfc8df67022f47086d6468b6dc332f41b95908745557e294d2bc8d1e4dec70a763ec208a
+  data.tar.gz: 1838ad363f5bc95a8e5abdb1ca07c7be7891a0ab5410cbdc22456b5187bc4297f193d57f2a93b57578582704702b788eb2e5e78d5c4ff7c0f978bcc58c8cd4c5

data/CHANGELOG.md

@@ -4,6 +4,33 @@ All notable changes to the `kairos-chain` gem will be documented in this file.
 
 This project follows [Semantic Versioning](https://semver.org/).
 
+## [3.67.0] - 2026-08-15
+
+### Added
+
+- **The Minimum Nomic bench ships.** Three language models play a self-amending
+  game with nine changeable rules, no goal and no termination condition, while a
+  fourth decides only who speaks next. It lived at `bench/minimum_nomic/` in the
+  development checkout, which the gemspec never walked, so nobody outside this
+  repository could reproduce a run. It is now the `minimum_nomic` SkillSet under
+  `templates/skillsets/`, with the five scripts in `bin/`.
+
+  The single thing that kept it out was a hard-coded `../../.kairos/` path to the
+  `llm_client` adapters, which resolved only in the development checkout.
+  `llm_client` is now resolved as a **sibling SkillSet**
+  (`../../llm_client/lib/llm_client`), the same relative path in the gem's
+  templates and in a projected instance. When it is absent the run aborts naming
+  both directories it searched, rather than failing inside a `require`.
+
+  `bin/cross_model.rb` is new: it analyses a stored game with one named model at
+  one named reasoning effort, instead of the panel recorded in the game's own
+  line-up. Without it, a comparison between model generations reuses both stored
+  panels and confounds generation with effort — the stored games ran
+  `claude-opus-4-6` at medium and `claude-opus-5` at high.
+
+  Not yet demonstrated: no game has been played from an installed gem. Until one
+  has, treat distribution as untested.
+
 ## [3.65.0] - 2026-08-13
 
 ### Changed

data/lib/kairos_mcp/version.rb

@@ -1,4 +1,4 @@
 module KairosMcp
-  VERSION = "3.65.0"
+  VERSION = "3.67.0"
   CHANGELOG_URL = "https://github.com/masaomi/KairosChain_2026/blob/main/CHANGELOG.md"
 end

data/templates/skillsets/kairos_hook_projector/mode_hooks/_EXAMPLE.json

@@ -50,6 +50,7 @@
     "Stop": [
       {
         "gate": "readable_gate",
+        "_description": "Measures the turn's last message against declared readability limits — length, headings, tables, undefined shorthand, a missing diagram — and reports to its log, or blocks the turn once blocking is true.",
         "section": "§ Readable output",
 
         "_blocking_note": "false on purpose in the example. The vocabulary rule below is the one thing here that cannot be got right by reading: whether a shape is coined shorthand or an ordinary technical word depends on what you write about. Start in report-only mode, read your log for a week, then set this to true. Shipping the example with true meant a consumer who copied it as instructed was blocked on the first message mentioning a character encoding.",

data/templates/skillsets/kairos_hook_projector/plugin/SKILL.md

@@ -20,16 +20,42 @@ under `.kairos/hook_configs/`.
 Not auto-installed (not a core SkillSet): install it by name first —
 `system_upgrade command="apply" approved=true names=["kairos_hook_projector"]`.
 
-1. Copy `mode_hooks/_EXAMPLE.json` beside your mode body as
-   `<mode>.mode_hooks.json` (e.g. `.kairos/skills/masa.mode_hooks.json`).
-2. Edit `mode_name` inside it to `<mode>` — filename and field must agree —
-   and replace the example numbers with your own.
-3. `mode_hooks_validate` reports what the copy still needs.
+1. `mode_hooks_add mode="<mode>" gate="readable_gate"` writes
+   `<mode>.mode_hooks.json` beside the mode body — creating it, or appending
+   to it; an entry with the same gate already on the event is refused, never
+   overwritten. Omitting `mode` targets the active mode, and on a stock init
+   that is `tutorial` — a gem-shipped template body carrying no
+   readable-output norm — so name your mode. The entry comes from the
+   catalogue (`mode_hooks/_EXAMPLE.json`): event, section, blocking, and
+   starting params. Tune the numbers in the written file afterwards, they are
+   the mode's own — and edit `section` to a heading your mode body actually
+   contains: it is copied from the catalogue, it is a claim about your own
+   text, and the gate quotes it verbatim in every block reason. Called
+   without `gate` it lists the catalogue and writes nothing. It stops at the
+   declaration and never touches `.claude/settings.json`.
+2. Or by hand, for someone who wants to write the numbers themselves: copy
+   `mode_hooks/_EXAMPLE.json` beside your mode body as
+   `<mode>.mode_hooks.json` (e.g. `.kairos/skills/masa.mode_hooks.json`),
+   then edit `mode_name` inside it to `<mode>` — filename and field must
+   agree — edit `section` to a heading your mode body actually contains (the
+   gate quotes it verbatim in every block reason), and replace the example
+   numbers with your own.
+3. `mode_hooks_validate` reports what the declaration still needs.
 4. `mode_hooks_project` proposes by default and writes nothing; to install,
    call again with `apply=true` and the `confirm_sha256` from the proposal.
 5. `mode_hooks_validate`, run again, answers whether the gate is installed:
    its `installed` check compares declaration and `.claude/settings.json`.
 
+The catalogue is gem-shipped and is not an extension point on the instance:
+`system_upgrade` overwrites `mode_hooks/_EXAMPLE.json` on any reinstall — at
+the same version, with no warning, without naming the file — so an edit to
+the installed copy does not survive. Adding a gate kind is a core release
+act: the catalogue entry, the kind in the compiler's known-gate table (until
+then every call refuses it as `unknown_gate`), and the gate implementation
+itself. Your declaration lives beside the mode body, outside the SkillSet,
+for the same reason — the tool refuses to write declarations inside the
+SkillSet directory because an upgrade would undo them.
+
 ## Removing a mode's hooks
 
 Two routes, and either works: empty the declaration's `hooks` object
@@ -54,6 +80,9 @@ installed command names them; delete them by hand if you want them gone.
 
 ## Tools
 
+- `mode_hooks_add` — write or extend a mode's declaration from the catalogue
+  (`mode_hooks/_EXAMPLE.json`); append-only, stops at the declaration, never
+  touches `.claude/settings.json`. Without `gate`, lists the catalogue.
 - `mode_hooks_validate` (read-only) — mode body vs declaration drift, compile
   resolvability, and declared-vs-installed divergence in both directions.
 - `mode_hooks_project` — compile and install; touches only entries it placed

data/templates/skillsets/kairos_hook_projector/skillset.json

@@ -1,6 +1,6 @@
 {
   "name": "kairos_hook_projector",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Projects an instruction mode's declared hooks into the harness configuration. Stage 1 compiles a mode_hooks declaration to a hook artifact plus a compile record. Stage 2 installs it: mode_hooks_project proposes by default and writes nothing, applying only when the caller echoes back the artifact hash from the proposal, and rewriting only hook groups carrying this SkillSet's marker for that mode — hand-added hooks and other modes' hooks are counted and left alone. Ships the generic readable_gate implementation; a mode supplies its own thresholds, the core supplies none.",
   "author": "Masaomi Hatakeyama",
   "layer": "L1",
@@ -15,12 +15,14 @@
     "hooks_status_readonly",
     "mode_hooks_validation",
     "mode_hooks_projection",
+    "mode_hooks_declaration",
     "readable_gate"
   ],
   "tool_classes": [
     "KairosMcp::SkillSets::KairosHookProjector::Tools::HooksStatus",
     "KairosMcp::SkillSets::KairosHookProjector::Tools::ModeHooksValidate",
-    "KairosMcp::SkillSets::KairosHookProjector::Tools::ModeHooksProject"
+    "KairosMcp::SkillSets::KairosHookProjector::Tools::ModeHooksProject",
+    "KairosMcp::SkillSets::KairosHookProjector::Tools::ModeHooksAdd"
   ],
   "config_files": [],
   "knowledge_dirs": [],