open/llm-security-commons
1
0
Fork 0
Code Issues Releases 1 Activity

docs(manifest): the active-content fixtures pin a version, and nothing said so

Browse source 
The seed runtime's v1.0.0 freezes its exported Python surface and explicitly
not its detection behaviour. The manifest pinned commit and version per
measurement block but never recorded that the thing pinned is a version rather
than a frozen classification.

manifest 0.5.2 -> 0.6.0, one new field next to active_content_provenance.
asymmetry, bounded by what the fixtures actually assert: all seven carry
pattern_id only, so three of the four calibration dimensions cannot move them.
Both pins named, not one. Their statement is attributed, not restated as ours.

Also closes the omission 0.7.3 named: the same misquote in
docs/secret-egress-divergence.md:75-76. Not the fix the note implied - those
lines are one single-backtick span across a line break, so the outer delimiter
is promoted to double backticks instead.

spec section 7 deliberately untouched and named in CHANGELOG.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016yZobrgUiRtpLSWx8i7u2Z
This commit is contained in:
Kjell Tore Guttormsen 2026-08-13 23:09:33 +02:00
commit c23aea9062
3 changed files with 59 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/secret-egress-divergence.md
View file

@ -72,8 +72,8 @@ rather than by measurement.
This is the finding a membership table would hide, and it is the one a consumer implementing
from commons will get wrong first.
`signatures/secret-egress.json` declares `match_semantics: "first match wins; patterns are
evaluated in ascending order"`, marks `ordering.normative: true`, and names
`signatures/secret-egress.json` declares ``match_semantics: "first match wins; patterns are
evaluated in ascending `order`"``, marks `ordering.normative: true`, and names
`last_entry_is_load_bearing: "JWT (three-part token)"` — the JWT entry is placed last
precisely so a token inside an `Authorization` header is reported as the header, not as a
bare JWT.