# Frames as dict classification

**🟢 Beginner · Lesson 25**

Spellframes are CATEGORIES. Organize one world's spells by the resolution ideas your app already has - "repositories", "notifiers" - and (category, name) becomes the full address. The addressing FEELS like a two-level dict, but frames are NOT dicts: they are grouping and contract keys. A string frame groups; a Protocol frame also VALIDATES what binds under it (intermediate tier). Seed for later: when a category needs its own OWNER and its own resolution conditions, the category graduates into a whole CONDUIT - that story is intermediate lesson 26.

## Before you run

Use the [Beginner guide](../../beginner/index.md) for prerequisite concepts. Run from a checkout with Melder installed and Python 3.14 free-threading selected. The collection download includes the level's local helper modules.

## Run the saved script

```bash
python UX_and_AIX_experiences/01_beginner/25_frames_as_dict_classification.py
```

```powershell
py -3.14t UX_and_AIX_experiences/01_beginner/25_frames_as_dict_classification.py
```

{download}`Download this collection <../../downloads/beginner-examples.zip>` · [Source on GitHub](https://github.com/Synaptic724/melder/blob/1211e838099a342c9dde48f064b1e772b6060e13/UX_and_AIX_experiences/01_beginner/25_frames_as_dict_classification.py)

## Public surface

spellframe + binding_name as a category address space

## Code

```{literalinclude} ../../downloads/01_beginner/25_frames_as_dict_classification.py
:language: python
:linenos:
```

## Check the outcome

The script contains its own assertions or demonstrated refusal paths. Run it to evaluate those checks against your installed version. The code above is taken directly from the saved file; no run output is invented here.

[More beginner examples](index.md) · [Level guide](../../beginner/index.md)

## Related guides

- [Spellframes and categories](../../beginner/spellframes.md)