@haus-tech/haus-workflow 5.9.1 → 5.10.0

package/library/global/skills/request/SKILL.md

@@ -16,12 +16,14 @@ the respective skill. Only routing, context carrying, the archive and the dispat
 | Task                                | Does                                                                                                                                                   |
 | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `speca <request or gid>`            | Source manifest → dispatch `request-specifier` → archive spec + reviewer block                                                                         |
+| `designa <gid, slug or nr>`         | Gate on `✅ Spec ok` → `superpowers:brainstorming` with the user → the design doc in the repo + `design.md` in the archive; never Asana                |
 | `bedöm <gid, slug or nr>`           | Gate → secure an analysis → dispatch `request-scorer` → archive JSON                                                                                   |
 | `status`                            | Queue state via request-sync, BLUF table with row numbers                                                                                              |
 | `godkänn <nr or gid>`               | Move Offer status forward via request-sync; see the gate section                                                                                       |
 | `underkänn <nr or gid> <reason>`    | Reason as an Asana comment + iteration counter via request-sync                                                                                        |
 | `döm <item>`                        | Human ruling on OLIKA: choose a run, order a rerun or reject the source material                                                                       |
 | `detaljer <gid, slug or nr> [step]` | Print archived JSON/documents for the item                                                                                                             |
+| `byt titel <nr or gid>`             | Rename the Asana task to the spec title (`state.json.title`) via request-sync, on request only                                                         |
 | `utvärdera <item…> <model…>`        | Run the flow once per named model against the experiment area, at least one model; `sammanställ` gives the sweep view, `rapport` a readable comparison |
 | `hjälp`                             | Explain the tasks, touch no files                                                                                                                      |
 
@@ -59,6 +61,10 @@ the respective skill. Only routing, context carrying, the archive and the dispat
   `impact.md` (it is part of the source material for the scoring), but no
   reviewer block may ever be sent along in material that goes to request-sync
   for customer-visible fields.
+- **The design doc never reaches Asana.** `designa` writes nothing via request-sync,
+  and `design.md` is internal source material for the assessor (pasted as the
+  `DESIGN` block); no design content may be sent along in material that goes to
+  request-sync for customer-visible fields.
 - **The archive is a cache, Asana is the truth.** On conflict, the board wins.
 - **Approval is never assumed.** That a spec exists in the archive does not mean it
   has been reviewed. See the gate under `bedöm`.
@@ -93,16 +99,12 @@ section follows it.
 | `spec.md`                                                                                                 | **customer-facing** | the customer's (ADR-0114, unchanged) |
 | `impact.md`                                                                                               | internal            | English                              |
 | `granskarblock.md`                                                                                        | internal            | English                              |
+| `design.md`                                                                                               | internal            | English                              |
 | score JSON: `customer_rationale`, `conditions`, `assumptions_stated`, `alternatives`, `coverage_post.yta` | **customer-facing** | the customer's (unchanged)           |
 | score JSON: evidence, bracketing, drivers, everything else                                                | internal            | English                              |
 | `korning.json`, `state.json`, `matning.json`, `experiment.json`                                           | machine             | unchanged                            |
 | The Asana description's three sections                                                                    | **customer-facing** | the customer's (unchanged)           |
-| Asana subtask `Analys` and its rows                                                                       | internal            | English body text, **Swedish title** |
-
-The subtask titles (`Analys`, `Påverkansanalys vN`, `Poängsättning vN`) stay in
-Swedish. They are lookup keys in Asana, the same class as the field names: `request-sync`
-looks up an existing `Analys` and reuses it, and a rename would split the items into
-before and after without anyone noticing.
+| A split part's subtask: its name and its scope line                                                       | **customer-facing** | the spec's language                  |
 
 Where this skill names a heading or row of the analysis or the reviewer block, it uses
 the English literal the agents write: `## For the reviewer`, _Deviation from the spec_
@@ -142,7 +144,9 @@ new runs.
 Rejected attempts carry an `-avvisad` suffix and stand outside the N count:
 the pricing's `<typ>-pricing-vN-avvisad.json` and the text steps'
 `spec-avvisad-<datum>.md` / `impact-avvisad-<datum>.md` (ADR-0099); see the
-redispatch rule in the dispatch contract.
+redispatch rule in the dispatch contract. A design doc refused on
+`## Spec conflicts` is copied in as `design-avvisad-<datum>.md`: the receipt for
+its stop (`designa` step 5), with no runs row, since the design is no dispatch.
 
 - Directory name: the Asana gid when the item is on the board, otherwise a kebab slug of
   the spec heading. A bundle without a gid: `<slug>-1`, `<slug>-2`, … When a gid is minted later:
@@ -165,7 +169,7 @@ redispatch rule in the dispatch contract.
   "slug": "<kebab-rubrik>",
   "former_slug": null,
   "title": "<spec-rubrik>",
-  "status": "spec_draft | spec_synced | assessed | priced | guard_run",
+  "status": "spec_draft | spec_synced | designed | assessed | priced | guard_run",
   "bundle": { "parent_slug": null, "part": null, "of": null },
   "split": { "parent": null, "part": null, "of": null },
   "approval": null,
@@ -174,6 +178,7 @@ redispatch rule in the dispatch contract.
   "stopp": null,
   "respec_varv": 0,
   "coverage_post": null,
