Contributions are welcome when their boundary is explicit. Lore Plugin separates product behavior, product evidence and LUS research so that a useful observation does not silently become a universal claim.
- Bugs, documentation and product changes: open an issue or a pull request.
- Cases and refutations: use GitHub Discussions and state the context, what happened, the claimed boundary and what would disprove the reading.
- Ideas and questions: begin in Discussions when no concrete patch exists yet.
- LUS research: identify the relevant hypothesis and distinguish observation, interpretation and evidence. A Discussion or product case is not admitted to the scientific corpus automatically.
Do not include private Lore, credentials, passphrases or third-party material you cannot publish.
- Keep the change as small as the claim permits.
- Update English and Spanish documents together when the same public statement appears in both.
- Preserve declared evidence boundaries; do not upgrade cases into proofs or hypotheses into product promises.
- Run
npm testand check every relative Markdown link you changed. - Describe what changed, why, and what was intentionally left outside scope.
Documentation-only changes ordinarily need no version bump. Tags and GitHub Releases are created only when maintainers deliberately cut a product release; historical release records are not rewritten to absorb later documentation edits.
By participating, you agree to the Code of Conduct.