Universities, colleges & public-interest research
Turn a bounded research question into work that another person can check. Faculty, students, centers, extension programs, and campus teams can propose source verification, dataset review, and public-facing research translation without surrendering authorship or bypassing editorial review.
Start with a question, not a promised result
A useful project may compare the wording of a public agreement with the records available to evaluate it, document where a regional dataset changes definitions, or identify the evidence needed to test a workforce claim. These are examples of possible work, not active projects or institutional commitments.
Describe the question, study geography, date range, intended sources, methods, available supervision, and limits of the proposed work. A capstone proposal should distinguish a student exercise from a completed research finding. Do not promise access to restricted data or participation by a community that has not agreed.
Keep research and community authority visible
Use the research exchange to submit a proposal or methods note. Name the source issuer and the contributors’ roles. Explain whether the work uses public records, analysis, interviews, or attributable local context; those evidence classes are not interchangeable.
Community-engaged work should identify who defined the question, how participants can review their attributed material, and what consent limits apply. Compute Equity intake is not an ethics review, research approval, or a substitute for the institution’s own requirements.
Make a reusable contribution
A source inventory, reproducible cleaning notes, a data dictionary, or a plain-language methods explanation can be useful even when the original question remains unresolved. Submit the stable source URL or an authorized file reference, state reuse rights, and flag gaps rather than filling them with assumptions.
After review, an approved organization can associate work with an existing Regional Intelligence record and propose a collection of reviewed public resources. This does not modify the separate Atlas or publish a Team_Compute article.
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.