+  "design": null,
   "runs": []
 }
 ```
@@ -181,14 +186,29 @@ redispatch rule in the dispatch contract.
 - `bundle` = specs from the same request (set by speca on a bundle).
   `split` = sub-items from a DELA_UPP outcome (set by bedöm). Both have the form
   `{parent…, part: N, of: M}`. Never both on the same directory.
+  A split part's `split` additionally carries `gid` once its Asana subtask exists:
+  written ONLY by `archive.mjs set-split-gid <del-katalog> --gid <gid>` (ADR-0144),
+  digits only and write-once (the same gid again is a no-op, a different one is refused).
+  `nasta-steg` reads it to say whether the part is synced, and every later sync of the
+  part passes it to request-sync, so the subtask is updated instead of created twice.
+  Absent until the subtask exists. `part` and `of` are integers (JSON numbers, never
+  strings); `nasta-steg` and `bluf` refuse a split whose parts disagree on `of` or carry a
+  non-integer `of`.
 - `stopp` = a stop outcome that the scripts have proven without a scorer:
-  `{ "utfall": "KONCEPT" | "DIAGNOS" | "TILLBAKA_TILL_SPEC" | "ESKALERA", "kalla": "spec.md" | "impact.md" | "granskarblock.md", "date": "YYYY-MM-DD", "orsak"?: string }`.
+  `{ "utfall": "KONCEPT" | "DIAGNOS" | "TILLBAKA_TILL_SPEC" | "ESKALERA", "kalla": "spec.md" | "impact.md" | "granskarblock.md" | "design-avvisad-<datum>.md", "date": "YYYY-MM-DD", "orsak"?: string }`,
+  the last one for a design refused on `## Spec conflicts` (`designa` step 5).
   Written ONLY by `archive.mjs stopp` (which itself checks that the source carries
   what is claimed: the candidate marker in `spec.md`, the label `contradiction` in
-  `impact.md`, the price-decisive open choice in `granskarblock.md`, ADR-0118)
-  and reset ONLY by `archive.mjs respec`. `orsak` is set when `utfall` is
-  `ESKALERA` (the command requires `--orsak` then, so a human sees why the item
-  did not go back to the spec once more) and is absent otherwise.
+  `impact.md`, the price-decisive open choice in `granskarblock.md`, ADR-0118, at
+  least one conflict under `## Spec conflicts` in `design-avvisad-<datum>.md`).
+  `add-design` clears a design-conflict stop (`kalla` `impact.md`, `orsak`
+  `design conflict: …`) and supersedes the analysis it came from (`impact.md` →
+  `impact-superseded-<datum>.md`), or a receipt replaces it (`designa` step 5); every
+  other stop is reset ONLY by `archive.mjs respec`.
+  `orsak` is set when `utfall` is `ESKALERA` (the command requires `--orsak` then,
+  so a human sees why the item did not go back to the spec once more) and for the
+  design sources (the conflicts for `design-avvisad-<datum>.md`, the design conflict
+  text for `impact.md`, see `bedöm` step 3), and is absent otherwise.
   `archive.mjs set-status priced` refuses while the field is set. Older archives
   lack the field and are read as `null`.
 - `respec_varv` is a monotonic counter, raised by 1 by every `archive.mjs respec`
@@ -203,7 +223,23 @@ redispatch rule in the dispatch contract.
   latest pricing file that carries it, the skeleton (`ny-korning`/`ny-del`) sets
   it to `null`. `bluf` shows `täckningspost: <yta>` in the `anm` column when
   the field is set.
-- `approval` is written by the gate in bedöm:
+- `design` is written ONLY by `archive.mjs add-design` and reset ONLY by
+  `archive.mjs respec`: `{ "path": "<absolute path to the canonical file in the repo>",
+ "file": "design.md", "sha256": "<marker-stripped hash of design.md, identical to the canonical file>",
+ "spec_sha256": "<the spec.md hash the design was made against>", "date": "YYYY-MM-DD" }`.
+  The status `designed` sits between approval and `assessed`; `add-design` sets it.
+  `add-design` writes no runs row: `runs[]` records dispatches and the design is not
+  one; the receipt is the field itself, write-once per version (a new design puts the
+  old copy aside as `design-superseded-<datum>.md`). Older archives lack the field
+  and are read as `null`.
+- `umbrella` is written ONLY by `archive.mjs paraply` (ADR-0144):
+  `{ "date": "YYYY-MM-DD", "sha256": "<marker-stripped hash of the umbrella spec.md>" }`,
+  the receipt that the parent's `spec.md` was rewritten one level up after a split.
+  The approved spec it replaced lies beside it as `spec-superseded-<datum>.md`, and the
+  parts keep their inherited copies of it. `paraply` also sets `title` from the umbrella's
+  heading; approval, design, runs, stops and the parts are untouched. The field is absent
+  until `paraply` writes it and is never reset.
+- `approval` is written by the gate in `designa` or `bedöm`:
   `{ "source": "asana" | "manual", "by": "<namn, krävs vid manual>",
  "status_read": "<värde>", "date": "YYYY-MM-DD" }`.
   The note is traceability, never the approval itself.
@@ -253,7 +289,9 @@ redispatch rule in the dispatch contract.
   `node <skillkatalog>/scripts/ref-hash.mjs <referensfil>`, NEVER raw
   `shasum` on the whole file: the installer stamps the files with the package version, so a
   whole-file hash changes value at every haus release and would invalidate
-  all archived runs. The same tool is used for `underlag_sha256`.
+  all archived runs. The same tool is used for `underlag_sha256`. An `impact.md`
+  row additionally carries `design.md` when the directory holds one (`underlagFor`),
+  and precheck `--impact` compares that hash too.
   The reference files lie under the Claude config directory (`CLAUDE_CONFIG_DIR`
   or `~/.claude`). A later guard run compares the hash and refuses to diff on
   skew ("rescoring required, the scale has changed").
@@ -405,7 +443,9 @@ på request-write-spec/references/specformat.md>`. The script sets
    `node <skillkatalog>/scripts/archive.mjs respec <katalog>` BEFORE the new
    spec is written. The command owns the whole invalidation (the analysis is put aside
    as superseded, status, `approval`, `granskarutslag` and `stopp` are reset,
-   `runs[]` is never touched); never write those fields by hand. The reason stands in
+   `runs[]` is never touched, and any `design.md` is put aside as
+   `design-superseded-<datum>.md` with `design` reset the same way); never write
+   those fields by hand. The reason stands in
    the runs contract: a new spec is unreviewed by definition, a ruling against a
    replaced spec is no longer valid, and an old analysis against a new spec is
    exactly the skew the provenance check exists to stop.
@@ -450,12 +490,127 @@ på request-write-spec/references/specformat.md>`. The script sets
    stop nothing.
 7. **Reply BLUF:** one line per spec (heading + any flags), then the reviewer block
    in its entirety. Offer to place the specs on the board via request-sync (🔍); do
-   it only on explicit request. When an item is placed on the board: set status
+   it only on explicit request. Placing a spec on the board is no rename: request-sync
+   renames the task to the spec title by itself only in the three automatic cases
+   (ADR-0144): the task name is empty, `Original request title` is empty, or the task is
+   one of several minted from one source. In the Closing, under the board line,
+   say which case applied: renamed automatically, or the task keeps the customer's
+   title and `byt titel <item>` is the optional next action. When an item is placed on the board: set status
    `spec_synced`, rename the slug directory to the minted gid, note the slug
    in `former_slug` and update `request_id` in `state.json`.
    **Close per `## Closing: where the item stands`** (the table from
    `archive.mjs nasta-steg`, the board line, the ISÄR check), never without.
 
