From ddee20e577de04747f3ab350ceec991583ea351d Mon Sep 17 00:00:00 2001 From: Danny Gillespie Date: Fri, 3 Jul 2026 20:30:36 +0100 Subject: [PATCH] docs(readme): note aperture dial provenance (grafted from auto-aperture) The aperture read imported only the novel uncertainty-scoring primitive from an auto-aperture skill fork; the rest already existed as cut/lock/decide/build/verify/ compile and was dropped to avoid a second dialect. Co-Authored-By: Claude Opus 4.8 (1M context) --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 913723b..cc464ea 100644 --- a/README.md +++ b/README.md @@ -174,6 +174,13 @@ depth that earns it: snap to `build → verify` when the task is trivial, open t when it isn't. In Codex, ask it to use the matching Torque Loop skill, for example `torque-loop:ignite` or `torque-loop:evolve`. +> **Provenance — the aperture dial.** The aperture read was grafted from an external +> `auto-aperture` skill fork. Rather than import it wholesale, we examined it against the +> existing loop: most of it already existed under other names (`cut` / `lock` / `decide` / +> `build` / `verify` / `compile`), so we took only its one novel primitive — scoring +> uncertainty to meter how much loop to run — and dropped the rest to avoid a second +> dialect. General mechanism, ratchet's own vocabulary. + ### Core loop | Command | Purpose |