# Activity tag conventions

Every development activity carries exactly one composite framework tag, named at
the point of use. The tag combines the 70/20/10 channel with the practice type,
so the reader sees both where the activity sits and what kind of activity it is.

## Format

`Channel, practice type`

Where:

- **Channel** is one of: `On the job`, `Social learning`, `Formal learning`
  (the 70 / 20 / 10 bands, in words).
- **Practice type** is one of: `deliberate practice`, `behavioral experiment`,
  `reflection`, `stretch assignment`, `coaching`, `mentoring`, `peer feedback`,
  `shadowing`, `applied learning`.

## Examples

- `On the job, behavioral experiment`
- `On the job, deliberate practice`
- `On the job, stretch assignment`
- `Social learning, coaching`
- `Social learning, peer feedback`
- `Formal learning, applied learning`

## Rules

1. One tag per activity. Do not stack multiple tags.
2. The channel must be consistent with the practice type. `Formal learning,
   stretch assignment` is incoherent. A stretch assignment is `On the job`.
3. Prefer `On the job` activities. Each priority leads with at least one.
4. The tag is rendered as a short label run, visually distinct (muted, in the
   booklet's Heading 4 style or as a leading bold label), immediately before or
   above the activity text. The content builder emits it as the bold label in an
   `emphasis_list` item so it reads as "Channel, practice type: activity text".