+## Task: `designa`
+
+Runs the design leg: brainstorming with the user against the approved spec, the
+design doc saved in the customer repo and recorded in the archive. Runs in the main
+conversation (the brainstorming skill asks the user questions), in a session whose cwd
+is the customer repo. Nothing here touches Asana: the design is internal source
+material for `bedöm`'s assessor and never reaches the board.
+
+1. **Gate. Identical to `bedöm` step 1.** Read Offer status via request-sync in the
+   main conversation immediately before the run. Only `✅ Spec ok` (normalized on the
+   alphabetic core) lets it through. An item without a gid follows `bedöm`'s rules for
+   that case (refuse when the repo has `.haus-workflow/request.json`, otherwise the
+   explicit "approved by whom" question). An item with a gid but no local archive
+   directory: not supported, say so and stop. Note the passed gate in
+   `state.json.approval` exactly as `bedöm` does; a later `bedöm` rereads the board.
+2. **Form check.** Run `node <skillkatalog>/scripts/precheck.mjs <katalog>`. A
+   `KANDIDAT:` line or a standing `stopp` means the item is not ready for a design,
+   with one exception: a stop from `impact.md` whose `orsak` starts with
+   `design conflict:` (the assessor found the design unbuildable) is exactly what a
+   redesign answers, continue to step 3; `add-design` clears that stop and puts the
+   old analysis aside as `impact-superseded-<datum>.md` when it records the redesign.
+   Any other such line or stop: route it as the stop outcome (see `bedöm`) and stop. A
+   `spec.md` with more than one spec block is a BRIST, as in `bedöm`. Other BRISTER:
+   fix the link that is defective before anything is designed.
+3. **Already designed?** A design-conflict stop let through by step 2 skips this
+   step: redesign, continue to step 4 (keeping an unbuildable design answers nothing).
+   Otherwise, if `state.json.design` is set, run
+   `node <skillkatalog>/scripts/precheck.mjs <katalog> --design`. Three branches:
+   (a) it passes (the hash still matches `design.md` and the canonical file): ask ONE
+   question via AskUserQuestion: keep it, or redesign. Keep: close per step 6 without
+   a new brainstorming. Redesign: continue; `add-design` supersedes the old one
+   (`design-superseded-<datum>.md`), it never overwrites.
+   (b) its only design BRISTER are the hash lines
+   (`design.md: hashen är inte state.design.sha256 …` and/or
+   `design.md: den kanoniska filen … har en annan hash än design.md`), with
+   `request_id`, `spec_sha256` and `## Spec conflicts` still passing: the canonical
+   copy drifted (typically formatted on commit). Rerun
+   `node <skillkatalog>/scripts/archive.mjs add-design <katalog> --file <state.design.path>`
+   (no brainstorming; the old archive copy is put aside as `design-superseded-<datum>.md`),
+   then ask keep/redesign as in (a).
+   (c) any other BRIST: redesign, continue to step 4.
+4. **Brainstorming.** Invoke `superpowers:brainstorming` via the Skill tool. The
+   opening message carries, byte-faithfully: the original request
+   (`## Ursprunglig förfrågan` from the archive or the board), `spec.md`,
+   `granskarblock.md` and `kallmanifest.md` as the source manifest, then the block
+   below verbatim (the id and the hash filled in: the hash comes from
+   `node <skillkatalog>/scripts/ref-hash.mjs <katalog>/spec.md`):
+
+   ```
+   INSTRUKTIONER TILL BRAINSTORMING:
+   - The approved spec is fixed. Questions may refine HOW, never change WHAT the
+     customer gets. A question whose answer would change the spec is recorded under
+     `## Spec conflicts` in the design doc instead of being answered.
+   - Classify as the skill says, but the design doc is written on every path (spike,
+     bounded, architectural). The bounded path's "short design in chat" is written to
+     the file as well.
+   - The doc is written in English (an internal artefact, per the language contract).
+   - The doc starts with the frontmatter (unquoted values) `request_id: <katalogens id>`,
+     `spec_sha256: <hash>` and `date: <YYYY-MM-DD>`, and carries the section
+     `## Spec conflicts` with the single word `none` or one list item per conflict.
+     No size words, no hours, no score talk: the assessor reads the doc and must not
+     inherit a size signal.
+   - Save the doc at `docs/superpowers/specs/<YYYY-MM-DD>-<katalogens id>-<slug>-design.md`
+     in the customer repo.
+   - Stop after the doc is written and self-reviewed. Do not invoke `writing-plans`:
+     the developer does that when the customer orders.
+   - Do not commit. The task stages the file and offers the commit in its closing line.
+   ```
+
+   A brainstorming session that ends without a file records nothing: `state.json` is
+   untouched and `designa` can be rerun.
+
+5. **Record.** Format the doc with the repo's formatter first (`yarn prettier --write <sökväg>`
+   when the repo has prettier, otherwise nothing): a format-on-commit hook must not
+   change the bytes after they are recorded. Then run
+   `node <skillkatalog>/scripts/archive.mjs add-design <katalog> --file <absolut sökväg till designdokumentet>`.
+   The command verifies the doc (the frontmatter `request_id` against the directory's
+   id, `spec_sha256` against the current `spec.md`, `## Spec conflicts` is `none`, the
+   file lies inside the repo), puts an existing `design.md` aside, copies the doc
+   byte-identically into the directory as `design.md`, writes `state.json.design` and
+   sets status `designed`. It writes no runs row (see the `state.json` contract). Then
+   run `node <skillkatalog>/scripts/precheck.mjs <katalog> --design` and show any
+   BRIST or VARNING lines. Stage the file (`git add <sökväg>`); never commit (the
+   house git rule: commit only on explicit OK).
+
+   **A refused doc with conflicts** (exit 2 on `## Spec conflicts`): copy the refused
+   doc into the directory as `design-avvisad-<datum>.md` (`-2` on collision, never
+   overwrite: the receipt, like `spec-avvisad-<datum>.md`), then run
+   `node <skillkatalog>/scripts/archive.mjs stopp <katalog> --utfall TILLBAKA_TILL_SPEC --kalla design-avvisad-<datum>.md --orsak "<the conflict lines, one sentence each>"`;
+   if `state.json.respec_varv` is already ≥ 1, `--utfall ESKALERA` with the same
+   `--orsak`, as in speca step 6. A standing design-conflict stop (bedöm step 3) is
+   replaced by the receipt: the redesign showed the spec is the problem, so the spec
+   route wins. The stop is what `nasta-steg`, `bedöm` and the Closing read. From there
+   the item goes to customer dialogue, then
+   `## Avgjorda val`, `respec` and a new `speca`, exactly as a price-decisive open
+   choice does (ADR-0118). The doc also stays in the repo under its own name so the
+   conversation is not lost, but it is never recorded as the item's design.
+   **Other exit-2 refusals** on the doc (a mismatched `request_id`, a stale
+   `spec_sha256`, the file outside the repo or under `.haus-workflow/`): fix the doc
+   and rerun `add-design`; nothing is recorded until it passes. A refusal on the
+   item's state (status `priced` or `guard_run`, a standing stop other than a design
+   conflict) is not fixed in the doc: `respec`, or decide the stop first.
+
+6. **Reply BLUF:** one line per item (the design's title and path), the
+   `## Spec conflicts` section verbatim when it is not `none`, the commit offer, then
+   **Close per `## Closing: where the item stands`** (the table from
+   `archive.mjs nasta-steg`, the board line, the ISÄR check), never without. For a doc
+   refused on conflicts, the Closing's part 4 presents the conflicts as the choice
+   (`## Avgjorda val`, `respec`, `speca <adress>`).
+
 ## Task: `bedöm`
 
 Runs the pricing leg: an impact analysis if it is missing, then scoring with a
@@ -481,6 +636,17 @@ drift guard.
      the reviewer block cannot be recreated from Asana.
    - Note the passed gate in `state.json.approval` (the manual case with `by`).
      The next `bedöm` reads the status again.
+   - **Gate 1b, the design (only when the assessor is to be dispatched).** When
+     `impact.md` is missing, or precheck rejects it on source-material provenance
+     (step 3's condition), run `node <skillkatalog>/scripts/precheck.mjs <katalog> --design`
+     first. `DESIGN: saknas` or any BRIST from the flag: refuse, show the lines and the
+     command `designa <adress>`, and stop (a drifted canonical copy is re-recorded there
+     without a new brainstorming, designa step 3). An item whose `impact.md` is present and
+     provenance-valid is not gated: it was analysed under the old rules and may be
+     re-scored. New items always hit the gate, since they have no `impact.md` yet,
+     with one exception: a split part (`state.split.parent` set) is not gated, the
+     split copied the parent's `design.md` into it, and the assessor gets it as the
+     `DESIGN` block.
 2. **Form check.** Run `node <skillkatalog>/scripts/precheck.mjs <katalog> --impact`
    (without `--impact` if the analysis does not exist yet). A `spec.md` with more than one
    spec block is a BRIST: split the item per the archive rule before anything is dispatched.
@@ -495,7 +661,7 @@ drift guard.
    below. No analysis and no score may ever be dispatched on a
    candidate.
 3. **Analysis.** If `impact.md` is missing, or precheck rejects it on
-   source-material provenance (the analysis was made against another spec): this requires a repo in
+   source-material provenance (the analysis was made against another spec or another design): this requires a repo in
    the session (otherwise stop: a guessed analysis is forbidden by the skill itself).
    Dispatch `request-assessor` per the prompt template: the spec's reviewer block
    is sent along as internal source material (the same trust domain; the flags there are
@@ -505,13 +671,19 @@ drift guard.
    language is never guessed again, the same line goes to the scorer in step 4);
    the assessor verifies the manifest itself and must never take it as true
    (ADR-0113: the assessor explored the repo from zero even though the manifest already
-   existed). Archive the reply as `impact.md`
+   existed). The `DESIGN` block carries `design.md` from the directory byte-faithfully
+   (the hard rule: pasted, never pointed to by path), or the line `DESIGN: ingen` when
+   the directory has no design (a split part of a parent analysed under the old rules,
+   or a standalone assessor run). Archive the reply as `impact.md`
    (including its "## For the reviewer" block: show the block to the user,
    never to customer fields), stamp with
    `node <skillkatalog>/scripts/archive.mjs add-run <katalog> --file impact.md
 --skill request-assess-impact --agent request-assessor
 --model <ur MODELL-svansraden>` (the script sets `underlag_sha256` against
-   `spec.md`). Run precheck again with `--impact`. Then read the line
+   `spec.md`, and hashes `design.md` into `underlag_sha256` via `underlagFor` when
+   the file exists; precheck's provenance check on `--impact` compares both hashes,
+   so an analysis made against a superseded design is rejected the same way one made
+   against a replaced spec is). Run precheck again with `--impact`. Then read the line
    `AVVIKELSE: <etikett>` from the precheck output (the label on the analysis's row
    `**Deviation from the spec:**`; not to be confused with the agents' tail line):
    `motsägelse` means that the spec presupposes something that does not hold in
@@ -519,7 +691,10 @@ drift guard.
    `node <skillkatalog>/scripts/archive.mjs stopp <katalog> --utfall TILLBAKA_TILL_SPEC --kalla impact.md`
    (the command sets status `assessed`), skip steps 4 to 7 and route
    the item as the stop outcome below: no scorer is dispatched on source material
-   that already says the spec must go back. `ingen` and `precisering` go
+   that already says the spec must go back. When the deviation line's text after the
+   label starts with `design conflict:`, pass `--orsak "<that text>"`: the item goes
+   back to the design, not to the spec, and the Closing routes it to `designa <adress>`
+   (a redesign clears the stop, see `add-design`). `ingen` and `precisering` go
    on to step 4. If precheck rejects the new
    draft → redispatch the assessor ONCE per the redispatch rule, and give
    the rejected draft a receipt exactly as in speca step 6: archive it as
@@ -655,28 +830,69 @@ ref-hash.mjs på request-score/references/poangskala.md>
    that takes the item ✅ Spec ok → ⚖️ Poängsättning redo för granskning per
    the sync's rules. **Close per `## Closing: where the item stands`**
    (the table from `archive.mjs nasta-steg`, the board line, the ISÄR check, and
-   a stop outcome or OLIKA as a choice the user must make), never without.
+   a stop outcome or OLIKA as a choice the user must make; a `DELA_UPP` as the two
+   separate choices in the routing below), never without.
 
 **Stop outcomes are routed, never interpreted.** A stop outcome is archived as the round's
 file (step 7), the status becomes `assessed`, never `priced`, and the item is routed:
 
