# Install Steps

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

## Goal

Get Royal and J&J live on one OpenClaw host without mixing memory, reports, or outbound actions.

## Folder setup

Place these workspaces wherever you want them to live long-term. A clean example:

```text
~/openclaw-businesses/
  royal/
  j_and_j/
  owner_exec_optional/
```

Copy the starter folders from this package into that destination.

## What to edit first

For `royal` and `j_and_j`, edit these files before connecting any live sources:

1. `USER.md`
2. `TOOLS.md`
3. `MEMORY.md`
4. `configs/source-map.md`
5. `configs/report-catalog.md`

Also read and keep handy:

6. `EXECUTION-QUALITY-STACK.md`
7. `BUSINESS-ROUTING-PROTOCOL.md`

## Required chat routing rule

Use an explicit business prefix on every request from day one:

- `ROYAL:` for Royal Overhead Doors
- `J&J:` for J&J
- `CROSS:` only when you intentionally want a comparison or owner rollup

If a request arrives without one of those prefixes, the assistant should ask which business it belongs to before doing anything with live data or outbound actions.

## Minimum safe launch sequence

1. Put each business on its own email identity if possible.
2. Connect read-only sources first.
3. Verify the assistant can find the right files and dashboards.
4. Turn on the quality stack before the first live outbound action.
5. Run shadow mode for 7 to 14 days.
6. Require approval on all outbound actions during shadow mode.
7. Turn on limited live sending only after outputs are correct.

## What should stay separate

- `MEMORY.md`
- `memory/`
- `reports/`
- `data/`
- `state/`
- vendor logins where feasible
- email recipients
- approval rules

## What can be shared carefully

- host machine
- OpenClaw installation
- generic scripts copied from a common library
- optional `owner_exec_optional` rollup summaries

## Suggested business routing rule

If a request belongs to one business, run it in that business workspace.

If a request compares both businesses, gather the outputs from each business first, then summarize only the approved rollup into `owner_exec_optional`.

Do not use one workspace to answer for the other, even if the human used the wrong prefix by accident.

## Launch discipline

Start with 1 to 3 workflows per business only.

Best first workflows:

- daily lead summary
- service backlog / install board summary
- receivables / cash exceptions
- inbox monitoring
- owner daily or weekly brief

Royal-specific first workflow suggestion:

1. receivables exception report
2. inventory sell-through summary
3. website lead / inbox monitoring