# V1.4.4 additional mandatory prompt

Read this with the V1.4.4 main prompt. This file is authoritative for Step 2 How mapping. V1.4.4 requires an internal review-and-correction pass before each delivery.

## Step 2 — restrained How mapping

### General admission test

Include a How link only when the source has a direct, material and reasonably specific contribution to the target. Theme similarity, broad usefulness, consultation, general interest or eventual downstream benefit is insufficient.

Review every actual source against every candidate in its permitted target layer. A source may legitimately have no accepted targets; record a source-specific reason rather than adding a token link.

Do not use quotas, equal counts, blanket coverage or one-link-per-source patterns. Review target-side duplication and remove links that merely restate a relationship already represented at a closer layer. Complete this review before packaging; do not turn the findings into a mandatory public user-check list.

### Default layers

Unless the user selected another setup:

- Level 1 → ordinary This–Then boxes;
- Level 2 → adjacent Level 1 boxes;
- competency/no-level page → Level 1 projects only.

Competencies must be unusually important, deliberately deployed or essential to delivery. Generic usefulness is not enough. Competencies may have zero links. If a competency genuinely applies to nearly every project, record it as a board-wide capability rather than repeatedly mapping it, unless the links make distinct decisions visible.

Calculate competency density using only the actually permitted target layer. Review:

- any competency reaching more than half the permitted projects;
- any project receiving nearly all competencies;
- a suspicious modal pattern where most competencies have the same positive link count;
- broad organisational sources that blur ownership, funding, governance, assurance and delivery.

Density thresholds are diagnostic review indicators, not target maximums. Never add or remove a relationship merely to land below a threshold. Retain or remove every link through the pair-specific admission test and explain any broad exceptions.

A user-selected alternative arrangement is permitted. Record it as `targetMode: "user-defined"`, state the user override reason and declare the exact permitted target refs.

### Step 2 annotations

All `mainText`, `notes1`, `notes2`, `notes3` and traffic-light fields on both link types remain blank.

### Completion review

Before packaging, inspect the actual final mapping and prune clear theme-only, generic, quota-driven, duplicated or implausibly broad links. Do not claim that all debatable ownership or contribution judgements have been eliminated. Record remaining judgement-dependent matters in the internal audit without converting them into a mandatory public issue list.