Aaron D. Lee 6325e86873

CI / lint (push) Failing after 1m1s

Details

CI / typecheck (push) Failing after 31s

Details

Comprehensive documentation for v0.2.0 release

README.md (700 lines):
- Three-tier deployment model with ASCII diagram
- Federation blueprint in web UI routes
- deploy/ directory in architecture tree
- Documentation index linking all guides

CLAUDE.md (256 lines):
- Updated architecture tree with all new docs and deploy files

New guides:
- docs/federation.md (317 lines) — gossip protocol mechanics, peer
  setup, trust filtering, offline bundles, relay deployment, jurisdiction
- docs/evidence-guide.md (283 lines) — evidence packages, cold archives,
  selective disclosure, chain anchoring, legal discovery workflow
- docs/source-dropbox.md (220 lines) — token management, client-side
  hashing, extract-then-strip pipeline, receipt mechanics, opsec
- docs/index.md — documentation hub linking all guides

Training materials:
- docs/training/reporter-quickstart.md (105 lines) — printable one-page
  card: boot USB, attest photo, encode message, check-in, emergency
- docs/training/emergency-card.md (79 lines) — wallet-sized laminated
  card: three destruction methods, 10-step order, key contacts
- docs/training/admin-reference.md (219 lines) — deployment tiers,
  CLI tables, backup checklist, hardening checklist, troubleshooting

Also includes existing architecture docs from the original repos.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-01 23:31:47 -04:00

1.9 KiB

Raw Blame History

Emergency Reference Card

Audience: All SooSeF users. Print, laminate, and carry in your wallet.

EMERGENCY DATA DESTRUCTION

Option 1: Pull the USB (Tier 1 -- fastest)

Remove the USB stick from the laptop. The laptop retains zero data.

Option 2: Software killswitch

In the browser: Fieldkit > Emergency Purge > type CONFIRM-PURGE > click Purge

From a terminal:

soosef fieldkit purge --confirm CONFIRM-PURGE

Option 3: Hardware button (Raspberry Pi only)

Hold the physical button for 5 seconds.

DESTRUCTION ORDER

The killswitch destroys data in this order (most critical first):

Ed25519 identity keys
AES-256 channel key
Session secrets
User database
Attestation log and chain
Temp files and audit log
Configuration
System logs
All forensic traces (bytecache, pip cache, shell history)
Self-uninstall

On USB: the LUKS encryption header is destroyed instead (faster, more reliable on flash).

DEAD MAN'S SWITCH

If enabled, you must check in before the deadline or all data will be destroyed.

Check in: Browser > Fieldkit > Check In

Or: soosef fieldkit checkin

If you cannot check in, contact your editor. They may be able to disarm it remotely.

KEY CONTACTS

Role	Name	Contact
Admin	_________________	_________________
Editor	_________________	_________________
Legal	_________________	_________________
Technical support	_________________	_________________

Fill in before deploying. Keep this card current.

REMEMBER

Pull the USB = zero trace on the laptop
Keys are destroyed first = remaining data is useless without them
The killswitch cannot be undone
Back up your keys regularly -- if the USB is lost, the keys are gone
Never share your passphrase, PIN, or LUKS password over unencrypted channels

1.9 KiB Raw Blame History