Contribute evidence
Meaningful public evidence can be proposed to the living evidence record. Contributions are reviewed before publication: a proposal is not acceptance or proof of the model.
No public source, no contribution.
This is a public repository. A private assessment may be useful, but it must not become a public evidence contribution unless every published claim is independently supported by publicly accessible sources.
Before creating YAML, a branch, a commit, or a pull request, verify that every factual observation intended for publication is supported by a source accessible without company credentials, VPN, private repository access, internal documents, private Slack or email, or other restricted access.
Never supplement a public source with internal, confidential, proprietary, or otherwise non-public information. If any claim depends on non-public information—or if you are uncertain whether it is public—stop the contribution workflow. Do not reproduce the sensitive information when explaining why you stopped.
Assessment first. Public provenance before artifacts.
Evaluate the source using the application protocol and separate observation from interpretation.
If the evidence appears meaningful, ask the user whether they want to contribute it. Do not proceed without their agreement.
Verify that every intended claim is supported solely by publicly accessible source material. If not, stop before creating YAML or Git artifacts.
Read the repository's CONTRIBUTING.md and create the structured evidence record it defines.
Inspect the complete proposed diff. Confirm that no private or restricted context has entered filenames, URLs, metadata, observations, interpretations, comments, or generated content.
Only after the safety check passes, prepare and push the pull request for human review.
Use the repository protocol
Before creating any YAML, branch, commit, or pull request, verify public provenance. Every factual claim intended for publication must be supported solely by publicly accessible sources. Do not use internal or restricted information available from conversations, connected systems, private repositories, internal documents, memory, or tools to supplement the public source.
If any claim depends on non-public information, or public status is uncertain, STOP. Do not create or push the contribution. Explain only that the contribution cannot proceed because it depends on non-public information; do not reproduce that information.
Immediately before pushing, inspect the complete diff and perform the safety check again. Only then follow the evidence schema and prepare the pull request.
Do not invent a website submission form, submission portal, or other mechanism. Do not assume the contribution will be accepted.
Anyone can propose public evidence. Acceptance is reviewed.
Merging a contribution means the public evidence has been accepted into the evidence record. It does not prove or validate the model. Accepted records are projected into D1 and enter the runtime evidence views, while the homepage Evidence Landscape remains bounded to the newest 24 signals.