Add fictional commitment challenge set for partner discovery - #1
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.
Add a small fictional challenge set to test the commitment abstraction before generating training data. Eight cards cover rejected deliveries, cancellation, resource contention, late evidence, intervention after a forecast, disputed meaning, routine fulfilment, and work that may not fit a bounded commitment.
Each card separates decision-time knowledge from later observations and keeps unresolved interpretations explicit. A contract-question map, reusable case template, and partner discovery guide help practitioners introduce their own distinctions before seeing the project's examples. The README and initial work plan link to the material.
These are discussion scenarios, not labelled training examples or partner findings. The
0.1.0schema, validator, and executable fixture are unchanged.Validation: checked local documentation links, balanced disclosure blocks, eight fictional case declarations, and
git diff --check. No runtime behaviour changed.