Skip to content

Clarify scientific decisions, exploratory mode and public API boundaries - #48

Merged
florian6973 merged 2 commits into
mainfrom
codex/scientific-ambiguity-policy
Nov 7, 2026
Merged

florian6973 merged 2 commits into
mainfrom
codex/scientific-ambiguity-policy

Conversation

@florian6973

@florian6973 florian6973 commented Nov 7, 2026 •

Copy link
Copy Markdown
Collaborator

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.

@florian6973 florian6973 changed the title Add scientific ambiguity confirmation and opt-in exploratory mode Clarify scientific decisions, exploratory mode and public API boundaries Nov 7, 2026
@florian6973
florian6973 merged commit 9fbfea4 into main Nov 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant