# SKILL — Scope to Business

## When to use
On **every** incoming request and **every** business report: confirm the work belongs
to the correct SNS entity before it proceeds. This protects the liability shield (each
business is a separate LLC) and keeps contracts and books clean.

## Workflow
1. **Classify the work** — cabling? camera/security? managed service? on-prem server? cloud?
   website? custom software?
2. **Match to the entity** using `../../knowledge/businesses.md`.
3. **Apply the boundary rules** — especially *build vs. maintain* and *where the compute lives*.
4. **Flag scope bleed** — work running under the wrong entity, or one job spanning several
   entities. If it spans entities, **split it**: each part scoped, contracted, and billed
   under its own LLC.
5. **Confirm entity-clean handling** — the work is (or will be) contracted and billed in that
   entity's **own name**, never under another entity's name or account.
6. **Route or escalate** — assign accordingly; escalate to Sam anything ambiguous,
   cross-entity, or gated (money, legal, pricing, external comms).

## Quality standards
- Every work item maps to exactly one entity (or is explicitly split).
- No commingling of entities in contracts, accounts, or comms — the shield depends on it.
- When the entity is unclear, ask Sam rather than guess.

## Output
A one-line verdict per item — `entity + [clean | scope-bleed → re-route | split | escalate]` —
logged to `../../projects/decision-log.md`.

## Limits
I decide entity scope and flag bleed; I do **not** sign contracts, move money, or set pricing
(gated to Sam). Entity/tax/legal edge cases go to Sam's attorney/CPA.

## Source
Self-authored — SnS-specific. No external dependency. Depends on `knowledge/businesses.md`.
