> For the complete documentation index, see [llms.txt](https://sp.jerrygems.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sp.jerrygems.tech/volume-vi-the-subjunctive-realm-el-subjuntivo/41-adverbial-clauses-escapa-vs-chad-ate.md).

# 41. Adverbial Clauses: ESCAPA vs. CHAD ATE

> *Conjunctions that unconditionally demand the subjunctive vs. those that shift with time.*

***

## 1. The ESCAPA Conjunctions (100% Invariable Subjunctive)

These 6 conjunctions always command the Subjunctive regardless of tense:

* **E — En caso de que:** *En caso de que llueva...* (In case it rains...)
* **S — Sin que:** *Sin que nadie lo note...* (Without anyone noticing...)
* **C — Con tal de que:** *Con tal de que me ayudes...* (Provided you help me...)
* **A — Antes de que:** *Antes de que termine el día...* (Before the day ends...)
* **P — Para que:** *Para que aprendas...* (So that you learn...)
* **A — A menos que:** *A menos que tengamos tiempo...* (Unless we have time...)

## 2. The CHAD ATE Conjunctions (Future = Subjunctive | Habitual = Indicative)

Conjunctions like *Cuando* (when), *Hasta que* (until), *Aunque* (even if/although), *Después de que* (after), *En cuanto / Tan pronto como* (as soon as):

* **If referring to an unfulfilled FUTURE action → SUBJUNCTIVE:**
  * *«Te llamaré cuando **llegue** a casa.»* (I will call you when I arrive home — in the future!).
* **If referring to a habitual or past FACT → INDICATIVE:**
  * *«Siempre te llamo cuando **llego** a casa.»* (I always call you when I arrive home — routine fact!).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://sp.jerrygems.tech/volume-vi-the-subjunctive-realm-el-subjuntivo/41-adverbial-clauses-escapa-vs-chad-ate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
