206 lines
9.0 KiB
Markdown
206 lines
9.0 KiB
Markdown
# SnS Business Context and Decision Memory
|
|
|
|
This is Codex's detailed, durable context for Samuel James's business planning
|
|
center. The root `AGENTS.md` is the automatic entrypoint; this file holds business
|
|
direction, priorities, patterns, and owner-confirmed decisions.
|
|
|
|
Keep this current but compact. It is not a transcript, task backlog, secret store,
|
|
or replacement for signed legal records.
|
|
|
|
## Owner objective
|
|
|
|
Build family legacy and family wealth through a portfolio of independently operated
|
|
businesses and appreciating assets. The portfolio should increase Sam's freedom and
|
|
must not create a collection of jobs that depend on his daily labor.
|
|
|
|
### Owner role
|
|
|
|
- Owner
|
|
- Capital allocator
|
|
- Strategist
|
|
- Systems designer
|
|
- Final approver for material decisions
|
|
- Never the permanent daily operator
|
|
|
|
## Governing principles
|
|
|
|
1. Take the most direct route to the goal: the shortest useful path between two points.
|
|
2. Use data rather than emotion, optimism, or hope. Hope is not a business strategy.
|
|
3. If a process works, change it only when the change saves meaningful time or money.
|
|
4. Automate reliable repetitive work using tools already available.
|
|
5. Work smarter, not harder; protect and increase Sam's time.
|
|
6. Build on Biblical and Godly principles.
|
|
7. Include a 10% tithe to a church in profit-allocation planning, with CPA review of
|
|
bookkeeping and tax treatment.
|
|
8. Prefer one strong recommendation over many weak possibilities.
|
|
|
|
## Holdings doctrine
|
|
|
|
SnS Network Solutions Holdings exists to hold assets for long-term family legacy and
|
|
family wealth.
|
|
|
|
Non-negotiable owner decision:
|
|
|
|
- Holdings never borrows.
|
|
- Holdings never carries debt.
|
|
- Holdings never holds a credit card.
|
|
- Holdings holds assets only.
|
|
|
|
Do not recommend placing operating liabilities, routine vendor contracts, payroll,
|
|
consumer-facing activity, or operating-company borrowing in Holdings. Any guarantee,
|
|
cross-collateralization, lien, or structural exception requires Sam's explicit choice
|
|
after attorney and CPA review.
|
|
|
|
## Venture priorities
|
|
|
|
| Priority | Venture | Current direction |
|
|
|---:|---|---|
|
|
| 1 | SnS Hospitality Group / The Daily Pour | Active focus; launch T00-DRIP and prove the unit |
|
|
| 2 | SnS Properties | Build asset ownership and family wealth after/alongside disciplined Hospitality progress |
|
|
| 3 | Technology and networking services | Develop as an operator-independent services business |
|
|
| 4 | SnS Creative | Future media, music, podcast, and related creative activity |
|
|
|
|
Priority means allocation of attention, planning effort, and execution sequencing. It
|
|
does not authorize spending or legal formation.
|
|
|
|
## Source-of-truth design
|
|
|
|
Owner-confirmed direction as of 2026-08-27:
|
|
|
|
- This Git repository becomes the authoritative business planning center.
|
|
- The repository is standalone at `~/Documents/SnS Network Solutions/`.
|
|
- Git records change history.
|
|
- Selected repository files should synchronize with Google Drive in both directions.
|
|
- Signed agreements and execution records may remain in cloud systems, with their
|
|
status and canonical location recorded here.
|
|
- Plane is expected to be retired; preserve useful project data before removal.
|
|
|
|
Recommended implementation direction:
|
|
|
|
- Keep Git authoritative for planning documents, structured data, and generated
|
|
business artifacts.
|
|
- Keep signed/executed originals authoritative in their execution or approved cloud
|
|
system.
|
|
- Define an explicit synchronization manifest rather than syncing the entire repo.
|
|
- Use conflict detection; never allow unattended last-writer-wins overwrites between
|
|
Git and Google Drive.
|
|
- Export Plane data into the appropriate entity's `projects/` area before retiring it.
|
|
|
|
The physical repository move was completed on 2026-08-28. Synchronization automation
|
|
is not yet completed.
|
|
|
|
## Document authority and lifecycle
|
|
|
|
Use this order:
|
|
|
|
1. Owner's newest explicit decision
|
|
2. Signed/executed legal record or official agency record
|
|
3. Current approved specification, quote, or decision record
|
|
4. Current working plan
|
|
5. Historical draft, projection, mockup, or memory
|
|
|
|
When a new owner-confirmed decision supersedes an old document:
|
|
|
|
- Update the current source.
|
|
- Move obsolete versions to the relevant `archive/` area.
|
|
- Preserve dates and provenance.
|
|
- Update links.
|
|
- Never allow two files to appear equally authoritative.
|
|
|
|
## Standard business organization
|
|
|
|
Use the following only as content requires it:
|
|
|
|
| Area | Purpose |
|
|
|---|---|
|
|
| `README.md` | Current entity overview, status, navigation, and next gate |
|
|
| `decisions/` | Durable owner decisions and decision rationale |
|
|
| `legal/` | Formation, agreements, compliance, and canonical-record references |
|
|
| `finance/` | Budgets, models, actuals, funding, and asset allocation |
|
|
| `operations/` | SOPs, staffing, vendors, equipment, and recurring controls |
|
|
| `marketing/` | Brand, customer acquisition, content, and measured performance |
|
|
| `projects/` | Finite initiatives, milestones, checklists, and deliverables |
|
|
| `archive/` | Superseded material retained for history |
|
|
|
|
Avoid empty scaffolding. Prefer clear filenames, one current version, and relative
|
|
links from the entity README.
|
|
|
|
## Hospitality decisions
|
|
|
|
### Ownership
|
|
|
|
Owner-confirmed 2026-08-27:
|
|
|
|
- The legally guaranteed vested ownership is 85% Holdings / 15% Kiowa.
|
|
- Kiowa has options that may increase her interest up to 25% under the operating
|
|
agreement's terms.
|
|
- The operating agreement should state this distinction clearly.
|
|
- Do not describe Kiowa as currently owning 25% unless option conditions are completed
|
|
and formally recorded.
|
|
|
|
### Operating Agreement
|
|
|
|
- Sam confirms the Hospitality operating agreement is signed.
|
|
- The authoritative executed copy is stored in Documenso.
|
|
- Canonical location:
|
|
`https://app.documenso.com/t/personal_netzdizknkwzxrtl/documents/f/cmsatz9g26wtkad1w289yzsxf`
|
|
- The agreement contents were not independently readable by Codex on 2026-08-27.
|
|
- Repository drafts are not controlling when they conflict with the executed copy.
|
|
|
|
### Current Daily Pour gate
|
|
|
|
T00-DRIP remains pre-launch. Sam has hired a Fiverr designer for **$211** to produce
|
|
buildout blueprints and is waiting for their return.
|
|
|
|
The immediate execution sequence is:
|
|
|
|
1. Receive blueprint package and editable/source deliverables.
|
|
2. Check the package against the current equipment, workflow, weight, electrical,
|
|
plumbing, winterization, and service-clearance requirements.
|
|
3. Correct material defects before agency submission.
|
|
4. Submit through the applicable health/building review process and track corrections.
|
|
5. Resolve certified food-protection coverage and recruit the operating lead/barista
|
|
capability needed for launch.
|
|
6. Freeze the approved prototype specification before purchasing or irreversible
|
|
buildout.
|
|
|
|
A repository-backed HTML progress tracker is requested and should become the current
|
|
operational checklist for this gate.
|
|
|
|
## Communication pattern
|
|
|
|
- State the answer first.
|
|
- Use two words when two words are sufficient.
|
|
- Add detail only when it changes a decision, prevents a meaningful mistake, or creates
|
|
a reusable record.
|
|
- Do not give Sam long lists of suggestions that do not serve the overall goal.
|
|
- Choose the best option automatically from available evidence.
|
|
- Surface a second option only when it is genuinely competitive or the primary choice
|
|
depends on unresolved legal, financial, safety, or irreversible facts.
|
|
- Do not make Sam repeatedly explain decisions already captured here.
|
|
|
|
## Decision memory
|
|
|
|
| Date | Decision | Status |
|
|
|---|---|---|
|
|
| 2026-08-27 | Holdings exists for family legacy and family wealth | Active |
|
|
| 2026-08-27 | Holdings holds assets only and never borrows, carries debt, or holds credit cards | Non-negotiable |
|
|
| 2026-08-27 | Venture priority is Hospitality, Properties, Technology, then Creative | Active |
|
|
| 2026-08-27 | Sam is owner/capital allocator/strategist, not daily operator | Active |
|
|
| 2026-08-27 | Hospitality ownership is guaranteed 85/15 with Kiowa options up to 25% | Active; verify wording against executed OA when available |
|
|
| 2026-08-27 | Executed Hospitality OA is authoritative in Documenso | Active |
|
|
| 2026-08-28 | Repository is the authoritative planning center and is standalone at `~/Documents/SnS Network Solutions/` | Completed |
|
|
| 2026-08-27 | Plane is expected to be retired after useful data is preserved | Planned |
|
|
| 2026-08-27 | Newest owner-confirmed document controls; superseded versions move to archive | Active |
|
|
| 2026-08-27 | Durable owner decisions are recorded automatically | Active |
|
|
| 2026-08-27 | Recommendations default to one best path | Active |
|
|
| 2026-08-27 | Profit planning includes a 10% church tithe | Active; accounting treatment pending CPA guidance |
|
|
| 2026-08-27 | Route Codex through local Headroom compression by default to reduce token cost; keep Ponytail's minimal-solution discipline active | Active; verify savings from measured usage |
|
|
|
|
## Maintenance
|
|
|
|
Update this file when Sam makes a durable decision, changes a venture priority, resolves
|
|
a contradiction, crosses a material gate, or changes the operating doctrine. Do not add
|
|
routine task updates, conversation history, credentials, private account data, or facts
|
|
that belong in a venture source document.
|