Skip to content

Signal Issuance Rubric

Issuance protocol — instantiates Signal Value Preservation

A written test of the evidence and category a case must satisfy before a given signal may fire — the gate that decides whether the mark goes up and exactly what it then claims.

Signal Issuance Rubric is the decision procedure an issuer applies before firing: a checklist of evidence thresholds and category boundaries a case must clear, plus a one-line statement of exactly what the issued signal then claims. Its distinguishing idea is that it governs the merits of the individual case — not the price of issuing it and not its publication. Where a bond makes firing costly and a register makes criteria public, the rubric is the operative test run in the moment: pass, and the signal fires meaning one specific thing; fail, and it doesn't. It preserves signal value by keeping every firing tied to evidence and pinned to a single clear claim, so the mark keeps separating real cases from ordinary ones.

Example

A network's red BREAKING chyron had crept onto routine updates until viewers stopped reading it as urgent. The desk adopts an issuance rubric: BREAKING may go up only if (a) the development is within roughly the last half-hour, (b) two independent sources confirm it, © it materially changes what viewers should do or expect, and (d) the banner states what specifically is new. A scheduled earnings release fails (a) and © → no banner. A plant explosion with two-source confirmation passes → BREAKING, with the claim pinned to "explosion confirmed, cause unknown" rather than an open-ended alarm. Within weeks the banner means "drop what you're doing" again, because it now fires only when the four conditions actually hold.

How it works

The distinctive move is an explicit pass/fail test applied per case against evidence thresholds and category boundaries, coupled to a claim template that fixes what the fired signal asserts. It does not price the firing, publish the criteria, or count how often the signal goes up — it decides. Rubrics are usually built as necessary conditions (all must hold) plus a short statement of the exact claim, so no single mark is quietly overloaded with several meanings.

Tuning parameters

  • Bar height — how much evidence each criterion demands. Higher preserves scarcity but risks missing real cases.
  • Necessary vs. weighted — all-conditions-must-hold vs. a scored threshold. Hard gates are predictable; scoring flexes for edge cases but invites fudging.
  • Claim granularity — how tightly the rubric pins what a firing asserts. Tighter claims resist one mark accreting many incompatible meanings.
  • Reviewer — self-applied vs. a second-person sign-off before firing. A second signer curbs optimism at the cost of speed.
  • Update cadence — how often the criteria are revisited as real cases and gaming patterns shift.

When it helps, and when it misleads

Its strength is that it forces every firing to be justifiable on evidence and pins one claim per mark, which makes issuance auditable after the fact. Its failure mode is ossification and box-ticking: issuers reverse-engineer cases to satisfy the letter of the rubric, or the criteria freeze while the world moves. The classic misuse is writing the rubric loose enough to justify whatever you were going to flag anyway — a rationale dressed as a rule. The discipline that keeps it honest is to pair the rubric with after-the-fact review of firing rates and false alarms and to revise the bar when it drifts, rather than treating the written criteria as self-enforcing.

How it implements the components

  • evidence_and_specificity_rule — the rubric is the evidence thresholds and category boundaries a case must clear to qualify.
  • signal_claim_definition — it fixes exactly what the fired signal claims, so one mark is not overloaded with many meanings.

It does not make issuing costly (channel_scarcity_policy) — that is Issuance Cost or Bond; it does not publish these criteria or the accredited-issuer list (issuance_authority_boundary) — that is the Public Criteria Register; and it does not monitor how often the signal actually fires — the Receiver Response Dashboard and Base-Rate and Precision Dashboard do.