Dossier
The battlefield is perception.
This is an information war.
We continuously observe the information environment, identify important signals and narratives, verify claims, connect evidence, prioritize threats and turn them into actionable intelligence.
Explore the system01 / The battlefield
A claim can cross the world before the evidence reaches the room.
Information warfare is the contest to define meaning at speed. A true fragment can be stripped of context. An unresolved claim can be repeated as fact. Five headlines can look like five confirmations even when all five descend from one original report.
The answer is not louder messaging. It is a faster, visible chain from source to claim, from claim to evidence, and from evidence to a public explanation.
02 / How pressure forms
One event. Five transformations.
- 01
Event
Something happens in the physical world.
- 02
Fragment
A partial image, quote, or claim becomes the first usable unit.
- 03
Amplification
Repetition increases visibility and can imitate independent confirmation.
- 04
Perception
The repeated frame becomes the lens through which later facts are interpreted.
- 05
Pressure
Public belief influences institutions, policy, and freedom of action.
Reach of the frame →. The facts have not changed.
03 / The independence test
Repetition is not corroboration.
The system groups syndicated copies under their upstream source family. Five copies of one wire report count as one origin, not five independent confirmations.
Five copies → one origin. Syndication, not corroboration.
04 / The Lions of Zion system
From open signal to public record.
Collection is automated and continuous. The evidence chain remains visible. Every public article can be corrected, removed, and traced back to its supporting material. Select any stage to inspect its inputs, outputs and guarantees.
This map describes how the system is built, with live state drawn only from the public record. Per-stage job telemetry is internal and we would rather draw nothing than draw a number we cannot show you: each stage below reports “No telemetry available” for its live state. What the system has actually produced is public — every entry is in the updates feed, and every checked claim is on the fact-check desk.
01collect
Source
Public reporting enters through monitored search queries and verified feeds.
Every source belongs to a named family. That is what lets five syndicated copies of one wire report be counted as one origin instead of five.
Stage details
- Job stage
- collect
- Inputs
- RSS/Atom feeds, official APIs, discovery queries over a bounded domain corpus.
- Outputs
- Raw fetch records queued per source.
- Live status
- No telemetry available — per-stage job state is internal.
02collect + enrich
Ingestion
Each result keeps its publisher, URL, retrieval time, and original source family.
Provenance is append-only in the database. A record of where something came from and when it was fetched cannot be edited afterwards, only added to.
Stage details
- Job stage
- collect + enrich
- Inputs
- Raw fetches from collection.
- Outputs
- Normalized evidence rows with provenance.
- Live status
- No telemetry available — per-stage job state is internal.
03cluster
Detection
Relevant stories, atomic claims, duplicates, and candidate narratives are separated.
Reports of the same event are clustered before anything is written about them, so volume never reaches an editor disguised as corroboration.
Stage details
- Job stage
- cluster
- Inputs
- Enriched evidence packet for the edition.
- Outputs
- Event clusters, duplicate groups, candidate narratives.
- Live status
- No telemetry available — per-stage job state is internal.
04triage + draft
Analysis
A claim is assessed against the material on record, and the assessment states what it could not establish.
An assessment scores ten separate confidence dimensions, and a database constraint refuses one that leaves its known gaps blank. Once written it is immutable: a changed finding is a new assessment, not an edited one.
Stage details
- Job stage
- triage + draft
- Inputs
- Clustered evidence.
- Outputs
- Draft assessments with stated gaps.
- Live status
- No telemetry available — per-stage job state is internal.
05draft
Evidence
Supporting and contradicting material stays attached to the statements it bears on.
A publication is refused unless every passage cites the evidence under it. The single exception is a Narrative Watch record published as our own analysis, which must cite nothing anywhere — never partly.
Stage details
- Job stage
- draft
- Inputs
- Draft assessments.
- Outputs
- Passages with attached citations.
- Live status
- No telemetry available — per-stage job state is internal.
06quality + publish gate
Verification
Nothing publishes on the say-so of whoever wrote it.
A database trigger holds the gate, so no code path reaches publication around it. An editor's publication must be approved by a human who is not the author. An automatic one must carry its run provenance and have passed all twelve named quality checks — and may not also claim human approval.
Stage details
- Job stage
- quality + publish gate
- Inputs
- Cited drafts.
- Outputs
- Gate decision: approved, returned, or blocked.
- Live status
- No telemetry available — per-stage job state is internal.
07publish
Publication
The record goes public, and stays correctable.
Every published record is versioned and every version is kept. A correction is a new version with a stated reason, and the history travels with the record rather than replacing it.
Stage details
- Job stage
- publish
- Inputs
- Approved editions.
- Outputs
- Daily Brief, updates feed, fact-check desk entries.
- Live status
- No telemetry available — per-stage job state is internal.
05 / What is happening now
Recent pipeline activity — the public record.
The pipeline’s internal job monitor is staff-only. What follows is what it has actually published: the newest public records, each reachable and traceable.
06 / From signal to intelligence
One signal, eight steps, under a minute to grasp.
Follow a single post from detection to the public record. Illustrative in shape; every published instance of it is linked from the activity and output sections.
Detected
A post or article is collected from a monitored source.
Attributed
Its publisher, URL, retrieval time and source family are recorded.
Extracted
The atomic claim is separated from commentary around it.
Clustered
Copies of the same report merge under one origin; volume cannot pose as corroboration.
Verified
The claim is checked across sources against primary material.
Scored
Confidence is assessed across ten dimensions, gaps stated in writing.
Gated
A second human — or twelve automated checks with run provenance — must approve.
Published
The finding joins the public record, versioned and correctable.
07 / Narrative intelligence
How narratives emerge.
Individual signals
Collected posts and articles, each with publisher, URL and retrieval time.
Semantic clusters
Reports of the same event merge; duplicates never count as corroboration.
Narrative
A persistent frame across clusters — the story the copies are telling together.
Intelligence assessment
Growth, source diversity and evidence status are weighed; gaps are stated in writing.
The number that matters is distinct source families, not account or copy counts. Twenty accounts in one family are one megaphone; three accounts across three families are a story actually spreading. Velocity, volume and reach figures are reported by platforms — and the most gameable number a hostile actor controls — so this page draws no dials for them.
08 / Claim and fake analysis
Suspicion is a process, not a verdict.
Complex verification is never reduced to a bare true/false. Uncertainty is written into the assessment — and only the summary reaches the public record.
Claim detected
An atomic claim is separated from the surrounding coverage.
Source analysis
The publisher's family and upstream origin are resolved.
Primary-source search
Original footage, documents or statements are sought first.
Cross-source comparison
Independent families are weighed; syndicated copies count once.
Context check
Date, place and translation are tested for recycled or stripped context.
Evidence assessment
Ten confidence dimensions are scored; unknown gaps are written down.
Verdict with confidence
A summary verdict publishes with its evidence chain — never a bare true/false.
09 / The daily intelligence cycle
Continuous intake, one daily edition.
- ContinuousCollection walks every active source, every 30 minutes.
- 10 and 40 pastNew documents are embedded for semantic search.
- Every 15 minutesThe outbox drains: re-indexing and cache invalidation.
- DailyCluster → triage → draft → quality → publish builds the edition.
- From 10:00 Israel timeThe edition is expected; a missing edition raises a critical alert.
- Nightly 03:20Maintenance: stuck-job recovery, data pruning, alert hygiene.
Collection never sleeps; the edition is daily. That is the whole rhythm: a continuous intake, one published brief per day, and a public record that stays correctable afterwards.
10 / The output
Evidence must travel.
The system turns a daily field of public signals into three readable outputs: a strategic brief, a chronological record of everything published, and a desk of checked claims with the sources each one rests on.