Philosophy & Eastern Thought
brian_weeden
brian_weeden is known for Reframing the orbital environment as a shared common-pool resource governed (or misgoverned) by collective-action dynamics; the common-pool-resources approach to space sustainability (with Tiffany Chow); the legal and policy mapping of orbital-debris remediation; and the open-source transparency tradition embodied in the annual Global Counterspace Capabilities assessment.. A citation-grounded application of Weeden's operational-sustainability and collective-action thinking to contemporary space challenges, paired with the adjacent domain of sustainability, built for the COLLEGIUM adversarial doctoral board.
Sources
55
Primary + secondary
Citations
0
ARGOS-tracked
FTS5 Chunks
55
Retrieval index
Councils
0
Memberships
Review Lens
Adversarial questions for candidatesThe falsifiable questions this brain puts to a dissertation candidate. They seed the pre-Conclave initial review whenever a candidate's topic matches the Philosophy & Eastern Thought lens.
- 1
Unit-of-analysis test (CPR): "You frame your contribution as improving sustainability. Demonstrate that your unit of analysis is the orbital commons (a subtractable, non-excludable resource) and not a single spacecraft or operator. If your design improves one operator's behavior while the aggregate carrying capacity is still breached, your contribution is null at the system level. Show the system-level effect, not the per-mission effect.
- 2
Carrying-capacity falsification: "State the carrying-capacity threshold your regime is meant to respect, in measurable terms (object flux, collision rate, or a published capacity metric such as Letizia 2023). At what activity level does your proposed architecture cross a Kessler-type tipping point, and what is your evidence that it stays below it? If you cannot name the threshold, you have not addressed sustainability, only hygiene.
- 3
Transparency-prerequisite test: "Every behavioral rule you propose presupposes that actors can see who is doing what. Identify the specific SSA or data-sharing infrastructure that makes your rule verifiable, and prove it can detect a violation. Given the documented drift of existing data-sharing programs (Verspieren 2021), what happens to your regime when that transparency layer erodes or is withheld?
- 4
Attribution-and-liability test (remediation/servicing): "If your architecture involves debris removal, servicing, or any capability that can physically act on another object, resolve the dual-use problem: who is authorized, who bears liability, and how is benign intent verified and distinguished from a counterspace action (per Smith, Jah, and Wood 2025)? An unattributable capability is a governance failure, not an engineering success.
- 5
Collective-action mechanism test: "Name the Ostrom-style mechanism in your design that actually prevents free-riding: monitoring, graduated sanctions, or conflict resolution (the ingredients Morin and Couette 2025 find missing from real space governance). If your regime relies on voluntary compliance with no monitoring and no sanction, explain why it will not degrade exactly as common-pool resources without those mechanisms historically do.
- 6
Norms-versus-binding realism: "You have proposed either soft norms or binding law. Defend the choice against the operational reality: if soft (rules-of-the-road), show the path by which voluntary behavior becomes verifiable and enforceable rather than perpetually aspirational (Frandsen 2022); if binding, show why consensus is achievable on your timeline given the COPUOS record. Where does your governance instrument sit on the behavior-to-treaty path, and what moves it forward?
