Weak Signal Log¶
Artifact — instantiates Weak Signal Triage
Records weak signals in a durable form so later evidence can be compared against the original observation rather than reconstructed from memory.
Weak Signal Log is the durable, faithful store of an ambiguous observation at the moment it was noticed — what was seen, why it is hard to interpret, and who is accountable for it — kept so that when more evidence arrives it is checked against the original record rather than against a hazy memory of "didn't someone mention this?" Its defining move is that it preserves without judging: it does not score the signal, tier it, or decide what to do about it. It fixes the observation and its uncertainty in place, un-rewritten, so that every later step of triage has a stable thing to reason from. A weak signal that is only remembered is a weak signal that will be quietly re-authored by whatever happens next; the log's whole reason to exist is to prevent that.
Example¶
A procurement analyst at a company that buys specialty capacitors notices three faint things over a month. A single supplier's on-time delivery slipped from 98% to 94%. A sales rep, in passing, mentioned "tight allocation this quarter." A public post showed that supplier's plant manager had left. Any one of these is the kind of thing you wave off. Instead she opens the weak signal log and records each: source, date, the verbatim wording of the rep's comment, her own read on the ambiguity ("could just be seasonal; could be early stress on a single-source part"), the assumption it threatens ("our capacitor supply is stable"), and she tags herself as owner.
Six weeks later a second delivery slips. Because the original entries are intact and untouched, the team compares the new data against what was actually observed and doubted at the time — not against a reconstruction colored by the fact that things later went wrong. The log's value shows up precisely here: it made a faint, easily-forgotten observation retrievable, and it kept the analyst's original uncertainty honest instead of letting hindsight rewrite it into "we always knew."
How it works¶
- Capture verbatim, with provenance. The observation is recorded in the words and form it arrived in, with source and date, not paraphrased into a conclusion.
- Record ambiguity as a field, not a problem to resolve. Why is this hard to read? What kinds of error are plausible? These are stored, not settled.
- Assign an owner at entry. Every record leaves the pen with a named person accountable for it, so it cannot become anonymous backlog.
- Keep the original immutable; append updates. Later evidence is appended as new entries; the original is never edited, so the trajectory is auditable and the first observation stays uncorrupted.
Tuning parameters¶
- Capture threshold — how faint an observation is worth logging. A low threshold catches more early evidence but grows a noisier store; a high one keeps the log clean but drops the faintest signals, which are often the most valuable.
- Field richness — how much structure each record carries (bare note vs. source, uncertainty, threatened assumption, follow-up need). Richer records interpret better later but cost more to enter, discouraging capture.
- Immutability policy — strict append-only vs. editable. Append-only protects the audit trail against hindsight rewriting; editable is lighter but lets the original quietly drift.
- Owner-assignment rule — self-assign at entry vs. routed later. Self-assign guarantees accountability but can concentrate load on noticers.
When it helps, and when it misleads¶
Its strength is that it defeats memory distortion: the original observation and the doubt attached to it survive intact, so later evidence updates a real record instead of a story. That is what makes the rest of triage possible — you cannot compare a trajectory against an origin you no longer have.
Its failure mode is becoming a graveyard. A log that nothing consumes turns into signal theater — a growing list that proves diligence while changing nothing, which is exactly the "collection without action" pathology. A subtler trap is hindsight bias working in reverse of what the log intends: once an event unfolds, readers over-credit whichever early entries pointed at it and forget the equally-faint ones that pointed nowhere.[1] The guarding discipline is to keep the log strictly an input — every entry must be picked up by a review that assigns a tier and an owner elsewhere — and to preserve the record's original uncertainty so that "we logged it" is never mistaken for "we understood it."
How it implements the components¶
Weak Signal Log fills the capture side of the archetype — the components that must exist before any assessment can begin:
weak_signal_record— it is the record: the durable, faithful store of the observation, its source, date, and the assumptions it threatens.ambiguity_context— it captures why the signal is hard to interpret as a first-class field, so the doubt travels with the observation instead of being lost.signal_owner— it stamps an accountable owner on each entry, so no record becomes anonymous.
It does not score plausibility_assessment or impact_estimate — that is the Signal Scoring Rubric; and it does not assign a response_tier or commission a follow_up_probe — those decisions belong to the Emerging Issue Triage Board. The log preserves the raw material; it does not act on it.
Related¶
- Instantiates: Weak Signal Triage — the log supplies the durable record every other mechanism reads from.
- Sibling mechanisms: Emerging Issue Triage Board · Signal Scoring Rubric · Watchlist Review · Probe Experiment · Early Warning Forum · Uncertainty Dashboard · Escalation Playbook
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Weak Signal Log operates as a persistent ledger, log, register, or case record that preserves history and traceability because it records weak signals in a durable form so later evidence can be compared against the original observation rather than reconstructed from memory.
Independent corroboration: The frozen evidence defines Weak Signal Log as 'Records weak signals in a durable form so later evidence can be compared against the original observation rather than reconstructed from memory', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Futurism & Strategic Foresight
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: Both independent reviews identify futurism foresight as the historical home of the operation—Records weak signals in a durable form so later evidence can be compared against the original observation rather than reconstructed from memory.. The retained alternates document formative adjacent traditions; the reach field, not the origin field, carries later applicability.
Related originating lineages:
- History & Historiography — Historical and historiographic method supplies a parallel or contributing lineage for the mechanism's defining operation: records weak signals in a durable form so later evidence can be compared against the original observation rather than reconstructed from memory.
- Library & Information Science — Library and information-science stewardship supplies a parallel or contributing lineage for the mechanism's defining operation: records weak signals in a durable form so later evidence can be compared against the original observation rather than reconstructed from memory.
- Organizational & Management Science — Organizational management's workflow, review, staffing, and coordination tradition contributes a separate formative lineage to the mechanism's weak signal log logic.
Review resolution: Both blind reviewers independently place the defining operation—Records weak signals in a durable form so later evidence can be compared against the original observation rather than reconstructed from memory.—in futurism foresight. Their queued differences are secondary: alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement. Reviewer A uniquely contributes no additional alternate; reviewer B uniquely contributes ['history_historiography', 'library_information_science']. I preserve the full evidence-supported union of 3 alternate domain(s), without a numeric cap. origin_mode=single_lineage reflects the more specific lineage judgment in reviewer B's evidence, while domain_reach=universal separately records present-day portability. The affirmative encyclopedia-synthesis finding is preserved, and confidence=medium uses the more conservative reviewer level.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The log deliberately refuses to resolve ambiguity. That restraint is what lets triage be re-run — re-scored, re-tiered, re-interpreted — without ever corrupting the source it reasons from. The moment a log starts editing originals to match what later turned out to be true, it stops being evidence and becomes a memoir.
References¶
[1] Fischhoff, B. "Hindsight Is Not Equal to Foresight: The Effect of Outcome Knowledge on Judgment Under Uncertainty". Journal of Experimental Psychology: Human Perception and Performance 1(3): 288–299 (1975). Shows that outcome knowledge inflates the apparent prior likelihood of what occurred and changes which preceding information seems relevant. registry ↩