# How these SOPs work

This page sets out how the SOPs at attention.jonashw.dev are written, versioned, changed and followed.

## One owner

One maintainer owns the SOPs and the research behind them. Anyone may read and follow them, people and agents alike. Followers do not edit them; they send change requests.

## Status line

Every SOP opens with one line:

> Version N, adopted YYYY-MM-DD. Proven on n cases.

A draft says so instead: "Version 1, draft. Tried on n cases." A draft is not listed as adopted until it has been tried on real work.

## Versions and the changelog

- A wording fix or a clarification edits the current version and adds a changelog line.
- A change to what the reader does ships as a new version. The SOP's page always shows the current version. The previous version stays readable at `<sop>-v<N>.md`, linked from the current page.
- Every change gets a dated entry in the [changelog](https://attention.jonashw.dev/changelog.md).

## Evidence levels

Each research claim in an SOP carries one tag and a linked source.

| Level | Means |
|-------|-------|
| **Strong** | Replicated findings or a meta-analysis. |
| **Some** | A few studies, small samples or mixed results. |
| **Practice** | Expert or community practice, not tested in studies. |
| **Field** | Observed in the maintainer's own work, with the date. |

Where nothing is known, the SOP says "unknown". Research summaries say what studies found and how strong the evidence is. Questions about diagnosis or medication belong with a clinician.

## Change requests

When a follower finds a gap or a case an SOP doesn't fit, it sends this request to the maintainer. Agents write it as plain text in a code block for a person to carry over.

```
Change request for attention.jonashw.dev
SOP or topic: <name and version>
From project and thread: <name, link>
What happened: <the case, in the person's exact words>
Proposed change: <concrete wording>
Urgency: <blocking now | when convenient>
```

The maintainer replies with the outcome: adopted (with the new version), adapted, or declined with the reason.

## Choosing between options

When an SOP change means choosing between options, the requirements are confirmed first, and the choice follows the [Alternatives Analysis Specification](https://alternatives.jonashw.dev/software.md).

## Field notes

When the maintainer corrects, approves or sets a rule for this work, the exact words are recorded with the date in `docs/field-notes/` in the source repository. Field notes are the raw record that the Field evidence level cites.
