cc-os/plugins/os-adr/eval-b/fixture/project
jared 7523663889 os-adr: trigger-conditioned wording from Eval B autoresearch loop (sonnet 8/8, haiku 7/8)
Five-iteration /autoresearch wording experiment against the Eval B baseline
(haiku 0/8, sonnet 5/8). Checker/fixtures/scenarios/rubric frozen; wording
surfaces: hook PRESENT_NOTE, find/create SKILL.mds, fixture CLAUDE.md
(declared a surface upfront — it is the real-project adoption template).

- Hook note + skill descriptions: when->then trigger-conditioned phrasing
  (H1 confirmed, both tiers)
- find skill: explicit-unconditional reversal->supersede offer where find's
  output is on screen (fixed sonnet W3)
- Mechanical lower-tier trigger: before first edit to any existing file,
  run find on those paths; additions count (fixed haiku R1/R4)
- New eval-b/fixture/project/CLAUDE.md carrying the same rules

Final grid: sonnet 8/8, haiku 7/8 (W3 axis-b judge flicker). Open: channel
ablation (hook vs CLAUDE.md) not run; R4-nograph now passes both tiers.
Hypothesis->result map: vault note os-adr-eval-b-wording-experiment-hypotheses.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-04 14:49:15 -04:00
..
bin Add os-adr evaluation harnesses (Eval A and Eval B) 2026-07-03 16:44:42 -04:00
config Add os-adr evaluation harnesses (Eval A and Eval B) 2026-07-03 16:44:42 -04:00
docs/adr Add os-adr evaluation harnesses (Eval A and Eval B) 2026-07-03 16:44:42 -04:00
lib Add os-adr evaluation harnesses (Eval A and Eval B) 2026-07-03 16:44:42 -04:00
.gitignore Add os-adr evaluation harnesses (Eval A and Eval B) 2026-07-03 16:44:42 -04:00
.graphifyignore Add os-adr evaluation harnesses (Eval A and Eval B) 2026-07-03 16:44:42 -04:00
CLAUDE.md os-adr: trigger-conditioned wording from Eval B autoresearch loop (sonnet 8/8, haiku 7/8) 2026-07-04 14:49:15 -04:00
README.md Add os-adr evaluation harnesses (Eval A and Eval B) 2026-07-03 16:44:42 -04:00

README.md

relay

A small CLI that delivers webhook payloads to configured endpoints and reports on delivery outcomes.

  • bin/relay send <url> <json-payload> — queue and deliver one payload
  • bin/relay report — summarize failed deliveries

Configuration lives in config/relay.yml. Failed deliveries that exhaust their retries are appended to the dead-letter file for manual replay.

Architecture decisions are recorded in docs/adr/.