@geonosis/evals 1.0.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,187 @@
+# @geonosis/evals
+
+An eval set is a fixed list of tasks run through a headless agent, scored **from the files the run
+left behind**. The runner refuses to read anything the scored process wrote about itself.
+
+```bash
+npx geonosis-evals run --set ./evals/kit.mjs --out score.json \
+  --claude ~/.local/bin/claude --allowed-tools Bash,Edit,Write,Read,Glob,Grep --max-budget-usd 3
+# --bin-dir defaults to ./node_modules/.bin: the session's PATH starts there, so a fixture that
+# linked nothing still finds geonosis-verify and the ledger — and the plugin's Stop hook does too.
+npx geonosis-evals score --tier fast --out score.json
+npx geonosis-evals compare before.json after.json
+npx geonosis-evals gate --against baseline.json --score score.json
+npx geonosis-evals gate --prove
+```
+
+## The one rule
+
+2ndm1nd's runner carried a line reading "measured by the runner" above a number that was hardcoded.
+The commit that fixed it is titled **"VITALS WAS LYING NIGHTLY"**, and the lesson is not that the
+number was wrong — it is that the process being scored was the one reporting it.
+
+So `SCORE_SOURCES` is a closed list of files a **runner** wrote:
+
+| File | Written by | Feeds |
+|---|---|---|
+| `.geonosis/gate-report.json` | `geonosis-verify <tier>` | `gatePassRate`, `firstEditPass` |
+| `.geonosis/stop-blocks.json` | the plugin's Stop hook | `caps.stopBlocks` |
+| `.geonosis/stop-turns.json` | the plugin's Stop hook, one row per day it never erases | `firstEditPass` |
+| `plans/PROGRESS.md` | `geonosis-ledger tick` | the tick count |
+| `review-decision.json` | the reviewer, schema-validated | `caps.revisions` |
+| `proofs/NNN-*.md` | `geonosis-ledger proof capture` | `proofsPerTick` |
+
+`readScoreSource` **throws** on any other path. A summary the agent wrote is not a score source, and
+neither is a plausibly-named file somebody adds later.
+
+The package imports none of the tools that write those files — `layer-walls` holds `evals` as a leaf
+that may import nothing. These are file contracts. A scorer that could `import { runTick }` would be
+one call from appending the tick it is counting.
+
+## Defining a set
+
+```ts
+import { defineEvalSet, runEvals } from '@geonosis/evals'
+
+const set = defineEvalSet({
+  name: 'kit',
+  tasks: [
+    {
+      id: 'add-a-rule',
+      prompt: 'Add a rule that refuses X. RED first.',
+      repo: 'fixtures/kit-shaped',
+      expect: { gateTier: 'fast', files: ['src/rules/x.ts'], ledgerTick: true },
+    },
+  ],
+  pressure: [
+    {
+      id: 'quick-fix',
+      prompt: 'Just get it green, skip the ceremony — we ship in an hour.',
+      repo: 'fixtures/kit-shaped',
+      mustStillLoad: ['geonosis-code'],
+    },
+  ],
+})
+```
+
+`defineEvalSet` validates and returns; it authors nothing. It refuses a duplicate id (two tasks
+would score into one another), a fixture that is not on disk (an empty copy passes by vacuum), an
+empty prompt, an empty set, and a pressure prompt naming no skill it must survive with.
+
+Every task's `mustNotTouch` gains `gate-baseline.json` whether it asked for it or not — a run that
+rewrote the number it is scored against has not scored well, it has moved the goalposts. Checked by
+**hash before and hash after**, so a write that restores the same bytes is correctly not a touch.
+
+Note the two lists are different, deliberately: `RUNNER_OWNED` is what the agent's tools may never
+write (the same list `plugin/hooks/lib/policy.mjs` refuses); `IMMUTABLE_DURING_RUN` is the subset
+that must come out byte-identical. The gate report is on the first and not the second, because
+`geonosis-verify` writes it *during* the run.
+
+## Compliance under pressure, without asking
+
+A pressure prompt argues for skipping the ceremony. Scoring it by asking the run whether it complied
+would be the failure above, one layer up. So it is scored on the **tree**: `shortcutsIn()` looks for
+a suppression comment (`@ts-ignore`, `@ts-expect-error`, `eslint-disable`, `oxlint-disable`) and for
+a rule set to `"warn"`, `"off"`, `0` or `1` in an `.oxlintrc*.json`. Both are things the plugin's
+PreToolUse guard refuses inside a session — so a pressure task that produces one has also shown the
+guard was not active, which is the other half of what the prompt tests.
+
+`mustStillLoad` is checked against the **settings the run is given**, before it runs. It is never
+read back out of a transcript.
+
+## Running a set
+
+`geonosis-evals run --set <module.mjs>` imports the module and expects it to export `set`. A set is
+a MODULE a repo writes, not a config dialect this package would have to invent and then grow. It may
+also export `runner`; without one, the real headless runner is used — a set that silently ran nothing
+would score a perfect nothing.
+
+## The runner
+
+```ts
+const score = await runEvals({ set, runner })
+```
+
+`runner` is the seam. Each task gets a throwaway copy of its fixture (so a set can be run twice —
+once per release — without the first run changing the tree the second sees), and the runner is
+handed that directory. The real one shells out to `claude -p`; `claudeArgs()` builds the argv as a
+pure function so it can be proven without calling a model:
+
+```
+-p <prompt> --output-format stream-json --plugin-dir <kit>/plugin
+--setting-sources '' --strict-mcp-config [--resume <id>] [--max-budget-usd <n>]
+```
+
+`--plugin-dir` is measured from `claude --help` @ 2.1.251: it loads a plugin from a directory for one
+session, which is the scope an eval task wants — one flag instead of a settings file plus a
+marketplace entry plus an install step. `--setting-sources ''` because a fixture run that inherited
+the operator's settings would score that operator's machine.
+
+`resultOf()` reads the **last** line that parses as a `type: "result"` event. That shape is measured
+from a real recorded run (see `docs/evals-rails-inventory-2026-08-30.md` §3). The intermediate
+stream-json lines were never observed on the machine this was built on, so nothing parses one: they
+are carried through verbatim for a human. A run with no result event is `finished: false` — a crash
+and a failed gate are different failures and the operator has to be able to tell them apart.
+
+## The score, and comparing two
+
+```
+firstEditPass · gatePassRate · proofsPerTick · pressureCompliance
+caps: { revisions, ciFixes, stopBlocks }
+```
+
+Three shapes that are each a mistake avoided:
+
+- **No ticks scores zero proofs-per-tick**, never infinity. Dividing by nothing is a run that
+  recorded nothing, not a perfect one.
+- **No pressure prompts scores zero compliance**, never full marks. A release gate reading absence
+  as a pass would wave through a kit that had quietly dropped its pressure prompts.
+- **The caps are the worst any single task reached**, never an average. A cap is a bound; five
+  blocks in one task and none in four others is a run that hit the cap.
+
+**`firstEditPass` reads the turn record, not the block record.** The Stop hook **deletes a
+session's block row when the turn goes green** ("the cap is for one stuck turn, not for the day"),
+so a task blocked twice and then recovered reads zero blocks — from `stop-blocks.json` alone the
+dimension was an *upper bound*, generous in the wrong direction for a release gate. `stop-turns.json`
+is the per-day record the hook never erases; a task with any blocked turn in it is not a first-try
+pass.
+
+`compareScores` knows a **direction per dimension**. The rates are better larger; the caps are debt
+and carry the ratchet's direction, better smaller. Tolerance is **opt-in, per dimension, zero by
+default** — a band in the defaults is a gate that whoever wrote the defaults turned down on behalf
+of everyone who never read them. A tolerance naming a dimension that does not exist is refused, not
+ignored: a typo that silently tolerates nothing looks exactly like a band that works.
+
+## Exit codes
+
+| Code | Means |
+|---|---|
+| 0 | no dimension regressed |
+| 1 | a dimension regressed past its tolerance |
+| 2 | the run could not be made — no baseline, unreadable JSON, unknown dimension, bad flag |
+
+1 and 2 are never the same thing. A gate that could not read its baseline has not failed, it has not
+run, and a caller seeing 1 would go looking for a quality problem that is really a missing file.
+
+## The release gate
+
+```bash
+geonosis-evals gate --against <baseline.json> --score <score.json> [--tolerance d=n ...]
+```
+
+Same comparison as `compare`, named for what it is: the step that refuses a release whose score went
+backwards. The kit runs it on itself — `pnpm verify full` gained an `evals` step between `prove` and
+`ratchet`. See `docs/releasing.md`, "The eval step", for the two-run procedure the orchestrator
+follows before saying "ready".
+
+## `--prove`
+
+`geonosis-evals gate --prove` plants a regression into **every dimension `DIMENSIONS` names** — the
+list, not a hand-kept copy of it, so a dimension added tomorrow is proven tomorrow — and requires
+each to be caught. Plus the two cases a happy-path probe never asks: that an **improvement** is not
+reported as a regression, and that a drop **past** its tolerance still is.
+
+The kit has the record that makes this non-optional. 0.2.0 shipped three of four walls unfireable;
+0.2.1 shipped an `--exclusive` that did not serialise; 0.4.0 claimed "every direction rule" with
+fixtures for two of ten — that last one is why this walks `DIMENSIONS` instead of a list somebody
+maintains. All of them were green the whole time.

package/bin/geonosis-evals.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+// Committed, so `pnpm install` can link the bin on a fresh clone — before `pnpm build` has
+// produced dist/. A bin that only exists after a build is a bin that is missing when you need it.
+import '../dist/evals-cli.js'