# Action Schema

> **Title requirement**
> Every Action Item table must begin with a single-line PascalCase title
> followed by ` — vX.Y` (X = major, Y = minor; X may be **0** for pre-implementation drafts).
>
> * The LLM is solely responsible for the accuracy and version updates of the table.
> * Since LLMs can make mistakes, the version number is for general approximation and does not guarantee precision. Users should verify critical details manually.
>
> If the `GOALS.md` template is used, Action Items may reference or be generated from entries defined in the goal hierarchy.
>
> If the `DEPENDENCY_MODELING.md` template is used, Action Items may reference or align with component dependencies or use cases described therein.

---

### Example Title:

```
MyActionList — v0.1
```

### Example Action Item Table:

```
| Tag  | # | Task                 | Status      | Next action / note       | Test-cases / validation checks |
|------|---|----------------------|-------------|--------------------------|-------------------------------|
| feat | 1 | Example new task     | Not started | Draft proposal spec      | Link to proposal spec draft   |
```

---

### Column Descriptions

| Column                             | Description                                                                             |
| ---------------------------------- | --------------------------------------------------------------------------------------- |
| **Tag**                            | Conventional-commit tag (`feat`, `fix`, `docs`, `meta`, etc.).                          |
| **#**                              | Sequential number; optional items may use letters (A, B, C…).                           |
| **Task**                           | One-sentence description of the Action Item.                                            |
| **Status**                         | One of: **Not started**, **In progress ⏳**, **Done ✅**, **Pending**, or **Optional**.   |
| **Next action / note**             | Concise phrase (≤ 20 words) stating the immediate next step or context.                 |
| **Test-cases / validation checks** | One or more checks proving completion, separated by commas; use “—” only if impossible. |

---

### Formatting & Content Rules

1. **Title line** (PascalCase + `— vX.Y`) always precedes the table.
2. Task descriptions must be ≤ 1 short sentence.
3. Number tasks starting at 1; optional tasks may be lettered (A, B, C...) after numbered tasks.
4. **Status** must strictly adhere to the five allowed values.
5. Keep **Next action / note** concise (≤ 20 words).
6. **Every Action Item must include at least one Test-case / validation check**; use “—” only if truly unavailable.
7. **Tag** must be selected from the defined conventional-commit set.
8. Each Action Schema is an immutable, **versionable artifact**; never overwrite prior versions—always create a new schema via Rotation.
9. Action Items may reference goals, tests, or concepts defined in `GOALS.md` or `DEPENDENCY_MODELING.md`, if present. However, the Action Schema must remain independently usable and complete without relying on those files.
10. Action Schema content generated by an LLM should be considered an approximation and verified manually for critical accuracy.
