Services / Prices / Scope

Build the next layer of your Sov Stack without creating a new dependency.#

Freedom needs infrastructure.

Conviction, tools, Bitcoin, Nostr, FOSS, privacy apps, self-hosting, hard money, local food, and correct opinions can all matter.

They become freedom only when a real life function moves into a system the right people can operate, recover, repair, teach, and hand off when life hits.

SSDC’s first services are written reviews for people already trying to build the exit.

The review names the function under pressure, the captured substitute still carrying it, the burden, the false strength, the adjacent systems, the professional boundary, and the next sane move.

Written review comes before architecture.

Blueprint comes only when earned.

Current services#

Pricing tiers#

Access pricing keeps the path reachable.

Standard pricing is the normal rate.

Pay-It-Forward pricing helps keep the lower-cost path alive for serious people with less cash.

Free — Signal Note#

A Signal Note is free triage.

It is for the person who knows something in the stack needs attention but does not know where the first move should land.

A Signal Note uses one short summary to identify the visible pattern and route the next move.

It may name:

• the apparent area;
• the first visible pressure point;
• the move to avoid first;
• whether a professional boundary appears;
• whether the next route is free material, Micro Audit, Basic Sov Stack Audit, Full Sov Stack Audit by acceptance, outside professional, refusal, pause, or no further action.

Signal Note exists to stop a bad first move before the client exposes too much, buys the wrong service, or starts changing the wrong part of the stack.

Signal Note routes the first summary.

It is not an Audit.

Paid — Micro Audit#

A Micro Audit is the smallest paid written review.

Use it when one narrow weak point is visible and the question is still small.

Examples:

• the family recovery path is unclear;
• the Bitcoin setup depends too much on one person;
• the business depends on one payment processor;
• the records are scattered;
• the self-hosted setup cannot be restored by anyone else;
• the customer-contact path depends on one inbox;
• the payment/refund process depends on the owner.

Micro Audit answers:

• what narrow weak point is visible;
• what substitute is currently being relied on;
• what breaks first;
• who carries the burden now;
• what can be judged from safe information;
• what remains unknown;
• what should stay still;
• what belongs outside SSDC;
• what the next sane move is;
• whether a Basic or Full Sov Stack Audit is justified.

Micro Audit names the weak point, the visible burden, and the next sane move.

It is short because the scope is narrow.

Paid — Basic Sov Stack Audit#

A Basic Sov Stack Audit is the first full written Audit tier.

It is for one narrow pressure point inside the stack.

Use it when one weak point is visible and the situation needs more than a Micro Audit but is still narrow enough to isolate.

Examples:

• custody depends too much on one person;
• family records exist but no one knows what matters first;
• merchant payments exist but refunds, receipts, and records still run through one owner-held workflow;
• self-hosting works but only one operator can restore it;
• a local group has people and conviction but no clean treasury, role, or handoff structure.

A Basic Sov Stack Audit judges:

• what narrow part of the stack is under review;
• what currently carries that part;
• what ordinary failure would expose;
• who carries the burden now;
• what becomes unclear if that person is unavailable;
• what remains unknown;
• what should stay still;
• what belongs outside SSDC;
• what the next sane move is;
• whether a Full Sov Stack Audit is justified.

Output: 1–2 written pages.

Acceptance only — Full Sov Stack Audit#

A Full Sov Stack Audit is a deeper written review across multiple connected parts of one accepted stack.

Full is used when Basic would give a false answer because the pressure is connected.

The key word is connected.

A Full Sov Stack Audit may fit when:

• household custody, records, recovery, roles, and handoff are tied together;
• merchant payment fallback affects receipts, refunds, customer contact, staff workflow, and accounting;
• records, communication, identity, and recovery cannot be judged separately;
• self-hosting depends on technical administration, documentation, restore proof, and second-operator readiness;
• a local cell has treasury, roles, communication, conflict, members, and succession tangled together.

Full reads the connection pattern.

It judges:

• the accepted review focus;
• the connected parts that must be read together;
• where one part silently carries another;
• where control actually sits;
• where continuity breaks across the connection;
• where operator burden is concentrated;
• where privacy, recovery, and handoff collide;
• what should stay still;
• what should simplify;
• what may need outside professional decision;
• what sequence is safe enough to consider;
• whether Blueprint is earned, premature, unnecessary, or unsafe.

Output: 6–10 written pages.

Earned only — Sov Stack Blueprint#

A Sov Stack Blueprint is a build plan after Audit proves architecture is needed.

Blueprint may define:

• the target state;
• what moves first;
• what stays still;
• the sequence;
• the roles;
• the ownership logic;
• the handoff path;
• the professional boundaries;
• the failure drills;
• the closeout standard.

Blueprint is not sold as the front door.

Architecture before review creates fantasy and capture.

Review first.

Blueprint only when earned.

What payment buys#

Payment buys a bounded written artifact.

It may buy:

• accepted scope;
• written judgment;
• dependency map at the category level;
• burden map;
• failure-mode identification;
• do-not-touch-yet list;
• professional-boundary routing;
• next-step judgment;
• Blueprint eligibility or non-eligibility;
• closeout.

Payment buys the artifact inside accepted scope.

It does not turn SSDC into custody, admin, implementation, emergency response, professional substitute, platform membership, certification, or ongoing support.

That boundary is how the work stays sovereign.

Where to begin#

Use Start Here before sending the first summary.

Start Here