@@ -7,7 +7,7 @@ fix(plugin-approvals): an approval's status write-back runs its automation as th
 Clause-②: no
 
 - **What changes.** The write that mirrors a request's status onto the record's `approvalStatusField` (submit, approve, reject, recall, send back, the action link) now names the organisation of the record it writes, and no longer carries an empty set of positions and permission sets. A `runAs: 'user'` hook on that object, and a `runAs: 'user'` record-change flow fired by that write, now run with the acting person's own request envelope in the record's organisation: their positions, their permission sets and their organisation's members, resolved exactly as their own request in that organisation resolves them.
-- **Before.** Such a hook ran on the member baseline and saw only the acting person in `sys_user`. Such a flow resolved the person's grants with no organisation: it saw only the person as a peer, and its positions came from every organisation the person belongs to rather than from the record's.
+- **Before.** Such a hook ran on the member baseline and saw only the acting person in `sys_user`. Such a flow resolved the person's grants with no organisation, so it saw only the person as a peer and did not run with what the record's organisation grants them.
 - **Every acting person, one organisation.** An approver drawn from another organisation's directory also acts in the record's organisation. The organisation is read from the record when the status is written, so a record moved to another organisation while its approval was pending is written, and cascades, in its new organisation.
 - **Unchanged.** The write stays elevated (`isSystem`), so it still lands on a locked record and on a read-only status field. A status written by a sweep with no person behind it (the dead-run release) stays user-less, so a `runAs: 'user'` automation it fires is still refused. `ctx.session.organizationId` in a hook on the write now carries the organisation, and `ctx.session.positions` is absent instead of an empty list.
 
 
@@ -3186,8 +3186,8 @@ export class ApprovalService implements IApprovalService {
    *    Nothing downstream supplies a missing organisation: the automation
    *    engine's grants bridge answers a `tenantId` only when it was handed one,
    *    and an organisation-less resolution is not the actor's request in the
-   *    record's organisation — its peers are the actor alone, and its positions
-   *    come from every organisation the actor belongs to.
+   *    record's organisation — its peers are the actor alone, and its grants
+   *    are not the ones that organisation gives them.
    * The write itself is authorized by `isSystem` alone — the security
    * middleware short-circuits before it reads any grant — so leaving the arrays
    * off changes nothing about what this write may do.
 
@@ -16,7 +16,7 @@
  * Two producer facts make that true, and each has its own pins here:
  *  - the write names the organisation (`tenantId`), read live off the record.
  *    Without it every consumer resolves organisation-less: the person alone as
- *    peer, and positions from every organisation they belong to;
+ *    peer, and grants that are not the ones the record's organisation gives;
  *  - the write carries NO `positions` / `permissions` of its own. A consumer
  *    keeps carried arrays verbatim, so empty ones stood in for the person's
  *    grants and left the hook on the member baseline.