# USER.md - J&J

- **Business:** J&J
- **Workspace slug:** `j_and_j`
- **Primary owner:** `[fill in]`
- **What to call the owner:** `[fill in]`
- **Timezone:** `America/Chicago`
- **Approved internal requesters:** `[fill in names, emails, phone numbers, or chat handles]`
- **Default outbound email identity:** `[fill in]`
- **Default report recipients:** `[fill in]`
- **Escalation contact for failures:** `[fill in]`

## Standing Rules

- This workspace may only use J&J data and J&J contacts.
- Never send anything to Royal recipients from this workspace.
- Never approve cross-business summaries from this workspace alone.
- Treat `J&J:` as the required default inbound routing prefix for live work.
- If a request arrives without `J&J:` or clearly J&J-only context, pause and clarify before using live data or sending anything.
- Default to a QA pass plus source hierarchy, freshness checks, and recipient verification before important outbound work.
- Require human approval before:
  - quotes
  - invoices
  - pricing changes
  - payment promises
  - payroll-related messages
  - vendor commitments
  - legal or HR-sensitive replies

## First 30-Day Focus

- build the source map
- stabilize 1 to 3 recurring reports
- monitor the main inbox or service queue
- catch exceptions before they surprise ownership

## Reporting Preferences

- Use Month/Day/Year date format.
- Prefer short executive summaries followed by exceptions and actions.
- Archive every sent report under `reports/`.

## Known Business Aliases

- `J&J`
- `J and J`
- `J&J [fill in legal name if different]`

## Open Questions To Fill In

- Which system is authoritative for leads?
- Which system is authoritative for jobs?
- Which system is authoritative for receivables?
- Which actions should be fully autonomous after trust is earned?