Tribal institutions & institution-controlled participation
Participation begins with the institution’s own priorities and authority. A public-interest research platform does not decide who speaks for a Tribal community, which information should be shared, or what consent can be assumed.
Define authority and scope before sharing
An application should identify the participating institution, the authorized contact, the intended contribution, and the geographic and subject boundaries of the work. An individual affiliation is not by itself authority to represent an institution or community.
Specify what is already public, who authorized its use, and whether interpretation or republication requires further review. Do not submit culturally sensitive, restricted, personal, or institution-controlled information through this public-record workflow. A file reference is not permission for the platform to obtain or publish its contents.
Preserve context and disagreements
A contribution may identify an official public statement, point to a source record, correct a geographic description, or explain why a conventional metric does not address the question the institution is asking. These are examples, not a presumption that any institution is participating.
Describe the source, date, attributed speaker or issuer, and limits. Do not present one submission as community consensus, treat a missing public record as absence of a concern, or extend a record beyond the authority that issued it.
Control public identification separately
An approved private organization record can support a scoped contribution workflow without a public directory listing. Public identification requires affirmative approval and a public-profile consent check. No outreach target is automatically turned into a profile.
A pause or revocation removes the organization and its dependent resources from public institutional views. Use the correction pathway to flag an attribution or context problem. The review team must evaluate a correction before publishing a changed public claim.
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.