sns-network-solutions/README.md
Samuel James 6d76305c6d Regroup parent repo: businesses/ by importance, divisions/ formal docs
- Move infrastructure into businesses/00-infrastructure; add 01-06 numbered dirs
  ordered by importance (secure, support, systems, cloud, web, software)
- Add per-business branding.html (accent color scheme + ChatGPT logo prompt)
- Add NN-name.md scaffold/research/todo docs for the six planned divisions
- Make divisions/ the formal-docs library: parent + infrastructure briefs,
  legal-structure, investment-research
- Add root README map and businesses/ index; empty READMEs per dir
- Fix all relative links broken by the moves
2026-07-16 12:38:16 -05:00

56 lines
2.8 KiB
Markdown

# SnS Network Solutions
**Parent company repository.** SnS Network Solutions is a technology-infrastructure
company for small and medium organizations — networking, Linux systems, security,
cloud, managed services, web, and custom software — structured as a **holding
company** that owns a separate operating LLC per division.
This repo holds the **parent-company identity, legal structure, and the catalog of
divisions**. Each division becomes its own repo (with its own legal + insurance
paperwork) as it launches. Business #1, **SNS Infrastructure**, is active.
## Structure
```
sns-network-solutions/
├── sns.md Brand foundation — identity, values, palette, logo direction
├── branding/ Shared brand assets (logo art)
├── divisions/ Formal documentation library (the catalog)
│ ├── sns-network-solutions.md Parent company brief
│ ├── sns-infrastructure.md + six division briefs
│ ├── legal-structure.md Indiana holding-company formation plan
│ └── investment-research.md Owner investment research (reference)
└── businesses/ Working area — numbered by importance; each is repo-ready
├── 00-infrastructure/ ACTIVE — hiring, comp, cash-flow, branding, todo
├── 01-secure/ Planned
├── 02-support/ Planned
├── 03-systems/ Planned
├── 04-cloud/ Planned
├── 05-web/ Planned
└── 06-software/ Planned
```
## How it's organized
- **`divisions/`** = the formal documentation library — the parent-company brief,
the polished one-page brief for each division, plus the holding-company legal plan
and investment research.
- **`businesses/`** = the working area: scaffold, research, TODO, branding, and (later)
milestones. Directories are **numbered by importance**; each folder is self-contained
so it can lift out into its own repo when the division launches.
- **Branding:** all divisions share one identity (navy base) and differ only by a
signature accent color. Each business folder has a `branding.html` (color sheet +
a copy-ready ChatGPT logo prompt). Foundation: [`sns.md`](./sns.md).
## Start here
- New to the company → [`sns.md`](./sns.md) · parent brief [`divisions/sns-network-solutions.md`](./divisions/sns-network-solutions.md)
- Legal / entity plan → [`divisions/legal-structure.md`](./divisions/legal-structure.md)
- Division catalog → [`divisions/README.md`](./divisions/README.md)
- Active business → [`businesses/00-infrastructure/`](./businesses/00-infrastructure/)
- All businesses → [`businesses/README.md`](./businesses/README.md)
---
*Docs contain general business/legal/tax research, not professional advice — verify
with an Indiana attorney and CPA before relying on them.*