Repository navigation
Separate learning and lab-development timelines - #9
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.
Summary
Encodes a distinction revealed by the first real orchestration run:
Why
The current Open Learning Lab design/orchestration conversation originated from a Marin-learning branch, but it is not itself Marin learning evidence.
Likewise, CP001's incomplete artifact creation is evidence about orchestration reliability—not learner understanding.
Adds
docs/orchestration.md— routing rules and operating model;Rule
When a conversation is mixed, split the records and cross-link them rather than forcing one artifact to represent both purposes.
Related: #8