Skip to content

docs(efficacy): add the score.py rescore of thin hybrid to round 4's verdicts - #1956

Merged
braboj merged 2 commits into
mainfrom
docs/round-4-rescore
Oct 17, 2026
Merged

braboj merged 2 commits into
mainfrom
docs/round-4-rescore

Conversation

@braboj

@braboj braboj commented Oct 17, 2026

Copy link
Copy Markdown
Collaborator

Follows #1954 and closes no issue.

docs/audits/2026-10-17-round-4.md, in the hybrid section, now gives the score.py rescore of the three thin hybrid trees with TARIFF_SECRET_KEY supplied. It includes the probes, which the direct re-run did not read. It also drops the matching "What is owed" item.

Trial Build suite Security probes Data-protection probes
hybrid-1 83.7 % 1.00 1.00
hybrid-2 94.6 % not measured 0.00
hybrid-3 82.4 % 0.82 1.00
  • The rescore was taken in a root restored from the verified archive, so the registered scoring area is untouched. It used main at 8f09318, and the hidden suite at 5792094, which differs from 65bfb9a only in AMBIGUITIES.md.
  • The readings and their command are archived in braboj/tariff-runs under rounds/2026-10-16-thin-sensitivity/score-py/ (049b95b).
  • The other thin arms' ranges quoted in the text were read from r4-thin-scoring/security-scores: security probes 0.55 to 0.91, and data-protection probes at 1.00 only in full-3.
  • hybrid-2's security reading fails at boot with No module named 'click'. Its registered reading was missing too.
  • These readings are unregistered and stand beside the verdicts, which are unchanged.

No CHANGELOG entry: this is a benchmark report. run_smoke.py passes 34/34.

🤖 Generated with Claude Code

…verdicts

With the key supplied, hybrid-1 and hybrid-3 read 0.82 to 1.00 on the
security probes and 1.00 on data protection; hybrid-2 fails at boot on an
undeclared dependency, as its registered reading did.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@braboj
braboj merged commit 1d8b291 into main Oct 17, 2026
1 check passed
@braboj
braboj deleted the docs/round-4-rescore branch October 17, 2026 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant