sns-network-solutions/README.md
Samuel James 55a80ce6e3 Move ai-core team into repo; relocate sns.md to ai-core/knowledge
- Add ai-core/ — Chief, Scout, Scribe OpenClaw agents + shared knowledge base
- Consolidate research/reference docs and the sns.md brand foundation under
  ai-core/knowledge/
- Repoint every sns.md reference (business branding, divisions, root README) to
  ai-core/knowledge/sns.md
- Update root + ai-core READMEs to reflect the new structure
2026-07-17 15:33:58 -05:00

60 lines
3.3 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/
├── ai-core/ Internal AI team + shared knowledge base
│ ├── agents/ chief · scout · scribe (OpenClaw agents)
│ └── knowledge/ sns.md (brand foundation) + research/reference docs
├── 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 — holding company + subsidiaries; each is repo-ready
├── 00-sns-holding/ Parent holding company (owns the brand + all subsidiaries)
├── 01-infrastructure/ ACTIVE — hiring, comp, cash-flow, branding, todo
├── 02-secure/ Planned
├── 03-support/ Planned
├── 04-systems/ Planned
├── 05-cloud/ Planned
├── 06-web/ Planned
└── 07-software/ Planned
```
## How it's organized
- **`ai-core/`** = the internal AI team — the Chief/Scout/Scribe OpenClaw agents — plus a
shared `knowledge/` base holding the brand foundation (`sns.md`) and research/reference docs.
- **`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: [`ai-core/knowledge/sns.md`](./ai-core/knowledge/sns.md).
## Start here
- New to the company → [`ai-core/knowledge/sns.md`](./ai-core/knowledge/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/01-infrastructure/`](./businesses/01-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.*