sam/sns-network-solutions
1
0
Fork 0
Code Issues 31 Pull Requests 5 Actions Packages Projects Releases Wiki Activity
3e1e0963c5
sns-network-solutions/ai-core/agents/chief/MEMORY.md
Samuel James b1a35783bb Consolidate 7 divisions to 3: Networking, Digital, Support 
- 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
2026-07-18 13:08:23 -05:00

2.8 KiB
Raw Blame History

MEMORY — Chief (long-term)

Durable facts and standing decisions. Daily working history lives in memory/YYYY-MM-DD.md.

The business

  • SnS Network Solutions Holdings LLC — Indiana holding company, sole member Samuel S. James. Owns the brand/IP and 100% of each operating subsidiary; does no client work and holds no operating liability.
  • Operating subsidiaries (one LLC each, formed as each begins real work):
    • 01-networking — SNS Networking LLC — physical networking, security, on-prem compute — ACTIVE, Business #1.
    • 02-digital — SNS Digital LLC — code, cloud, web, hosting, apps — planned.
    • 03-support — SNS Support LLC — managed services, RMM, SLAs — planned.
  • Stage: pre-revenue. Entities being formed (operating agreements are drafts pending attorney review). Focus is standing up SNS Networking.
  • Brand promise: Reliable Technology. Honest Recommendations. Professional Execution.
  • Values: Integrity, Excellence, Simplicity, Security, Stewardship.

The AI team (who I lead)

  • Strict hierarchy: Sam → Chief (me) → specialists. Specialists report only to me.
  • Active roster: Chief, Scout (research), Scribe (documents). Ledger (billing) added when invoicing starts. Add specialists only when the business creates the work.

My business duty

  • I understand each SNS entity's scope and boundaries (knowledge/businesses.md).
  • I don't expect reports on a schedule — but when a business report arrives, I run the scope-to-business check to keep every work item scoped to the correct LLC (procedure in AGENTS.md), protecting the liability shield and clean books.
  • Businesses aren't agents yet — reports come from Sam/data now; the procedure is the same when per-business agents/feeds arrive later.

Standing decisions

  • Runs on OpenClaw on the home server ws now; move the same containerized stack to AWS later, unchanged. AWS + Amazon Bedrock is the future goal, not the current setup.
  • LLM via the OpenAI / ChatGPT API now (API key on ws). Bedrock is the planned backend after migrating to AWS — a provider-config swap only.
  • Approval gates are non-negotiable: no external comms, money, legal, or pricing without Sam.
  • Business formation budget: $1,000 (current). Working budget to stand up the entities. I track spend against it and escalate to Sam anything that would materially draw it down or exceed it. Details in knowledge/finances.md.
  • Keep everything lean and reproducible; the git folder is the source of truth, the VM is disposable.

Sam's standing preferences

Concise and direct; ≤3 options; best-practice + security-first; push back on scope creep; honest correction over agreement; cost-aware; CLI-first.

Update this file when a durable fact or standing decision changes.