docs(schema): read runtime.platform's two situations as examples - #272
Merged
Merged
Conversation
#234 aligned the schema description with spec 3.1.1, but its enumeration reads as exhaustive. The lead clause is "no hardware root of trust"; the two named situations are a development-mode execution and a record assembled from evidence produced outside the runtime. A production runtime emitting for its own executions, origin.kind self, with no TEE anywhere in its stack, is covered by the lead clause and named by neither, so the description narrowed the rule again in a smaller way. "For example" restores the reading without adding a case or diverging from docs/schema.md. Both schema copies carry it. Raised by @chernistry on #232 and again on #234. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012yyHFd4YA35oNUjhrztJSb
imran-siddique
deleted the
docs/schema-platform-examples-are-examples
branch
September 2, 2026 19:27
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 this changes
Follow-up to #234, taking @chernistry's remaining wording note from #232.
#234 aligned
runtime.platform's schema description with spec 3.1.1. Its lead clause is "no hardware root of trust", and it then names two situations: a development-mode execution, and a record assembled from evidence produced outside the runtime. Read as written, the enumeration is exhaustive.A third class is covered by the lead clause and named by neither: a production runtime emitting for its own executions,
origin.kind: self, with no TEE anywhere in its stack. So the description narrowed the rule again, in a smaller way than the one #234 fixed.Adding "for example" before the enumeration restores the reading. No case is added and nothing diverges from
docs/schema.md. Both schema copies carry the change, astest_packaged_schema_matches_repo_schemarequires.This is not a hypothetical class. It is the same one under argument in #242, where the proposal was to require an all-zero
runtime.measurementfor production software-only records. I have ruled against that: a software-only record with no hardware root can still carry a real software commitment, and all-zero is reserved for a producer making no commitment at all.Type of change
Spec section
3.1.1
Credit
Raised by @chernistry on #232 and again on #234. Carried by a maintainer rather than sent back to @rajnisht7 for one word.