01
Support pursuing it
The respondent supports pursuing the mission substantially as framed, while still being free to question implementation details.
Consequential missions attract disagreement because they involve tradeoffs: cost, risk, timing, safety, equity, feasibility, alternatives, and what should be prioritized first. Assemble Teams exists to help capable people understand and assemble around missions—not to tell them which missions they must support.
When community perspectives are eventually enabled for a specific mission or proposition, a person’s response belongs only to that mission. It is not a permanent identity or worldview assigned to that person.
The respondent supports pursuing the mission substantially as framed, while still being free to question implementation details.
The respondent may support the mission if safeguards, evidence, governance, design changes, costs, or other conditions are addressed.
The respondent does not support the mission as framed and favors a materially different method, priority, or allocation of effort.
Mission perspectives are never inferred from browsing behavior, occupation, employer, location, social accounts, demographics, or prior discussions. People may change or remove their response. Individual positions are private by default unless a person explicitly chooses otherwise.
Claims directly supported by named primary sources, standards bodies, peer-reviewed research, or other high-quality evidence appropriate to the subject.
Where credible people or institutions interpret the same evidence differently, we attribute the disagreement rather than silently choosing a side.
Our synthesis—such as identifying an overlooked workforce or coordination bottleneck—is labeled as analysis, not presented as a sourced statistic or community consensus.
Missing evidence, unresolved engineering constraints, policy choices, costs, uncertainties, or facts that would materially change the debate.
Only real, self-selected responses from eligible participants, shown as a descriptive snapshot under published methodology and integrity controls.
A large amount of agreement may tell us that a community sees a problem or approach similarly. That can help mission owners understand social support, concerns, or conditions. It cannot prove that the majority is technically correct, ethically correct, or likely to succeed.
Illustration only—not live community data. Public percentage bars will not appear until a mission has at least 25 eligible responses and integrity controls can exclude duplicate, automated, or manipulated participation. Any future snapshot will show its response count and “as of” date. Consensus is descriptive, not an endorsement, prediction, verification signal, or measure of truth.
A lunar infrastructure proposal might turn on scientific value, cost, geopolitical resilience, environmental safeguards, and alternative exploration strategies. A clinical AI mission might turn on patient outcomes, validation, privacy, clinician authority, access, and failure modes. Energy infrastructure might turn on reliability, affordability, land use, timelines, emissions, supply chains, or local consent.
The platform should help people see those tradeoffs clearly enough to make their own judgment—and, when they choose, find others capable of doing the work.
Browse current Intelligence for sourced analysis, or explore public people, organizations, and missions in GameChangers. Presence in the directory is not an endorsement by Assemble Teams.