plans: no verb adds a role instance, so the 149 brief and acceptance 314 name Jason's business-file edit (#1643)

Dewey 0572: organization.set's instances field only sets the model of an
instance the business file already declares (launch-settings.mjs:46-52),
and business.mjs:130 refuses a launch.instances name the roles don't
declare. The row 149 brief said chief's organization change adds the
merge-gate and security-reviewer instances, and acceptance 314's
before-the-run list repeated it. Both now say Jason adds them by editing
the business file and validates it. Doc-only; no test reads either file.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/acceptance/314.md

@@ -16,9 +16,10 @@ bus schema.
 - `mosaic bus status` says the host is live.
 - `mosaic inbox` shows no open decision. If one is open, resolve or
   supersede it first, so step 6 starts from an empty inbox.
-- The organization has security-reviewer and merge-gate instances, added
-  through the chief of staff's organization change with Mos's go, and
-  both are in `launch.instances`.
+- The business has security-reviewer and merge-gate instances, and both
+  are in `launch.instances`. No verb adds an instance today, so Jason adds
+  them by editing the business file, then runs
+  `scripts/mosaic business validate <business>`.
 - `arbiters.technical` is `cto`, which step 5 assumes.
 
 ## Steps

docs/plans/2026-10-15_q167-rows-r3.md

@@ -197,10 +197,13 @@ agents are proactive, and no role contract says so.
   spec citation go to the domain's arbiter, and only an uncited gated raise
   or a hard wait goes to the human. Both texts say that, next to the
   proactive line. This is also from Dewey's row 139 Follow-ups.
-- Instances of the new roles are added through chief's organization
-  change verb (row 132), never by editing Jason's business file. Adding
-  them to the mosaic-stack business is a live step after the re-pin, with
-  Mos's go. It is not part of the row.
+- No verb adds a role instance today. organization.set's `instances` only
+  sets the model of an instance the business file already declares
+  (`packages/business/src/launch-settings.mjs:46-52`, Dewey 0572), and
+  `business.mjs:130` refuses a `launch.instances` name the roles don't
+  declare. So adding security-reviewer and merge-gate instances to the
+  mosaic-stack business is an edit to Jason's business file, made by Jason
+  after the re-pin. No agent makes it. It is not part of the row.
 - Tests: both role files load and validate; security-reviewer's tool list
   has no write or shell tool; merge-gate's only grant is
   git.merge.protected cross-role; a merge-gate raise with domain