-- `DELA_UPP` → propose a new analysis round per part; the parts become directories of their own with
-  `split` set (`part`/`of`), and a part without a ceiling becomes `OVER_SKALAN`, never
-  DELA_UPP again. Sub-items inherit, per the skill, the item's spec and never write
-  one of their own: the parent's `spec.md` and `granskarblock.md` are COPIED unchanged into
-  each part directory, separately (one reviewer block per part directory, ADR-0118,
-  no part directory shares its block with another), while `impact.md` is written per
-  part by the new analysis round.
+- `DELA_UPP` → the Closing offers two separate yes/no choices (ADR-0144), each answered on its own:
+  1. **Split the item** (as before): a new analysis round per part; the parts become
+     directories of their own, `del-1/ … del-M/` under the parent's directory, with `split`
+     set (`parent`/`part`/`of`), each `state.json` written by the orchestrator as before
+     (`ny-del` stays the experiment's command: its skeleton carries `experiment: true`,
+     which `set-status priced` refuses), and a part without a ceiling becomes `OVER_SKALAN`,
+     never DELA_UPP again. Sub-items inherit, per the skill, the item's spec and never write
+     one of their own: the parent's `spec.md`, `granskarblock.md` and `design.md` are COPIED
+     unchanged into each part directory, separately (one reviewer block per part directory,
+     ADR-0118, no part directory shares its block with another), while `impact.md` is written per
+     part by the new analysis round. The parts inherit the parent's design the way they
+     inherit its spec: `state.design` stays `null` on a part, the parent's record is the
+     receipt, and bedöm's gate 1b does not run on a part.
+     **Every part becomes a subtask under the parent**, never a separate request: the sync
+     that follows a part's own `bedöm` round creates it, named as the part's changed state
+     with its scope line, both from the analysis round that pointed out the parts; the
+     orchestrator passes both to request-sync in the spec's language (the analysis round
+     writes English, so translate the name and the scope line when the spec is Swedish, the
+     same rule as the spec title). Then run
+     `node <skillkatalog>/scripts/archive.mjs set-split-gid <del-katalog> --gid <deluppgiftens gid>`
+     and pass the recorded `split.gid` to request-sync on every later sync of that part, so the
+     subtask is updated instead of created twice. Moving the parent from ✅ Spec ok to ⚖️ is
+     request-sync's job in the run that writes the last part's subtask: pass it `split.of`
+     and every part's state (`priced` with its score, or `OVER_SKALAN`, and its `split.gid`).
+     The parent row of `nasta-steg` says when that run is due:
+     `se delarna (K av M delar prissatta)` until every part is done, then the sync row,
+     `sync föräldern till brädan (request-sync ⚖️)`.
+  2. **Rewrite the parent as an umbrella** (optional, and only after choice 1 has created
+     the part directories: `paraply` refuses a parent without parts, and a no to the split
+     means no umbrella): dispatch `request-specifier` in umbrella mode, the template with the
+     `PARAPLY:` block (see the dispatch contract). Split the reply as in speca step 5,
+     write the spec to a scratch file outside the archive and show the draft BLUF with
+     its reviewer block. On an explicit yes, run
+     `node <skillkatalog>/scripts/archive.mjs paraply <katalog> --file <utkastet>`: it puts
+     the old `spec.md` aside as `spec-superseded-<datum>.md`, copies the umbrella in, sets
+     `title` from its heading and records `state.umbrella`; approval, design, runs, stops
+     and the parts are untouched (the parts keep the approved spec they were priced
+     against). A refusal (the form check or the title line) is redispatched ONCE with the
+     refusal lines as `RÄTTNINGAR:`; a second refusal stops and the parent keeps its spec.
+     After `OK: paraply`, write the description's `## Specifikation` from the umbrella via
+     request-sync, under the lock (`Decision` read first), never with a rename; when the
+     umbrella title differs from the task name, the Closing lists `byt titel <item>` as the
+     optional next action. No to the umbrella leaves the parent's description as it is.
 - `OVER_SKALAN` → the item is quoted separately; never split further (the split is done
   one step, the skill's own rule).
 - `TILLBAKA_TILL_SPEC` / `KONCEPT` / `DIAGNOS` → back to the spec step
-  or the customer dialogue respectively; show the reason. If the outcome came from the scripts (a candidate in
+  or the customer dialogue respectively; show the reason. A `TILLBAKA_TILL_SPEC` from
+  `impact.md` whose `orsak` starts with `design conflict:` routes to `designa <item>`
+  (a redesign, bedöm step 3), not to `speca`. If the outcome came from the scripts (a candidate in
   `spec.md`, `contradiction` in `impact.md`, a price-decisive open choice in
-  `granskarblock.md`, ADR-0118), `state.json.stopp` carries it via
+  `granskarblock.md`, ADR-0118, conflicts in a refused design's
+  `design-avvisad-<datum>.md`), `state.json.stopp` carries it via
   `archive.mjs stopp` and there is no round file; if it came from the scorer,
   the round file is archived as before and `stopp` stays `null` (the command takes
-  only the three script-proven sources: `spec.md`, `impact.md`,
-  `granskarblock.md`). A respec resets `stopp`.
+  only the script-proven sources: `spec.md`, `impact.md`, `granskarblock.md` and a
+  `design-avvisad-<datum>.md` receipt). A respec resets `stopp`; `add-design` clears
+  a design-conflict stop from `impact.md`.
 - `ESKALERA` / `INPUT_SAKNAS` → show the reason and stop, or a price-decisive
   choice that remains after respec (source `granskarblock.md`, reason in
   `stopp.orsak`, ADR-0118).
