business: README names nine hard waits, git.push.remote included; row 199 added it to GATED_ONLY (row 199 review N3, duckworth-0068, #1697 )

2026-10-20 19:27:10 -05:00
1 changed files with 4 additions and 3 deletions
@@ -50,10 +50,11 @@ in this repository, or `$MOSAIC_ROLES_DIR` if set.
  `withinRole` actions run without asking. `crossRole` actions need the
  arbiter. Any action not listed is gated: it goes to Jason, or to the
  arbiter for its domain when the raise cites the project's current spec
-  commit (PRD 1.5 REQ-DEC-2). The eight hard waits in `GATED_ONLY`
+  commit (PRD 1.5 REQ-DEC-2). The nine hard waits in `GATED_ONLY`
  (REQ-WAIT-1: `spend`, `data.delete`, `network.expose`, `account.create`,
-  `credential.mint`, `message.external`, `git.push.protected`, `deploy`)
-  always go to Jason and can't appear in either list (REQ-WAIT-2).
+  `credential.mint`, `message.external`, `git.push.protected`,
+  `git.push.remote`, `deploy`) always go to Jason and can't appear in
+  either list (REQ-WAIT-2). `git.push.remote` joined in row 199 (#1697).
  `GATED_ONLY` is every action that `ROUTED` doesn't name, so an action
  added to the vocabulary is a hard wait until a PRD says otherwise and the
  commit adds it to `ROUTED` (REQ-WAIT-3). `git.merge.protected`,