Who is the stack for?
- Individual
- Household / oikos
- Merchant / business
- Local cell / community
- Institution / clinic / school / other
Direct channels only.
First contact is Nostr only. Keep it written, brief, secret-free, and focused on classification rather than oversharing.
Use the smallest safe first message.
State who you are, what unit you represent, what pressure exists, and what you think the next step is. Early contact is for fit, trust, and scope classification — not for dumping the whole stack into an unsafe channel.
Classify the unit and the pressure first.
Where is the pressure?
- Family continuity / inheritance / spouse or heir usability
- Merchant / payments / records / operator burden
- Communications / privacy / work constraints
- Local economic mesh / meetup / community coordination
- Care / clinic / education / resilience / other material layer
What is biting now?
Hidden dependency, fragility concentration, recovery weakness, hybrid compromise, staff or spouse misalignment, succession anxiety, degraded-mode fear, or another specific pressure surface.
What shards already exist?
Name what is already in place, what is already hybrid or compromised, and what you are afraid of breaking by moving too fast.
How did you find SSDC?
- Referral
- Meetup / local node
- Media node / podcast / article
- Campus / hub
- Vertical builder
- Other
Nostr
Nostr
npub1ad0h4776rf2eh2swdz6dxw5upxk963g52g3yyh83e99z8dvu6g4q09c7zj
Use Nostr for first contact. Keep the first message minimal: unit form, pressure lane, current choke point, and likely next step.
First message
Do send
- Who you are, what unit form you represent, and roughly where you are operating from.
- The pressure lane: family continuity, merchant / payments, communications / privacy, community coordination, care / clinic, resilience, or another real surface.
- The current choke point: where the stack feels captured, fragile, overburdened, or confusing.
- What you think you need now: Triage, Blueprint, or a short fit check.
- What parts of the stack are already in place and what is already hybrid or compromised.
- How you found SSDC if relevant: referral, meetup, media node, campus / hub, vertical builder, or other.
Do not send
- Seed phrases, private keys, passwords, or password-manager exports.
- Admin credentials, raw private-message archives, or unrelated personal archives.
- A giant unsorted dump of screenshots, documents, and notes in the first message.
- Anything you would not want sitting in the wrong relay, client, or transcript.
Trust and next step
Trust boundary
Not every message becomes an engagement. Messages are reviewed manually for fit, trust, scope, and obvious risk. The wrong information should never need to cross the boundary in the first place.
Next step
A pre-engagement threat questionnaire may be required before anything further for people not already known or trusted.
The first paid engagement, when there is a fit, is Triage. That is how SSDC determines whether the honest next move is self-remediation, Blueprint, a later specialist, a bounded follow-on, public docs, or nothing at all.