feat: tiered confidential-compute escalation contract (#22) - #24
Merged
Conversation
Adds ConfidentialComputeEscalation (SourceOS-vs-Apple ModelCarry spec section 5.2): model execution escalates to a higher confidential-compute tier (on_device -> sealed_enclave -> attested_tee) based on the data-residency / sensitivity class of the inputs, and the escalation decision is governed and receipted. - contracts/confidential-compute-escalation.schema.json: ordered compute tier lattice, sensitivity/residency class -> minimum-tier map, and a receipted decision record (chosen tier + reason + attestationRef + SHA-256 receipt). SHA-256 is the authoritative receipt hash (FIPS 180-4). - tools/validate_confidential_compute_escalations.py: structural validator with teeth, wired into make validate. Teeth (fail-closed is the core invariant): - a request satisfied by its chosen tier VERIFIES; - a request run BELOW its required minimum tier is REJECTED; - a chosen tier requiring attestation with no attestationRef is REJECTED; - a non-monotonic tier lattice is REJECTED; - an undeclared sensitivity class is REJECTED (never defaulted). Follow-up (@mdheller): live TEE attestation verification; governed staged pre-load + atomic swap (#21). Refs #22, #20.
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
Closes the §5.2 gap from the SourceOS-vs-Apple ModelCarry analysis: a tiered confidential-compute escalation. Model execution escalates to a higher confidential-compute tier (
on_device→sealed_enclave→attested_tee) based on the data-residency / sensitivity class of the inputs, and the escalation decision is governed and receipted — the SourceOS analogue of Apple's on-device → Private Cloud Compute boundary.Consume-not-fork; matches the existing manifest/boundary house style (schema + stdlib validator + valid/invalid fixtures +
maketarget). Builds onModelCarryManifest(#20, MERGED).contracts/confidential-compute-escalation.schema.json— ordered compute-tier lattice, sensitivity/dataResidencyClass→ minimum-tier map (residency vocab aligned with the estate InferenceReceipt), and a receipteddecision(chosen tier + reason +attestationRef+ SHA-256 receipt).tools/validate_confidential_compute_escalations.py— structural validator, wired intomake validate.docs/confidential-compute-escalation.md— contract, invariants, teeth.SHA-256 is the authoritative receipt-hash algorithm (FIPS 180-4). Fail-closed is the core invariant.
Teeth
…attested-tee.json(valid)…below-minimum-tier.invalid.json…missing-attestation.invalid.jsonattestationRef.…non-monotonic-tiers.invalid.json…unknown-class.invalid.jsonsensitivityClassMap(never defaulted to weakest).Verified locally:
make validateandmake release-dry-runboth green.Boundary / follow-up (@mdheller)
Structural contract only — no live TEE attestation, no compute provisioning, no runtime authorization. Follow-ups:
Refs #22, #20.