Repository navigation
Clarify scientific decisions, exploratory mode and public API boundaries - #48
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.
Clarify how implementation agents handle scientific uncertainty and API design. The prompt defaults to confirmation before implementing unresolved choices that materially change the algorithm, while allowing documented routine defaults and continued independent work.
An unchecked exploratory-mode checkbox permits explicitly requested provisional design choices, recorded for review before a faithful-reproduction claim. Leakage, label access, cohort/target definitions, evaluation validity and existing execution approvals remain blocking in both modes. The generated guide, agent instructions and implementation report carry the same decision policy.
Keep the algorithm/configuration classes importable and the public API intentional. Implementation-only helpers use single-leading-underscore names, stay out of package re-exports and all, and preserve required public contract methods/hooks. Explain that Python underscores are conventions rather than access controls, and reserve name mangling for actual inheritance collisions.
Validation: 9 JavaScript tests cover all 144 input/mode combinations, absent/invalid opt-ins, checkbox defaults, stale output and reset. The full Python template suite, strict docs build, lint and installed-generator packaging checks passed for the policy implementation; the API-guidance follow-up also passes the browser tests and strict docs. This is guidance for coding agents, not a runtime enforcement mechanism.