◇ doctrine :: three bindings

What this operation refuses to do, written down.

Every page on this site footnotes three words: consent-required · passive-preferred · shield-not-sword. This page exists so those words are quotable, citable, and verifiable — not as vibes, but as standing decisions the operator made before you arrived and will not bend for any single engagement.

binding 01 :: consent-required
Consent-required
Nothing happens to you, about you, or on your behalf without your explicit ask.
No cold outreach. No surprise interventions. No third-party introductions made without your knowing yes. No screenshots of your message shared. No off-the-record notes turned into public posts. The Brief format exists because it forces every engagement to start with an explicit, written ask from you — not from a friend, not from a family member, not from an algorithm.
// in practice
- +Every engagement begins with a Brief you submitted yourself.
- +Your name, your situation, and your contact details are never surfaced anywhere you didn't sign off on.
- +If a third party (family, partner, employer) reaches out about you, the operator will not act on their request until you have personally confirmed it.
// refuses
- −Concerned-family interventions where the subject hasn't asked for help.
- −"I'd like to gift this support to my friend" — gifts go to people who already opted in.
- −Public commentary on individuals who have not consented to be named.
binding 02 :: passive-preferred
Passive-preferred
When two responses solve the problem equally, the one that adds less to the world wins.
The operator does not believe the answer to most problems is more activity, more content, more outreach, more posts, more meetings, or more software. Passive-preferred means: prefer the smaller intervention, the quieter system, the one-time fix over the ongoing subscription, the deletion over the addition. This is not minimalism as aesthetic — it is a working hypothesis that most clients arrive over-stimulated and most situations are over-engineered.
// in practice
- +Briefs default to the smallest scope that resolves the stated problem.
- +HelmKit is local-first by design — no servers, no telemetry, no accounts.
- +Recommendations more often subtract (cancel this, archive that, stop doing this) than add.
// refuses
- −Retainer arrangements that exist mainly to bill recurring hours.
- −Software builds that add a subscription where a one-time tool would do.
- −"Let's set up a weekly check-in" — only if the work genuinely needs one.
binding 03 :: shield-not-sword
Shield-not-sword
The work defends, deflects, and removes harm. It does not attack, retaliate, or coerce.
Operator support is for protecting yourself, your data, your time, your relationships, and your sanity from things that are pressing on them. It is not for going after people, for organizing retaliation, for OSINT-as-stalking, for reputational warfare, or for any work whose primary effect is to do harm to a third party — even a third party who has wronged you. This binding is non-negotiable and predates any single engagement. If a Brief reads as sword-shaped, it gets declined with an explanation, not a counter-offer.
// in practice
- +Defensive OSINT ("who is doxxing me / what's exposed about me?") is in scope.
- +Harm-reduction routing (crisis lines, legal aid pointers, safer alternatives) is in scope.
- +Strategic withdrawal, account hardening, and quiet exits are in scope.
// refuses
- −Offensive OSINT targeting an individual.
- −Help with retaliation, doxxing, harassment campaigns, or reputational sabotage.
- −Any work whose stated goal is to make a specific person suffer, even one who deserves it.

// citation

These bindings predate this website and apply to every engagement under the Archangel Agency LLC umbrella. They are not subject to per-client negotiation. To quote: link to the section anchor (e.g. /doctrine#consent-required).

Questions about scope, edge cases, or whether a specific situation falls inside or outside these bindings: ask via /connect before submitting a Brief.