Seven-Action schema

Built-in id: passo-uno:seven-action:1.0

Published at: https://hawkeyexl.github.io/manni/schemas/seven-action/1.0.json

Constrains action to the seven reader actions. Derived from upstream model version 2025-01-09.

It is one of the taxonomy schemas. Where Diátaxis and TGDP classify what a page is, the Seven-Action Documentation Model classifies what a reader is doing. It claims a different key, so it composes with either.

Use it

This schema is in the default set, right after OKF. It can be, because it constrains a key that documents do not otherwise carry and does not require it. So it fails nothing that passed before.

A run with no -s, no in-file $schema and no config override already applies it. A schemas: list in config adds to the default set, so it stays. A config that sets defaults: false, or an override without defaults: true, replaces the default set. Name it there to keep it:

manni.config.yaml

meta:
  defaults: false
  schemas:
    - diataxis:diataxis:1.0
    - passo-uno:seven-action:1.0

Fields

Field	Type	Required	Values
action	string	No	appraise, understand, explore, practice, remember, develop, troubleshoot

Value	Alternate verb	What the reader is doing
appraise	Discern	Judging whether something fits their situation
understand	Learn	Grasping a concept
explore	Discover	Finding out what exists
practice	Train	Building a skill by doing
remember	Recall	Looking up a detail they once knew
develop	Integrate	Building the thing into their own work
troubleshoot	Solve	Getting past a problem

Only the left column validates. The alternate verbs are how the model names each action in prose; action: learn fails.

Additional properties

Allowed. The schema says nothing about any key but action.

Example

---
action: practice
title: Work through the tutorial
---

A common mistake

Writing the alternate verb instead of the value is the usual failure:

✗ docs/tutorial.md
    /action  must be equal to one of the allowed values  (line 2)  [passo-uno:seven-action:1.0]

If you already use an `action` key

action is a generic field name. If your frontmatter already uses it for something else (a workflow name, a button label), two things change:

• validate fails. Your value is not in the vocabulary, so it is reported as an error against passo-uno:seven-action:1.0.
• fill overwrites it. A key whose value is invalid is a candidate for replacement, not just for filling a gap, and manni meta fill writes to disk unless you pass --dry-run. Run manni meta fill --dry-run first on any repo that uses action for something of its own.

Set defaults: false and a schemas: list without Seven-Action in manni.config.yaml before running either command. The list then replaces the default set, which opts you out of both.

The taxonomy schemas overview maps each action to a Diátaxis type.