strictlybetter

Run the strictlybetter meta-benchmark: the walled loop against a naive loop on fixture repos, reporting false-accept rate and cost per accepted improvement. Use when the user asks to benchmark, validate, or compare strictlybetter itself (not the target project).

Distill the strictlybetter ledger now: run the engine's plateau/bandit/false-promotion statistics, spawn the distiller to rewrite the inheritance body, store it, show the decision. Use when the user asks what the loop has learned, wants the inheritance body refreshed, or a campaign just ended.

Discover and instrument metrics for strictlybetter: spawn the metrologist, add the cards, measure the noise floor (sigma) with repeated runs, probe monotonicity, demote what fails. Use when a profile exists but no baselined metric cards do, or the user wants to add or re-measure a metric.

Orient strictlybetter on this repository: spawn the orienteer once, verify build/test/lint/bench commands by running them, store the profile. Use when strictlybetter has no profile yet, the toolchain changed, or the user asks to re-orient / refresh the project profile.

Run exactly one strictlybetter cycle: read the brief, pre-register a batch, spawn tiered experimenters into worktrees, submit, screen-measure, judge, blind-judge, confirm, accept or discard, record cost, distill on schedule. Use when a campaign is running and the Stop hook or the user says to continue it.

Show the strictlybetter campaign state: status line, the cold-start brief, and the budget counters, all quoted from the engine. Use when the user asks how the campaign / research loop is going, what is left, or what the next batch looks like.

Stop the strictlybetter loop at the next safe point by writing the STOP file; the Stop hook no longer continues the campaign. Use when the user says stop, pause, halt, or 'enough' about the research loop or campaign.

Universal research loop: orient on this repo, discover metrics, run pre-registered experiments, keep only strictly-better changes. Use when the user wants the repo/project improved automatically, mentions strictlybetter, a research loop, autoresearch, optimizing a metric, or continuous improvement.