CrisisCore Systems
About
I build privacy-first tools and protective frameworks for people operating under real instability: illness, displacement, coercion risk, partial connectivity, and low-trust environments.
Independent systems designer. Based in Vernon, BC.
I work across local-first architecture, threat modeling, security review, degraded-mode UX, and operational reliability.
Why this exists
Protective computing
Most systems are designed for a world where trust holds and conditions are stable. My work assumes the opposite.
The goal is not “perfect security.” The goal is a system that remains usable, safe, and legible when users are under stress and the environment is adversarial.
I’m not here to sell growth theater. I build systems that stay legible and usable when conditions turn hostile.
Operating principles
- •Local authority over defaults (users own their data and failure modes are explicit).
- •Degraded-first behavior (it should still work when the network and attention don’t).
- •Reversibility (users can undo; operators can roll back).
- •Explicit trust boundaries (who/what is assumed safe—and what is not).
- •Evidence over claims (repro steps, tests, and verifiable artifacts).
What I do (and don’t)
Do
- •Threat modeling and risk framing that matches adversarial reality.
- •Audits that produce actionable outputs (not theater).
- •Local-first / privacy-first product architecture.
- •Operator-ready docs: checklists, runbooks, verification steps.
Don’t
- •Sell compliance badges as security outcomes.
- •Make unverifiable claims about guarantees.
- •Build systems that require constant connectivity to be safe.
- •Optimize for vanity metrics over operator safety.
Mission plate
Engagement
I work best asynchronously and artifact-first. A short written context + constraints + links beats a meeting.
If coercion risk, compromised devices, or legal exposure are in play, say so early. Those conditions change the trust boundary from the start.
Operational note: avoid sending sensitive personal data by email. If you need a higher-safety channel, say so in the first message.