Repository navigation
Rewrite the specification as a formal draft - #3
Merged
Merged
Conversation
joostfarla
force-pushed
the
formal-draft
branch
from
October 22, 2026 13:56
22cd943 to
26d8339
Compare
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
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.
This replaces SPECIFICATION.md with a Bikeshed draft in v1/ that states the format as Spectral and OpenLint behave today, as identified requirements with conformance tests.
What it adds:
$idand property tables generated from it.AI use: Claude Code produced the first draft, fixtures and tools; the rest is my editing, verification and restructuring.