README: keep the integration contracts task-general - #11
Merged
Conversation
…xample Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Follow-up to #9/#10: the "How to plug SPINE into your ML code" section described the contracts in CURTAIN's vocabulary. Now the general rule comes first and CURTAIN is the named example: tasks (not "the sampler") decide and build targets in detector units; the geometry asset universally needs xyz plus the key array, with
knn_idxintroduced as CURTAIN's additional requirement; selections must satisfy the task's own predicate, withcan_always_splitas CURTAIN's instance.This re-lands the generalization that was pushed to the #9 branch moments after it was merged and therefore never made it into main.
🤖 Generated with Claude Code