Repository navigation
Simplify documentation and make format boundaries explicit - #5
Merged
Merged
Conversation
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.
Current and historical guidance had drifted: readers could confuse package versions, Core semantics, local runtime envelopes or outdated development instructions.
This change simplifies the maintained entry points and states this component's actual role, format and verification scope. Updated files:
CONTRIBUTING.mdNOTICE.mdProtocol definitions stay in jep-core; organization-wide navigation stays in .github/PROJECTS.md. Published protocol snapshots, original research bodies, signed archives, package identifiers and executable behavior are preserved.
Validation: relative documentation links and Markdown fences checked; git diff --check clean. Core frozen-publication hash check passes. This is documentation only and does not create a package release. Existing repository CI is allowed to complete before merge.