@@ -718,7 +934,7 @@ get wrong:
   description fields.
 - **Close per `## Closing: where the item stands`** when the item has an
   archive directory: the table from `archive.mjs nasta-steg` plus the board line, so
-  the move is visible together with what it opens up for (`bedöm`, customer, nothing).
+  the move is visible together with what it opens up for (`designa`, customer, nothing).
 
 ## Task: `döm`
 
@@ -821,11 +1037,34 @@ facts in the analysis above.
 ## Task: `detaljer`
 
 `detaljer <gid|slug|nr> [step]`: print archived files for the item: without
-a step, a list of what exists; with a step (`spec`, `granskarblock`, `analys`,
-`poäng`, `state`) the file's content raw; `klass` reads older archives'
+a step, a list of what exists; with a step (`spec`, `granskarblock`, `design`,
+`analys`, `poäng`, `state`) the file's content raw (`design` prints `design.md`);
+`klass` reads older archives'
 classification files (before ADR-0098). For `klass`/`poäng`: the latest
 `-pricing-vN.json` without a suffix (never `-run2`/`-avvisad`).
 
+## Task: `byt titel`
+
+`byt titel <nr|gid>`: rename the item's Asana task to the spec title, on request only
+(ADR-0144). The task name follows the customer: request-sync renames it by itself only
+in the three automatic cases (empty task name, empty `Original request title`, or one of
+several tasks minted from one source), and this task is the only other way the spec title
+reaches the name.
+
+1. **Gate: the item has a gid.** Addressing as for `godkänn` (a row number from the latest
+   `status` listing in the same session, or a gid; never fuzzy heading matching). An item
+   without a gid is not on the board: say so and stop. An item with a gid but no archive
+   directory: say so and stop, the spec title lives only in the archive.
+2. **Read the title.** Read `title` from the directory's `state.json` (`add-run` writes it
+   from the heading of `spec.md`, `paraply` from the umbrella's). A `null` title: say so
+   and stop.
+3. **Rename via request-sync** in the main conversation (the Skill tool): the gid and the
+   title, nothing else. request-sync keeps ADR-0124's order: `Original request title` is
+   written and read back before the task name changes. A title equal to the current task
+   name is no rename: say so and change nothing.
+4. **Close per `## Closing: where the item stands`**: the table from `archive.mjs nasta-steg`
+   and the board line. The archive status does not change.
+
 ## Task: `utvärdera`
 
 Model evaluation: `utvärdera <item…> <model…>`, with at least one model. Runs an
