> 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-v-non-finite-forms-and-verbal-periphrases/35-the-participle-active-vs-passive.md).

# 35. The Past Participle: Agreement vs. Compound Invariance

> *When participles must agree in gender/number and when they stay frozen in -o.*

***

## The Dual Life of the Participle

Past participles end in **-ado** (-AR verbs) or **-ido** (-ER/-IR verbs):

* *hablar → hablado* (spoken)
* *comer → comido* (eaten)

### Rule 1: With HABER in Compound Tenses → 100% INVARIABLE!

When used in compound tenses (*he hablado, habíamos comido*), the participle **never changes**. It stays frozen in the masculine singular **-o**, regardless of whether the subject is a woman, a man, or a group:

* *«Ellas han **comido** pizza.»* (They \[females] have eaten pizza — NOT \*«*comidas»*!).

### Rule 2: As an Adjective with ESTAR or Nouns → MUST AGREE!

When the participle functions as a descriptive adjective, it must agree in gender and number:

* *«La puerta está **cerrada**.»* (The door is closed — feminine singular).
* *«Los libros están **abiertos**.»* (The books are open — masculine plural).


---

# 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-v-non-finite-forms-and-verbal-periphrases/35-the-participle-active-vs-passive.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.
