docs(profile): add the field-positioning table - #32
Merged
Conversation
…ung)
A four-foil comparison — Sigstore, mcp-scan/Invariant, ARM/FIDES, prx —
across {rung, enforcement point, attests/enforces, what it can't}. Makes
the positioning claim legible to a skimmer with real named tools instead
of an abstraction: the shipped agent-safety toolchain converged on
identity + integrity/scanning; the authority rung (and inter-contract
enforcement above it) is sparsely tooled and where this org works.
Honesty: prx's "what it can't" names the integrity axis as a gap on
purpose (composes with mcp-scan, doesn't replace it); inter-contract
enforcement and the prx-vs-guest-room delta live in the footnote graded
Aspirational/Partial, not in the cells. No generated block touched.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a four-foil comparison table to
profile/README.md, between Provenance & substrate and Contracts beyond authority — its thematic home, since the table's claim is provenance attests origin, not authority.Rows: Sigstore · mcp-scan/Invariant · ARM/FIDES · prx. Columns: rung · enforcement point · what it attests/enforces · what it can't.
Why
The shipped agent-safety toolchain has converged on two rungs — identity (Sigstore) and integrity/scanning (mcp-scan, ARM/FIDES). Almost nothing is authority — is this privileged effect attributable to a signed owner and permitted for it. That emptiness is the positioning; the table makes it legible to a skimmer with real named tools instead of an abstraction.
Honesty calibration
guest-roomenforcement delta live in the footnote, graded Aspirational/Partial — not in the cells.Checklist
mainregistry-graphblock untouched;knowledge-checkpath not triggered🤖 Generated with Claude Code