aitp-assume-theoretically-possible

name	aitp - Assume Theoretically Possible
description	Force the assumption that something is theoretically possible — no physical, logical, or mathematical barrier prevents it. Trace what engineering, resource, or practical barriers remain.
output	{"format":"prose"}

Assume Theoretically Possible

Input: $ARGUMENTS

---

Core Move

Assume: no law of nature, logic, or mathematics prevents this. It is possible in principle. The question shifts from "can it be done?" to "what would it take?"

Separates theoretical possibility from practical feasibility.

---

Procedure

Step 1: State the Claim

What is being assumed theoretically possible?

Step 2: Force the Assumption

"No fundamental barrier exists. Physics, logic, and math allow this."

Step 3: Trace Implications

If theoretically possible:

1. What's the gap between theory and practice? — What engineering, resource, or knowledge barriers remain?
2. What would a proof of concept look like? — Smallest demonstration that it works in principle.
3. What's the timeline? — If possible, when could it realistically be achieved? 1 year? 10? 100? Never practical?
4. What enabling technologies are needed? — What doesn't exist yet but could?
5. Who is closest? — What research group, company, or field is nearest to achieving this?
6. What becomes possible downstream? — If this is achieved, what else unlocks?

Step 4: Test the Assumption

• Is there actually a theoretical proof of possibility?
• Or just absence of a known impossibility proof?
• Are there information-theoretic limits? Thermodynamic limits?
• Has anyone claimed to prove impossibility? Were they right?

Step 5: Synthesize

CLAIM: [stated]
ASSUMING THEORETICALLY POSSIBLE:
  Theory-practice gap: [what remains]
  Proof of concept: [smallest demo]
  Timeline estimate: [when practical]
  Enabling needs: [what's missing]
  Downstream unlocks: [what else becomes possible]
THEORETICAL POSSIBILITY CONFIDENCE: [high/medium/low]
NEXT MOVE: [pursue proof of concept / identify limiting barrier]

---

When to Use

• Evaluating futuristic or ambitious proposals
• Separating "impossible" from "really hard"
• Planning long-term R&D

Integration

• Pair with /ati for the opposite stance
• Follow with /de to plan practical implementation