Signal Scan
Compact first-use object for orientation, checking, and contradiction detection.
Engine
The structured case-file engine for contested claims.
Civitas Engine turns a claim, article, thread, transcript, or post into a bounded case file that keeps support, conflict, and unresolved questions visible instead of flattening them into one model answer. Signal Scan is now live as the public first-pass object.
What the engine does
Takes a claim, article, thread, transcript, or post as the starting object.
Builds a structured case file instead of a generic chat answer.
Keeps support, contradiction, and uncertainty legible as separate states.
Escalates from quick orientation into deeper dossier and institutional work.
What it starts from
The public surface starts with claims, articles, threads, transcripts, and posts. The product stays case-centric, not dashboard-centric, because the underlying value is adjudication structure rather than generic AI access. The live Signal Scan route is the first public submission surface.
Public workflow
Input→
Signal Scan→
Dossier→
Institutional Pack
Public ladder
Dossier
Repeat depth for serious users who need more evidence structure, explanation, and follow-through.
Institutional Pack
Higher-governance path for heavier challenge, handoff, and review conditions.
March 27 owner-authored dossier exemplar
First real dossier exemplar
Public Memory / Atrocity Adjudication
A short-form monologue arguing that public remembrance in the West is ranked by power, race, and institutional sponsorship rather than distributed evenly across atrocity histories.
What the dossier examined
- The distinction between atrocity occurrence and atrocity remembrance.
- How schools, museums, memorial infrastructure, archives, and legal categories shape public grief.
- Where rhetoric about slavery, the Holocaust, Congo, Armenia, Herero/Nama, and Rwanda remains directionally strong but numerically unstable.
Tensions found
- The case is strong on hierarchy in remembrance, selective institutional grief, and slavery-afterlife continuity.
- It becomes weaker when cross-atrocity arithmetic is treated as a clean scoreboard.
- Race matters, but it is not the whole explanation for Holocaust centrality in Western memory.
What remained unresolved
- Which curricular systems and memorial infrastructures most clearly demonstrate the hierarchy being claimed.
- What comparison framework is rigorous enough when duration, killing, trafficking, and afterlife effects differ.
- How the engine should separate memory politics from historical arithmetic without flattening either one.
Why this is dossier-grade
- It mixes historical fact, memory politics, institutional analysis, and quantitative caution in one object.
- A yes or no scan would erase the real structure of the argument.
- The right product shape is a dossier that preserves force, limit, and unresolved state together.
First Signal Scan specimen cards
These compact specimen cards are tied to owner-frozen March 20 case-family anchors. The live Signal Scan route now publishes the first outward-facing owner-derived artifacts from this set, rather than leaving them as abstract examples.
These public examples are derived from owner-authored Civitas case material. Eval fixtures, EPI Rail specimen manifests, golden or tamper scenarios, benchmark harnesses, and Sanctuary Core validation traces are intentionally excluded.
Primary-source contradiction / clickbait compression
Input type
Article, clip, or post that compresses what a primary source actually said.
What the scan detects
Origin-to-propagation mismatch, overstatement, or reversal between the primary source and the circulated claim.
Why it matters
This is a public-legible first-wave case because it teaches the difference between claim origin, compression, and propagation behavior.
Output shape
A compact claim map, source-role split, compression note, and next verification step.
Tesla / R8 malformed comparison
Input type
Post, thread, or short argument built around a persuasive comparison that may break category logic.
What the scan detects
Comparison-frame failure, category mismatch, and analogy that sounds clever before the structure is tested.
Why it matters
The case shows that adjudication starts with claim structure and frame integrity before evidence scoring begins.
Output shape
A frame-integrity note, comparison warning, and bounded recommendation on whether the analogy survives review.
Produced authenticity / talent show
Input type
Clip, performance object, or commentary claim about authenticity, merit, or organic emergence.
What the scan detects
Where mediated performance, packaging, and institutional framing are being mistaken for raw authenticity.
Why it matters
Authenticity claims often hide framing claims, so the engine has to separate presentation from support.
Output shape
A framing note, authenticity-versus-packaging split, and recommendation on whether deeper dossier work is needed.
Chronology restoration / immigration speech
Input type
Speech clip, article, or thread where event order materially changes interpretation.
What the scan detects
Scrambled sequence between speech, event, reaction, and later framing.
Why it matters
Chronology restoration is one of the engine's strongest differentiators when narrative laundering depends on sequence confusion.
Output shape
A first-pass timeline, chronology conflict note, and signal that the case may need dossier depth.
Tucker-style unresolved opacity claim
Input type
High-salience claim where evidence remains partial, withheld, or too thin for clean closure.
What the scan detects
Opacity, evidentiary insufficiency, and conditions where disciplined unresolved state is more honest than a verdict.
Why it matters
This case family matters because the engine has to show when withholding judgment is rigorous rather than evasive.
Output shape
An unresolved state, visible evidence gaps, and a clear note on what would need to change before the case can close.
Outreach-ready live set
Each live artifact opens with a direct URL, a compact outreach line, and a send-this-case kit on the Signal Scan route.
Trust and limits
The engine does not force false closure.
Source roles and open questions stay visible.
Method and support surfaces remain public enough for review.
Proof and docs stay close to product use instead of being hidden in doctrine.
Packaging summary
Starter: hosted Signal Scan entry for first serious use.
Pro: recurring lane and the main revenue center for deeper work.
Teams / Early Access: deferred lane for heavier private or institutional handling.
Hosted versus BYOK
The launch posture is hybrid. Starter stays hosted. Pro stays hosted by default and becomes BYOK-capable where privacy, cost control, or repeat depth actually justify it. Teams remains later and custom.