@@ -944,6 +1183,21 @@ The question is therefore about the cost, not the risk of losing data.
    The manifest ends with the section `## Avgjorda val`: every choice that a human
    has decided after an earlier stop, one line each, verbatim as the answer was given;
    `inga` if there are none. The specifier must never flag a choice that stands there.
+   The design is an optional pinned input, like the manifest: when the production
+   archive holds a recorded design for the item, copy it byte-identically to
+   `experiments/<slug>/design.md` and note its hash with
+   `archive.mjs experiment experiments/<slug> --satt design_sha256=<hash>`
+   (`ref-hash.mjs` on the file). `korning.mjs` reads the file when it exists, copies
+   it into every part directory before the assessor runs (so `add-run` hashes it) and
+   pastes it as the assessor's `DESIGN` block. Without the file every round runs as
+   today. Known limitation, recorded so nobody measures against it by accident: a
+   sweep regenerates the spec per round while the design is fixed against one
+   production spec, so a sweep with a design measures the assessor and the scorer
+   against a design that may not match the round's spec byte for byte, and a bundle's
+   parts all get the one experiment design, while production designs are per item
+   directory; `experiment.json.design_sha256` and the part's `impact.md` runs row
+   (`underlag_sha256["design.md"]`, shown by `detaljer`) tell the reader which
+   design the round ran against.
 3. **The escalation choice is made once** per `speca`'s rules and applies to all
    rounds; the escalation choice too is part of what is held constant.
    If the choice triggers: the agent becomes `request-specifier-eskalerad` instead of
@@ -1098,7 +1352,8 @@ The question is therefore about the cost, not the risk of losing data.
    the split itself, see step 4; the rules here apply when it runs):
    part directories
    `<modell>/k<N>/del-1/ … del-N/` with `split` set, the parent's `spec.md` +
-   `granskarblock.md` copied in, a new analysis + score per part. If a
+   `granskarblock.md` (and `design.md`, when the experiment has one) copied in, a new
+   analysis + score per part. If a
    bundle part is split, it becomes `del-N/del-M/` under that part, never a new
    sibling in the root (`bundle` and `split` are never set on the same directory).
    A part without a ceiling becomes `OVER_SKALAN` and is never split further. Other
@@ -1251,7 +1506,7 @@ the human's, made on experience of the system. The report shows the spread.
 
 ## Closing: where the item stands
 
-The tasks `speca`, `bedöm`, `godkänn`, `underkänn` and `döm` ALWAYS end
+The tasks `speca`, `designa`, `bedöm`, `godkänn`, `underkänn`, `döm` and `byt titel` ALWAYS end
 with this block (#530). A reply that ends without it leaves
 the user to guess where the item stands, what they should do and which command
 runs on, and the archive and the board can then drift apart silently (`spec_draft`
@@ -1262,32 +1517,39 @@ locally, empty Offer status on the board). The block consists of four parts, in
    directory and part), NEVER handwritten, for the same reason as `bluf`: a
    handwritten closing drops exactly the row that would have said what is
    waiting. The script computes the rows from `state.json` (status, `stopp`,
-   `respec_varv`, `approval`, an unlifted OLIKA via the hold, the scorer's current
-   outcome from the pricing file) with the rules from this skill's own gates;
+   `respec_varv`, `approval`, `design`, an unlifted OLIKA via the hold, the scorer's current
+   outcome from the pricing file and, on a split root, how many parts are done) with the
+   rules from this skill's own gates;
    the rule table with a source reference per row stands above the function
    `nastaStegFor` in the script. A state the script does not know is written as
    `okänt läge: <status>`, never as a guess.
 2. **The board line.** If the item has a gid: fetch Offer status via request-sync in
    the main conversation (never from memory) and write the line
    `Bräda: <Offer status>` directly under the table. If the item lacks a gid: write
-   `Bräda: ingen (posten ligger inte på brädan)`.
+   `Bräda: ingen (posten ligger inte på brädan)`. For an item at
+   ⚖️ Poängsättning redo för granskning, add one line: the analysis and the pricing are
+   not on the board (ADR-0144), `detaljer <item>` shows them.
 3. **The ISÄR check.** The archive status and the Offer status must correspond to each other
    per the table below (the values are request-sync's, normalized on
    the alphabetic core as there). If they differ, a line
    `ISÄR: arkiv <x>, bräda <y>` is written, followed by the command that closes the gap.
 
