@hyperscale0/cli 1.0.441 → 1.0.442

package/README.md

@@ -113,6 +113,26 @@ A scenario is the same story as a file. It stops at the first step that fails:
 
 `hyperscale scenario init` writes one that fits your Product.
 
+A bank's QA keeps a folder of scenarios beside the Core and runs it with
+`hyperscale scenario run assure/ --rehearsal --json`. Each file runs on a
+fresh rehearsal copy of the Product, every step gets a verdict, and the run
+exits 1 when any step failed. Suites run in sandbox only; live is refused with
+`assure_live_refused`. Three more fields serve them:
+
+| Field      | Does                                                                                                  |
+| ---------- | ----------------------------------------------------------------------------------------------------- |
+| `staff`    | Names sandbox team members by staff role; each one's token comes from `HYPERSCALE_STAFF_<NAME>`       |
+| `refused`  | `"status 403 \"missing_required_permission\""` on a step passes only on that refusal                  |
+| `approval` | A run that waits for approval keeps it by name; `{ "approve": "<name>", "by": "<staff>" }` decides it |
+
+An approver also needs `HYPERSCALE_STAFF_<NAME>_PASSWORD`. The report is kept
+on the Product; a report Arc does not keep exits 1 with
+`assure_report_not_stored`. `hyperscale core evidence <core-id> --out
+evidence/` exports it with the Core's documents, certificate, checks, plan
+and audit events, and needs `audit:read`. `hyperscale core certificate <core-id> --verify` checks the signed
+certificate against your installation's `/release.json`
+([docs/public/assure.md](../../docs/public/assure.md)).
+
 ## Watch and debug
 
 | Command                                                     | Shows                                                            |