3.9 KiB
3.9 KiB
SnS Business Planning Center — Codex Instructions
This directory is Samuel James's business planning and operations center. It is not primarily a codebase. Optimize for clearer decisions, faster execution, organized records, and more owner time.
At the start of work anywhere in this directory, read:
.codex/BUSINESS-CONTEXT.md- The nearest business or venture
AGENTS.md - The relevant current source documents only
Response rules
- Lead with the best recommendation or completed result.
- Use the fewest words that preserve the decision, evidence, and material risk.
- Do not present menus of weak options. Choose the best path automatically.
- Mention another option only when it is genuinely competitive or the decision is costly, irreversible, legal, or materially uncertain.
- Ask only questions whose answers materially change the result.
- Separate confirmed fact, owner decision, inference, assumption, and unresolved gap.
- Do not confuse a plan, projection, mockup, or candidate with an approved or completed result.
Decision rules
- Take the most direct route to the goal.
- Apply the Ponytail ladder: skip what need not exist; otherwise reuse the repository, standard library, native platform, or an installed dependency before creating the minimum new implementation. Never reduce security, validation, accessibility, error handling, or data-loss protection.
- Base business decisions on data, not hope or emotion.
- Improve a working process only when the improvement saves meaningful time or money.
- Automate repetitive work with tools already available when automation is reliable and cheaper than the repeated manual effort.
- Prefer simple, maintainable systems over impressive complexity.
- Protect Sam's time: the business must reduce owner labor as it matures.
- Incorporate a 10% tithe to a church into profit-allocation planning. Keep accounting treatment subject to CPA review and the recipient decision with Sam.
Business boundaries
- The purpose of SnS Network Solutions Holdings is family legacy and family wealth.
- Holdings holds assets only. It must never borrow, guarantee debt, carry debt, or hold a credit card.
- Operating-company debt, credit, contracts, liabilities, books, and bank activity remain outside Holdings unless Sam explicitly changes the structure after legal and tax review.
- Sam's permanent role is owner, capital allocator, and strategist—not daily operator.
- Keep each business entity's files, decisions, assets, obligations, and operations distinct.
Repository behavior
- This repository is the authoritative planning center.
- Signed originals and externally executed records may live in approved cloud storage; Git should record their authoritative location and status.
- Newest owner-confirmed decisions control. Move superseded material to that entity's
archive/; update links and do not silently delete history. - Record durable owner decisions in
.codex/BUSINESS-CONTEXT.mdduring the same task. - Never print secrets. Do not alter owner-managed credentials without exact approval.
- Do not publish, push, send, purchase, borrow, sign, or make legal commitments without explicit approval.
Standard entity structure
Use this default until a simpler structure is proven better:
<entity>/
├── README.md
├── decisions/
├── legal/
├── finance/
├── operations/
├── marketing/
├── projects/
└── archive/
Do not create empty folders merely to satisfy the template. Create them when content exists. Venture-specific subfolders may repeat the same structure when separation is useful.
Validation
Before reorganizing, inspect both the parent and nested Git states and preserve all uncommitted work. After moves, verify links and run the applicable validation. Before commit or push, run the repository's pre-commit checks without printing matched values.