-   | archive status (`state.json`)                  | expected Offer status                | closes the gap                                                                                 |
-   | ---------------------------------------------- | ------------------------------------ | ---------------------------------------------------------------------------------------------- |
-   | `spec_draft`                                   | empty or 📥 Inkommet                 | sync via request-sync (🔍) when the spec is to be reviewed                                     |
-   | `spec_synced`                                  | 🔍 Spec redo för granskning          | `godkänn`/`underkänn`, or sync if the board stands at 📥                                       |
-   | `spec_synced`/`spec_draft` with `approval` set | ✅ Spec ok                           | `bedöm`; if the board stands at 🔍, the approval note is older than the board, reread the gate |
-   | `assessed`/`priced`, the score synced          | ⚖️ Poängsättning redo för granskning | sync via request-sync if the board still stands at ✅                                          |
-   | done (`godkänn` from ⚖️)                       | 📤 Klar – till kund                  | nothing, the customer's `Decision` decides the rest                                            |
+   | archive status (`state.json`)                          | expected Offer status                                                          | closes the gap                                                                                                                                              |
+   | ------------------------------------------------------ | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+   | `spec_draft`                                           | empty or 📥 Inkommet                                                           | sync via request-sync (🔍) when the spec is to be reviewed                                                                                                  |
+   | `spec_synced`                                          | 🔍 Spec redo för granskning                                                    | `godkänn`/`underkänn`, or sync if the board stands at 📥                                                                                                    |
+   | `spec_synced`/`spec_draft` with `approval` set         | ✅ Spec ok                                                                     | `designa`; if the board stands at 🔍, the approval note is older than the board, reread the gate                                                            |
+   | `designed`                                             | ✅ Spec ok                                                                     | `bedöm`; if the board stands at 🔍, the approval note is older than the board, reread the gate                                                              |
+   | `assessed` with the scorer's `DELA_UPP` (a split root) | ✅ Spec ok until every part is done, then ⚖️ Poängsättning redo för granskning | the parent row of `nasta-steg` (`se delarna (K av M delar prissatta)`), then the sync that moves the parent, `sync föräldern till brädan (request-sync ⚖️)` |
+   | `assessed`/`priced`, the score synced                  | ⚖️ Poängsättning redo för granskning                                           | sync via request-sync if the board still stands at ✅                                                                                                       |
+   | done (`godkänn` from ⚖️)                               | 📤 Klar – till kund                                                            | nothing, the customer's `Decision` decides the rest                                                                                                         |
 
    The archive is a cache and Asana the truth (Hard rules): an ISÄR is always resolved
    in the direction of the board, never by rewriting the board to match
    the archive. An experiment variant (`experiment: true`) has no board line and
-   no ISÄR check; it never reaches Asana.
+   no ISÄR check; it never reaches Asana. A split part has no Offer status of its own:
+   its place on the board is its subtask (`split.gid`), so a part row gets no board line
+   and no ISÄR check.
 
 4. **The choice, when there is one.** A stop outcome (`TILLBAKA_TILL_SPEC`,
    `ESKALERA`, `KONCEPT`, `DIAGNOS`) and an unlifted `double_run: olika`
