Contact

Email-first. Engagements typically map to: Trust Hardening Review, Hardening Sprint, or Fractional Trust Architect support.

Start here

Send repo + context for fit check

Fastest path: email. Include context, constraints, and any repo or deployment links; I’ll reply with next steps and whether the engagement looks like a fit.

crisiscore.systems@proton.me GitHub ↗Proof

Trust Hardening ReviewHardening SprintFractional Trust Architect

Operational note: avoid sending sensitive personal data by email. If you need a higher-safety channel, say so in the first message.

Direct email: crisiscore.systems@proton.me

What to include

•What you’re building (or auditing) and for whom.
•Your operating reality: instability factors, threat model, and constraints.
•Timeline + decision point (what would ‘done’ look like).
•Links to artifacts: repo, docs, screenshots, DOI, or deployment.

Tip: the email button above pre-fills a short template. A concise artifact-first note beats a polished pitch.

Inquiry template

Context:
- What you are building and who it serves

Need:
- Trust Hardening Review / Hardening Sprint / Fractional Trust Architect

Constraints:
- Timeline
- Budget range
- Security or compliance boundaries

Artifacts:
- Repo / docs / deployment links

Decision target date:
-

Response expectations

I aim to respond within 1–3 days. If you’re in an urgent window, put URGENT in the subject line and include your deadline.

I prefer verifiable artifacts over long calls: a short description, constraints, and links beat a meeting.

For operators

If your environment includes coercion risk, compromised devices, or legal exposure, say so early. We’ll treat threat boundaries as first-class.

Protective computing is constraint-led. “Normal” assumptions are optional.

Web form fallback

If the email button doesn’t open a client on your device, use this form to generate and send your inquiry via webmail.

Open in Gmail ↗Open in Outlook ↗

Fallback path for devices without a configured local mail client.