# Business Routing Protocol

**Produced:** 08/18/2026 09:35 PM CDT

## Goal

Prevent Royal and J&J from ever mixing in chat, memory, reports, recipients, or outbound actions.

## Day-one rule

Every inbound request should begin with one of these prefixes:

- `ROYAL:`
- `J&J:`
- `CROSS:`

## Meaning

- `ROYAL:` means the request belongs only to the Royal workspace.
- `J&J:` means the request belongs only to the J&J workspace.
- `CROSS:` means gather inputs separately from each business and only then produce a rollup.

## If the prefix is missing

The assistant should ask which business the request belongs to before:

- opening live business data
- drafting outbound messages
- sending emails
- updating business memory
- saving deliverables into a workspace

## Hard rules

- Royal memory must never be written into J&J files.
- J&J memory must never be written into Royal files.
- Royal recipients must never receive J&J output.
- J&J recipients must never receive Royal output.
- `CROSS:` work must be explicit and human-intended.
- If recipient lists, files, or facts look mixed, stop and clarify before acting.

## Good examples

- `ROYAL: show me the top unpaid invoices over 90 days`
- `ROYAL: what inventory should we push first on the website`
- `J&J: summarize tomorrow's installs`
- `CROSS: compare receivables risk between Royal and J&J`

## Bad examples

- `send the report`
- `what are we owed`
- `draft this invoice`

Those are ambiguous unless the workspace and business prefix are already explicit.