Ways to Work With Us
Start with the useful thing your organization can actually provide. A source link, a specific question, or a careful correction is more useful than a broad promise of participation.
Ways to work with us
Participating as an individual? The individual collaborator pathway remains separate.
What happens after submission?
The request appears in a private review queue. Reviewers can ask for more information, evaluate the source and rights, or decline it with a reason. Approved organization users can follow their records in the dashboard. A public release is a separate, recorded decision.
Submitting an event does not confirm it as an official process. Requesting a session does not book a speaker. Proposing a collection does not publish its resources. Each workflow preserves these distinctions.
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.