Scan · Classify · Preserve · Map · Escalate

Stage 02

Classify — categories, not verdicts about people

Each item is assessed against a defined taxonomy and returned with a category, a severity, a confidence value and the specific passages that support the reading. Model confidence and reviewer confidence are recorded separately, because they are different claims about different things.

The output is never “this person is antisemitic.” It is: this content, at this address, on this date, appears to meet this definition and to engage this rule, for these stated reasons.

Stage 03

Preserve — a record built to survive examination

Not a screenshot in a chat. A structured record built to an evidentiary standard: assembled so that someone who would prefer it fell apart can examine it and find that it does not.

What each field is for

1. Capture URI. The exact address the material was read from, stored in full. The public rendering is redacted; the vault copy is not.
2. Captured (UTC). The moment of capture and the response the server gave, in a single timezone, so two records from two countries can be compared.
3. Method. How the page was rendered and what was retained. Raw archives of whole sites are not kept; the record is the unit, not the crawl.
4. Extracted text. The readable text of the page, including text inside images. Material placed in a picture to escape a text filter does not escape this.
5. Translation. Attached, never substituted, and carrying its own confidence value. The original language is the record; the translation is an aid to reading it.
6. SHA-256. A digest computed over the preserved bundle. It does not protect the content. It proves the content has not changed since the moment it was sealed — which is why the button above recomputes it in front of you rather than asserting it.
7. Policy match. The specific rule engaged, recorded together with the version of that rule in force on the date of capture. Rules change; records should not have to.
8. Severity and confidence. Two separate scores, never merged. A severe item read with low confidence is not the same object as a mild item read with high confidence, and treating them alike is how monitoring systems lose their credibility.
9. Chain of custody. An append-only log of every action taken on the record — capture, review, decision, escalation — with the person and the system version responsible for each. Nothing can be quietly amended. Nothing can be silently deleted.

Stage 04

Map — one page is an incident

Preserved records are the beginning. Held together, they show what a single report can never show: which sites recycle each other, which text reappears in four languages, which domains keep resurfacing under new names, and which of them are being paid.

That is the difference between reporting a page and being able to describe the thing the page belongs to.

Stage 05

Escalate — the ladder, and where it stops

This stage is last because it is a consequence, not a purpose. Civic Shield is built to produce evidence; enforcement is what evidence of that quality lets other people do, and the people entitled to do it are platforms, regulators, service providers and lawyers — not us.

The ladder below describes what a completed record makes possible. None of it has been exercised: no notice has been sent, no regulator contacted, no case file produced. If the record is not good enough to stand on its own, nothing on this ladder is available at all.