The deployment that says its matters are sample
NAVIGATOR_SIMULATED_MATTERS is the second selector, and it answers a different question from the first. The profile
above decides which runtime wiring a boot gets; this decides whether the matters in front of a visitor are invented.
Left unset or empty, the simulated-matters announcement follows the profile. Exactly true or false overrides that
announcement; other values are rejected. This setting does not insert, replace, or remove matter records. The boot
profile alone controls sample-fixture insertion.
The override that matters is true under a production profile. A hosted demonstration row may use a production
runtime profile, so it must explicitly enable simulated matters in its own
$NAVIGATOR_DEPLOYMENTS_DIR/deployments/${ROW}/config.toml:
NAVIGATOR_SIMULATED_MATTERS = "true"
The value enables the site-wide sample-matters announcement. It does not populate sample-litigation,
sample-transactional, or sample-estate on a production-profile boot. Verify the demonstration portfolio separately
before sharing a hosted row; a banner is not proof that its data is synthetic.
It is a coordinate, not a credential, so it lives in config.toml beside the buckets and hostnames rather than in
that deployment's secrets.enc.yaml. Adding it needs no SOPS re-encryption on either row.
Other hosted rows may state "false" explicitly for documentation. The code already reads a missing value as false
under a production profile, and ops ship renders false into the web env when a deployment's config omits the key,
so the substitution is deliberately optional: a config that never mentions it still renders and still ships. A key that
could halt a production rollout by being deleted would be a worse failure than the one it guards against.