@@ -1296,8 +1558,12 @@ locally, empty Offer status on the board). The block consists of four parts, in
    open choice from `stopp.orsak` or the source file; for OLIKA the two
    runs' evidence side by side, see bedöm step 6) and the command that
    carries out the answer (`speca <item>` after `## Avgjorda val` + `respec`,
-   `döm <item>`, customer dialogue). A stop that is only routed is read as "the machine
-   is working on it", and nobody does anything.
+   `döm <item>`, customer dialogue). A `TILLBAKA_TILL_SPEC` from `impact.md` whose
+   `orsak` starts with `design conflict:` routes to `designa <item>` (a redesign, bedöm
+   step 3), not to `speca`; the command for that case is `designa <item>`. A stop that
+   is only routed is read as "the machine is working on it", and nobody does anything.
+   A `DELA_UPP` is presented as two separate yes/no choices, split the item and rewrite
+   the parent as an umbrella (bedöm's routing, ADR-0144), each answered on its own.
 
 ## Mechanical scripts: `scripts/`
 
@@ -1313,7 +1579,7 @@ cheaper, faster and without judgment drift. Every script carries sha256 for the
 reference files whose rules it mirrors and WARNS when a catalog bump has changed them
 (contract drift must be discovered by a check, not by a customer):
 
-- `scripts/precheck.mjs <arkivkatalog> [--impact]`: the form check BEFORE expensive
+- `scripts/precheck.mjs <arkivkatalog> [--impact] [--design]`: the form check BEFORE expensive
   dispatches: headings, exactly one spec block, 2–5 bullets, forbidden vocabulary,
   reviewer block rows, state.json fields. Distinguishes BRISTER (exit 1, stops)
   from VARNING (a heuristic: shown, does not stop). The headings are matched via
@@ -1326,7 +1592,21 @@ reference files whose rules it mirrors and WARNS when a catalog bump has changed
   `**Deviation from the spec:**` is read and written as `AVVIKELSE: ingen`,
   `AVVIKELSE: precisering` or `AVVIKELSE: motsägelse`; a row without a
   label is a BRIST. The orchestrator reads candidate and deviation from those
-  lines, never from the files itself.
+  lines, never from the files itself. The spec rules live in `lib.mjs` (`specForm`),
+  shared with `archive.mjs paraply` (ADR-0144).
+  With `--design` (`designa` step 3 and `bedöm` gate 1b): `design.md` must exist,
+  `state.design` must be set, the hash of `design.md` must equal `state.design.sha256`,
+  the canonical file at `state.design.path` must exist and hash the same, the
+  frontmatter `request_id` must equal the directory's id, `spec_sha256` must equal the
+  current `spec.md` hash, and `## Spec conflicts` must be `none`; each failure is a
+  BRIST. Size words, hours and score words in the design body are a VARNING (the
+  assessor is instructed to ignore them, the reviewer should see them). The line
+  `DESIGN: ok` (the file exists and `state.design` is set) or `DESIGN: saknas` is
+  written always, even at exit 1, so the orchestrator reads the state from the line
+  and never from the files. With `--impact`, a `design.md` in the directory must
+  match the analysis row's `underlag_sha256["design.md"]`, the same provenance rule
+  as for `spec.md`, except that a missing design hash is a BRIST, not a VARNING:
+  the design existed when the analysis should have seen it.
 - `scripts/resolve-anchors.mjs <run.json> <spec.md> [impact.md]`: resolves
   evidence anchors (`belagg_ankare`/`ankare`) to verbatim source blocks, runs
   BEFORE contract-check. Exit 0 = everything resolved (or no anchors in the file), 1 =
@@ -1377,20 +1657,48 @@ reference files whose rules it mirrors and WARNS when a catalog bump has changed
 - `scripts/archive.mjs <kommando> <katalog> [flaggor]`: the archive's mechanics
   (full list in the script's header): `add-run`, `next-n`, `sparr`,
   `utslag`, `set-status`, `kalibrering`, `ny-korning`, `proveniens`, plus
-  `stopp <katalog> --utfall KONCEPT|DIAGNOS|TILLBAKA_TILL_SPEC --kalla spec.md|impact.md`
+  `add-design <katalog> --file <path>` (verifies the design doc: frontmatter
+  `request_id` = the directory's id, `spec_sha256` = the current `spec.md` hash,
+  `## Spec conflicts` = `none`, the file inside the repo root; puts an existing
+  `design.md` aside as `design-superseded-<datum>.md`, copies the doc in
+  byte-identically, writes `state.design` and sets status `designed`; no runs row;
+  refuses a file under `.haus-workflow/`, a `priced` or `guard_run` item and any
+  standing stop except a design conflict from `impact.md`, which it clears, putting
+  `impact.md` aside as `impact-superseded-<datum>.md`;
+  exit 2 on every refusal, under the archive lock),
+  `set-split-gid <del-katalog> --gid <gid>` (records a split part's Asana subtask gid in
+  `split.gid` under the archive lock; refuses a directory without `split`, a gid that is not
+  digits only and a different gid already recorded, while the same gid again is a no-op;
+  ADR-0144),
+  `paraply <katalog> --file <spec>` (rewrites the parent's spec as an umbrella: refuses a
+  split part, an item without `approval`, a file that fails the spec form check
+  `precheck.mjs` runs, a file without a title line and an unreadable file; puts `spec.md`
+  aside as `spec-superseded-<datum>.md`, copies the file in, sets `title` from its heading
+  and records `state.umbrella = { date, sha256 }`; approval, design, runs, stops and the
+  parts are untouched; prints `OK: paraply <sha256>`; ADR-0144),
+  `stopp <katalog> --utfall KONCEPT|DIAGNOS|TILLBAKA_TILL_SPEC|ESKALERA --kalla spec.md|impact.md|granskarblock.md|design-avvisad-<datum>.md [--orsak <text>]`
   (writes `state.stopp` after checking that the source carries the outcome;
-  `--kalla impact.md` sets status `assessed`, `--kalla spec.md` does not touch
+  `--kalla design-avvisad-<datum>.md` requires at least one conflict under
+  `## Spec conflicts` in that receipt and takes `TILLBAKA_TILL_SPEC` or `ESKALERA`,
+  and replaces a standing design-conflict stop from `impact.md` (any other standing
+  stop refuses a different one, exit 2);
+  `--kalla impact.md` sets status `assessed`, the other sources do not touch
   the status), `respec <katalog>` (puts `impact.md` aside as
-  `impact-superseded-<datum>.md`, resets status (to `spec_draft`),
-  `approval`, `granskarutslag` and `stopp`, never touches `runs[]`) and
+  `impact-superseded-<datum>.md` and `design.md` as `design-superseded-<datum>.md`,
+  resets status (to `spec_draft`), `approval`, `granskarutslag`, `stopp` and
+  `design`, never touches `runs[]`) and
   `bluf <katalog>` (the markdown table `| post | poäng | utfall | konfidens | anm |`
   over the directory and its `del-N/` recursively, the bundle root as
-  `bunt (N delar)`; the values from the files, never from prose) and
+  `bunt (N delar)`, a split root with `K av M delar prissatta` in `anm`; the values from
+  the files, never from prose) and
   `nasta-steg <katalog>` (read-only, the markdown table
   `| post | står | väntar på | nästa |` over the directory and its `del-N/`
   recursively: where the item stands, what a human is expected to do and which
   `/request` command runs on, from `state.json` and the scorer's current
-  outcome per the rule table in the script; an unknown state is written as
+  outcome per the rule table in the script; on a split root the parent row counts the
+  parts (`se delarna (K av M delar prissatta)`) until every part is `priced` or
+  `OVER_SKALAN` and then names the sync that moves the parent, and a part row says
+  whether its subtask is recorded (`split.gid`); an unknown state is written as
   `okänt läge: <status>` with exit 0, a broken `state.json` is exit 2, see
   `## Closing: where the item stands`). `add-run` reads
   `effort:` from the agent definition when `--effort` is omitted and canonicalizes
@@ -1498,6 +1806,25 @@ continue as if the check had passed.
   English `**Concept candidate**` or `**Diagnosis candidate**`); the
   specifier decides that itself per the skill.
 
+  In umbrella mode (`bedöm`'s `DELA_UPP` choice 2, ADR-0144) the prompt is the template
+  above with `ESKALERAD: nej`, `ÖNSKEMÅL:` from the description's `## Ursprunglig förfrågan`,
+  `KÄLLOR:` from `kallmanifest.md` and `SPRÅK:` from its first line, and it ends with one
+  more block:
+
+  ```
+  PARAPLY:
+  <förälderns spec.md bytetroget>
+
+  DELAR:
+  del 1: <delens namn, det ändrade läget>: <omfattningsraden>
+  del 2: <delens namn, det ändrade läget>: <omfattningsraden>
+  ```
+
+  The parent's spec is pasted byte-faithfully (the hard rule); the part lines come from
+  the analysis round that pointed out the parts, one per part directory, in part order.
+  The umbrella dispatch writes no runs row: `state.umbrella` is its receipt once `paraply`
+  accepts the draft.
+
   `request-assessor`:
 
   ```
@@ -1524,6 +1851,9 @@ continue as if the check had passed.
 
   GRANSKARBLOCK (internt underlag, följer aldrig med i analysens kundtext):
   <granskarblock.md bytetroget>
+
+  DESIGN (beslutad i brainstorming, internt underlag, följer aldrig med i analysens kundtext):
+  <design.md bytetroget, eller raden "DESIGN: ingen">
   ```
 
   `RUBRIKER:` is the analysis's own heading skeleton, the English literals from
@@ -1531,6 +1861,11 @@ continue as if the check had passed.
   The skeleton is independent of `SPRÅK:`, which steers only the analysis's customer-facing
   parts, not this internal structure.
 
+  `DESIGN` is the item's design doc from the directory (`design.md`, written by
+  `designa`), pasted, never pointed to by path: the hard rule "documents are pasted
+  byte-faithfully" applies. Without a design (a split part of a parent analysed under
+  the old rules, or a standalone assessor run) the block is the single line `DESIGN: ingen`.
+
   `request-scorer` (source material by path, ADR-0099: never pasted):
 
   ```