> 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-xvi-the-40-sentence-assessment-arena/82-practice-arena-overview-and-rubric.md).

# 82. Practice Arena Overview & Study Rubric

> **How to Test Yourself Using GitBook's Collapsible Solution Cards**

Welcome to the ultimate proving grounds of the Spanish Codex!

Reading grammar rules is passive; testing yourself with active recall is where neural connections actually form. This arena contains **40 carefully calibrated challenge sentences** spanning every level of the Common European Framework of Reference for Languages (CEFR):

* 🟢 **Tier 1 (Sentences 1–10):** Level A1–A2 (Foundations, Articles, Ser/Estar basics, Direct Objects, Simple Present).
* 🟡 **Tier 2 (Sentences 11–20):** Level B1 (Preterite vs. Imperfect, Por vs. Para, Gustar-like verbs, Object Clitic combinations).
* 🟠 **Tier 3 (Sentences 21–30):** Level B2 (Subjunctive triggers, The 8 Faces of SE, Commands with clitics, Conditionals).
* 🔴 **Tier 4 (Sentences 31–40):** Level C1–C2 (Advanced Subjunctive sequences, Accidental clitics, Literary backshifting, Inverted syntax).

***

## 🕹️ How GitBook Solution Cards Work

Each sentence is presented as a fill-in-the-blank puzzle with 4 options (A, B, C, D).

The answer and detailed linguistic explanation are hidden inside a GitBook collapsible `<details>` card:

```markdown
<details>
<summary><b>🔍 Reveal Answer & Step-by-Step Breakdown</b></summary>
...explanation here...
</details>
```

> \[!IMPORTANT] **Honest Self-Study Rule:** Do NOT click the dropdown card until you have written down your answer and your reason for choosing it on a piece of paper or in your text editor!


---

# 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-xvi-the-40-sentence-assessment-arena/82-practice-arena-overview-and-rubric.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.
