b1a35783bb
- Merge Infrastructure + Secure + Systems → SNS Networking (Business #1) - Merge Web + Software + Cloud → SNS Digital (planned) - SNS Support unchanged (planned) - Add infra/ folder with 16 FOSS-first buildable designs - Update all agent knowledge, division briefs, legal structure - Restructure businesses/ from 7 to 3 operating folders
3.0 KiB
3.0 KiB
KNOWLEDGE — SnS Businesses
Why I keep this: to route and scope every piece of work to the correct SNS entity, protect the liability shield (each business is a separate LLC), and keep contracts and books clean. When a request or a business report comes in, I check it against these scopes.
The entities
| # | Entity | Scope — what it does | Boundary — what it does NOT | Liability | Status |
|---|---|---|---|---|---|
| 00 | SnS Network Solutions Holdings LLC (parent) | Owns brand/IP + 100% of each subsidiary | No client work; no operating liability | None (by design) | — |
| 01 | SNS Networking LLC | Physical networking, cabling, wireless, security (cameras, access control, cyber), on-prem servers/virtualization/Linux — if it touches the network, protects it, or runs on-prem compute | Not cloud/off-prem (Digital), not recurring managed contracts (Support), not websites/apps/code (Digital) | High (physical + cyber E&O) | ACTIVE (Business #1) |
| 02 | SNS Digital LLC | Cloud infrastructure (AWS/Azure), websites, hosting, custom software, automation, CI/CD — anything code, cloud, or web | Not physical/on-site work (Networking), not recurring managed contracts (Support) | Medium (professional E&O) | Planned |
| 03 | SNS Support LLC | Managed services, helpdesk, RMM, monitoring, SLAs — maintains what Networking and Digital build. ALL recurring/managed contracts live here | Not net-new build (that's Networking or Digital) | Med–High (SLA) | Planned |
Boundary rules (the lines I enforce)
- Build vs. maintain: Networking and Digital build; Support maintains. Any recurring or managed contract belongs to Support — not the builder.
- Physical vs. digital: On-site work (wire, servers, cameras, firewalls) = Networking. Remote/code/cloud work (apps, websites, AWS) = Digital.
- One job may touch multiple entities — then it is split, and each part is scoped, contracted, and billed under its own LLC. Never run one entity's work under another's name.
Scope-bleed examples (catch and correct these)
- A "manage our network monthly" ask landing on Networking → the managed part is Support.
- A cloud migration filed under Networking → belongs to Digital.
- A hosting-with-SLA website job under Digital → build is Digital, the SLA/managed part is Support.
- A camera install being scoped as Digital work → physical install belongs to Networking.
- A client wanting a custom app + on-prem server → server is Networking, app is Digital.
What each business reports on (when it reports)
Work in progress · new requests/leads · blockers · anything crossing entity lines · anything needing Sam (money, legal, pricing, external comms).
Source & upkeep
Summarized from the SNS division briefs and legal-structure.md in the sns-network-solutions
repo. Update this file if a division's scope, boundary, or status changes.