Conversation
This was referenced Sep 22, 2026
Owner
carlok
added a commit
that referenced
this pull request
Sep 22, 2026
…ns-doc docs: add contribution directions and PR cadence (from #196)
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.
Summary
Adds
docs/CONTRIBUTION-DIRECTIONS.mdas a non-normative roadmap for building more connected, reusable mathematics across the LeanFrontier corpus.This is the upstreamed and refreshed version of the contribution-directions dossier discussed in #186.
What changed
docs/, as requested in Upstreaming the contribution-directions dossier, and build errors in receiver reports #186;main;LeanFrontier.Geometry.FordCircleTangencyas accepted infrastructure, so the Ford–Farey–Descartes direction is now immediately actionable;LeanFrontier.MarkovTree.jump_descends_ordered_positiveas accepted infrastructure and updates the Markov/Farey direction around the remaining tree/path representation gap;reflectoperations;Scope
This is documentation only. It does not modify the submission contract, receiver, policy, workflows, or mathematical source.
The document explicitly states that
CONTRACT.mdand the live submitter guidance remain authoritative, and that contributor-specific branch state / PR queues should not be encoded in the shared roadmap.Closes the contribution-directions part of #186.