Contribute Evidence, Data or Local Context
Make the record checkable before asking others to rely on it. Sign in, choose an approved organization or your approved individual collaborator account, and submit the source with its date, geography, evidence class, and limitations.
Prepare the source and its boundaries
Include the title, issuer, public source URL or authorized file reference, publication or effective date when known, geography, topic, why it matters, limitations, and relevant interests. An unknown date stays unknown. Do not submit private personal data, credentials, restricted records, or material you do not have the right to share.
A file reference is a reference only, not an upload. It remains private and cannot become a public resource without an accessible public source URL. No submitted URL is automatically fetched by this workflow.
Submission is not publication
Save a complete contribution as a draft or send it for review. A reviewer may ask for more information; the original submitter can then revise and resubmit, with earlier versions retained in the private audit history.
Evidence class and evidence status remain separate from review state. Approval for a source record does not publish a Team_Compute article or change Atlas. Public release requires an additional rights, provenance, and redaction check.
What approval does and does not mean
Participation is not endorsement of this project, any organization, or data-center development. Institutions may submit evidence and context, but they cannot execute or publish Team_Compute articles. Article publishing remains owner-only.
Applications, source submissions, regional associations, events, and resource collections have separate review states. A received request is not an approved relationship. An approved workflow state is not a measure of evidence quality. Public material retains its issuer, date, geography, limitations, review context, and a correction route.