# 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 Infrastructure LLC** | Structured cabling, LAN/networking, wireless — the physical wire and foundation | Not cameras/security (Secure), not servers/OS (Systems), not cloud (Cloud) | High (physical/on-site) | **ACTIVE (Business #1)** |
| 02 | **SNS Secure LLC** | Cameras, access control, alarms (physical security) **+** cybersecurity (audits, firewall, monitoring, incident response) | Not the base LAN (that's Infrastructure) | High (physical + cyber E&O) | Planned |
| 03 | **SNS Support LLC** | Managed services, helpdesk, RMM, monitoring, SLAs — maintains what the others build. **ALL recurring/managed contracts live here** | Not net-new build (that's the builder division) | Med–High (SLA) | Planned |
| 04 | **SNS Systems LLC** | On-prem servers, Linux, virtualization, on-prem compute/storage | Not the wire (Infra), not off-prem (Cloud), not ongoing management (Support) | Medium | Planned |
| 05 | **SNS Cloud LLC** | AWS/Azure, hybrid, off-prem compute, migrations | Not on-prem (Systems); managed cloud is handed to Support | Medium | Planned |
| 06 | **SNS Web LLC** | Websites, hosting, domains, digital presence | Managed hosting SLAs coordinate with Support | Low–Med | Planned |
| 07 | **SNS Software LLC** | Custom apps, automation, integrations (client owns the code) | Not off-the-shelf resale | Medium | Planned |

## Boundary rules (the lines I enforce)
- **Build vs. maintain:** a division *builds*; **Support** *maintains*. Any recurring or
  managed contract belongs to Support — not the builder.
- **Where the compute lives:** the wire = **Infrastructure** · on-prem servers = **Systems**
  · off-prem = **Cloud**.
- **Security is its own entity:** cameras / access control / cyber = **Secure**, even on an
  Infrastructure job site.
- **One job may touch several 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 camera install being run under Infrastructure → belongs to **Secure**.
- A "manage our network monthly" ask landing on Infrastructure → the managed part is **Support**.
- A cloud migration filed under Systems → **Cloud**.
- A hosting-with-SLA website job under Web → build is **Web**, the SLA/managed part is **Support**.

## 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.