Duty-officer posture
2 OPEN TIER-1
Clocks running from recognition; verification never pauses Tier 1.
Open incidents
6
3 desk_staff · 2 election_official · 1 lamplighter
High severity
3
2 credible_threat
Election officials
2
1 Tier 1 active
Referred
4
LE 2 · platform 1 · counsel 1

Incident Log

DESK VIEW · ADMIRALTY-RATED · SUBJECTS: DEFENDERS ONLY
ALL OPEN HIGH-SEV ELECTION OFFICIAL DESK STAFF CREDIBLE THREAT
IDSubjectNatureSevStatusAdmiraltyConsentDuty officer

+ Log Incident

CONSENTING PARTNER OR DESK · NOT OPEN PUBLIC INTAKE

Confidentiality-override notice — read before filing

This record concerns a real person who may be at risk. Filing an incident may trigger the duty-to-warn state machine (see redoubt-duty-to-warn.md v1.0). If credibility indicators are present — especially approach behavior — the Tier-1 clock starts at recognition and notification proceeds without waiting for verification or leadership sign-off. Ordinary confidentiality and consent limits are overridden the moment a duty-to-warn threshold is met; that override is itself a logged decision, not a silent one.

Subjects are limited to the three defender types (desk staff, election official, Lamplighter). This is not a tool for filing on a private citizen — no such record type exists in this schema.

Only the three defender types. No "person of interest" option exists.
Required — a vetted partner org submits on the subject's consenting behalf.
Linking an incident to an attribution case is a separate, human, logged action — never automatic.
On "upload," a SHA-256 is computed and the append-only custody chain is opened.
SHA-256 (simulated)
Referral, not substitution — REDOUBT never replaces law enforcement.
Submit disabled until the confidentiality-override box above is checked.
Boundary invariants — this is the reference tool for boundary-as-code.
No private-citizen "person of interest" record type exists. Subjects are limited to the three defender types (desk_staff / election_official / lamplighter), each with a consent_ref.
Incident and attribution are never auto-linked. Any connection to an AZIMUTH case is a separate, human, audited action — reporter_belief is free text, not an attribution. No accusation register exists anywhere in this system.
Evidence is append-only and hash-verified; the custody chain cannot be edited — only extended.
← back to Log

RDT-0142

Full Record

DESK-GATED

Custody Chain

APPEND-ONLY · HASH-VERIFIED

Referral Status

ROUTING, NOT SUBSTITUTION

Duty-to-Warn State Machine

redoubt-duty-to-warn.md v1.0
TIER — (none assessed)
Clock: not started.

Record a non-warning (logged decision — never silent)

A non-warning requires both a reason and an actor — it cannot be recorded silently.