feat(trust): add SOVP-v1 pre-execution infrastructure attestation type (§5.2.1, §5.2.2)#48
Closed
litzki-systems wants to merge 1 commit into
Closed
Conversation
- Add SOVP-v1 to registered attestation types table in §5.2.1 - Add §5.2.2 with seven-property contract, example, and references - Extend digest field to structured object with alg + value - Cross-reference TRACE-v0.2 and install-manifest as complementary layers Closes ards-project#41
litzki-systems
requested review from
evalstate,
mindpower and
rvguha
as code owners
yepgent
added a commit
to yepgent/ard-spec
that referenced
this pull request
Jun 26, 2026
Per review feedback on ards-project#49 (litzki-systems): the detached JWS in §5.1.1 shares the RFC 8785 (JCS) canonicalization baseline with SOVP-v1's attestation payload (ards-project#48, §5.2.1). Note the shared signing primitive as a composition property — disjoint sections, no normative coupling. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
|
I'm closing this until your IETF proposal gets accepted. Please reopen with use-cases etc. at that time. |
Author
|
Understood and appreciated, @evalstate. Will reopen once draft-litzki-sovp advances to a later stage. The layer position and seven-property contract remain available as reference in the meantime. |
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
2 participants
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.
Summary
Adds SOVP-v1 as a documented attestation type in §5.2.1 and §5.2.2, complementing TRACE-v0.2 (runtime governance) and install-manifest (install-time consent).
The layer SOVP-v1 occupies
The four-layer stack that converged in this repo this week:
Each attests a distinct axis. As @imran-siddique confirmed: "What SOVP addresses is the infrastructure the enclave sits on: cluster hardening, network topology, sovereign compliance of the broader environment. Those are distinct axes, not overlapping ones."
Changes
digestfield fromStringto structured object (alg+value) for content-addressable verificationReferences
application/install-manifest+jsonin the AI Catalog (install-time safety envelope) #43