docs: publish reactor spec reconciliation#99
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.
Summary
Fold the public OpenProse/Reactor spec into
openprose/proseunderspec/for the v0.1.0 release.This PR:
00-Tenets.mdunchanged as the public tenet anchor01-Language,02-ReactorHarness,03-ReactorPattern, and04-Evalswith Ideal / Current / Roadmap separationreactor-v0.1.0state46:46vs92:0/92:0, not the stale256:004-EvalsRequired Evaluation Suite out of the frozen Ideal section and into RoadmapValidation
git diff --checkrg '0\\.1\\.0-rc|5cfbac8|153 tests|281 tests|256:0|not yet published|technical report has not' spec→ no hits for stale release/status contentrg --pcre2 '\\[[^\\]]+\\]\\((?!https?://|#|\\./)[^)]+\\)' spec→ no private relative linksThis is docs-only and follows the release handoff Step E spec reconciliation item.