Refresh context for the Root Sequence router role - #25
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
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.
Why this is needed
Merged PR #24 changes Root Sequence’s current working model from a broad project “about connections” to a transdisciplinary router + synthesis + build role. It also replaces
site/index.htmlwith a new router-role review candidate while deliberately leaving the September 18 approval record unchanged.Proposed edits
START-HERE.mdso the concise orientation names the router role and distinguishes the current website candidate from the last approved edition;PROJECT-CONTEXT.mdto route readers to the canonical Research Method / Method & Concept Router and record the blocked publication state;site/README.mdthat still called the current candidate and digest “approved.”The edits preserve PR #24’s boundaries: the method does not replace native disciplines, different mechanisms are not treated as identical, the revised site is not approved or released, and its full validation remains outstanding.
The top-level
README.mdlink toSTART-HERE.mdis present and working, so it is unchanged.