docs(linkedin-studio): N6 — bånd-fordelings-kalibrering (MR-F6) i trend-scoring-modes.md

Ukalibrert modell-dømmekraft inflaterte topp-båndet (observert 13/20 → Immediate).
Legger til en eksplisitt fordelings-forventning som scoring-SSOT: de fleste kandidatene
hører hjemme i Medium–High (4.0–7.9); Immediate (≥8.0) er unntaket (arbeidsmål ≤~3/20).
Score relativt over batchen, ikke sjenerøst i isolasjon.

Fordelings-formen er mekanisme; terskelen for hva som teller som eksepsjonelt bor i
brukerprofilen/dimensjons-rubrikkene, aldri hardkodet (domene-generelt). Etterprøvbart nå
fordi composite+band persisteres (RE-R3a); MR-F7-bånd-cap-gaten (N7) bygger på samme signal.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S7SQpXJpBSNvpWaTNq1kWZ
This commit is contained in:
Kjell Tore Guttormsen 2026-07-21 09:10:06 +02:00
commit bace49f8c2

View file

@ -92,6 +92,36 @@ The same priority bands apply to both modes (the composite is on the same 010
| 2.03.9 | **Low** | Note, skip for now | Park unless the angle sharpens |
| 01.9 | **Skip** | Off positioning | Off positioning |
## Calibration — the expected score distribution (MR-F6)
The five dimensions are **model judgment**, and unanchored judgment inflates: an observed sweep
put 13 of 20 candidates in **Immediate** (≥8.0), which makes the band meaningless — if most
things are "draft now", nothing is. The composite is only useful if the bands are **scarce at the
top**. So a scoring pass must calibrate against this distribution expectation, not score each
candidate generously in isolation:
- In a **typical sweep**, most candidates belong in **MediumHigh (4.07.9)**. That is the honest
home of "worth writing about, eventually".
- **Immediate (≥8.0) is the exception, not the rule** — reserve it for candidates that are
genuinely exceptional *relative to the rest of this sweep*. As a working target, expect on the
order of **≤3 of 20** in Immediate; a sweep that floods the top band is uncalibrated, not lucky.
- **Skip/Low (<4.0)** is a real outcome — an off-pillar or already-resolved topic should land
there, not get floated to Medium to be polite.
Mechanics for the pass:
- **Score relatively across the batch.** A 910 on a dimension means "exceptional versus the other
candidates in *this* sweep", not "good in the abstract". Rank the batch, then assign — a flat
batch of 8s is the failure mode this rule exists to catch.
- **The distribution shape is the mechanism; the threshold of what counts as exceptional is the
user's calibration** (the dimension rubrics above + the profile), never a hard-coded fact about
any one operator's topics. Domain-general: the anti-inflation rule travels; the specific bar does
not live here.
- **This is now measurable.** The composite + band are **persisted** on each record (RE-R3a,
`TrendRecord.score`), so the distribution can be checked across runs — e.g. count the Immediate
share of a stored sweep. The MR-F7 band-cap gate (N7) builds on the same persisted signal: a
candidate with no formulable reader-grip is capped below Immediate regardless of composite.
## Consumers
- `agents/trend-spotter.md` — reads the requested mode and applies the matching rubric