Test Scenario: Verify holding company CRM ticks live

• The database must be freshly provisioned via --source acme: compass db recreate -y -k then compass shell -f projects/ores.shell/scripts/library/provisioning/how_do_i_provision_the_system_with_acme_corporation_holding_group.ores. Confirm the run completes with no failed steps – each office's acme_uk.synthetic_feeds: ... completed (and the equivalent for us/hk) confirms live feeds actually started, which this scenario depends on.

Each step is its own heading — the title should be five to seven words so it fits on one line in the QA Validation Runner's step list without wrapping or truncating (e.g. "Edit and save the record", not a full sentence describing the whole operation). The body below the title is a bullet-point checklist, not a prose paragraph: give the tester every piece of context needed to execute that one step without looking anything up elsewhere — what UI state must already exist, exactly what to click or type, and exactly what confirms the step passed. The panel writes each step's PASS/FAIL/PENDING outcome and notes back as a *** Result child heading directly under it.