docs(evidence): clarify identity vs authority wording

Identity is independent of how authority is received; authority may be native or delegated.
Remove the 'identity grants no authority / separate delegation' generalisation; scope the
dispatch-time grant check to the delegated-authority scenario actually exercised.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: chrisjleal

public/evidence/aaif/authority-at-dispatch/2026-10-06/SHA256SUMS

@@ -1,5 +1,5 @@
 67dcbff2c2045f421ad8ef8dd1926f0ff967870c66570cd45575d13a127cda4a  README.md
-3022a3af146d3bddd4b8edd2cb6801c3af1c77683b3aea96e481ec58441b1501  manifest.json
-9486cda06badff4c4d4878773f46dececcbe8a3694aa79a412f2b42d7f90836f  authority-effect-results.md
-b65b16f4578278fa4be402d4960c2b6554b3ed4307c2a7fe4aca2bff531b7232  authority-effect-results.json
+c590a8c934694ffc6c0f8644e921a56fe7c89d5e43cf8929621536f53f64abe8  manifest.json
+fb38ad6b4a11f4a6937af93a079662a55b6aa30a75ac92a4ead5df99812e81d0  authority-effect-results.md
+c4b35ed7c2f08dc8924979934a137a9bfd673436a4c98f89395d3d6ece7dd92f  authority-effect-results.json
 d749cf16fe8dd599f528e21e95863b930004a0b3f0a9882695e3d3b03e8c2183  trace.jsonl

public/evidence/aaif/authority-at-dispatch/2026-10-06/authority-effect-results.json

@@ -9,7 +9,7 @@
   "custody": "SELF (author-operated; ordinary non-admin Pro review tenant)",
   "boundary": "authority \u2192 decision \u2192 dispatch \u2192 effect/outcome \u2192 receipt",
   "authority_policy_version": "authority-policy.v1",
-  "authority_policy_boundary": "identity grants no authority; a separate delegation carries bounded authority and is re-evaluated from current state at dispatch",
+  "authority_policy_boundary": "identity is independent of how authority is received; authority may be native or delegated, and when delegated the grant is evaluated from current state at the action boundary",
   "evidence_scope": "author-operated; independent reproduction not yet claimed",
   "contract": {
     "reference": "probityai/agent-evidence-observer",

public/evidence/aaif/authority-at-dispatch/2026-10-06/authority-effect-results.md

@@ -21,17 +21,21 @@ denial as retroactively preventing an earlier effect.
 
 ## How Proofable produces the result (public-safe summary)
 
-- **Identity is not authority.** An agent identity record establishes who the agent is and grants no
-  permissions. Bounded authority is a separate delegation, so an agent can be authenticated and still
-  lack the authority to act.
-- **Authority is evaluated at the action boundary.** The dispatch path resolves the selected
-  delegation from current state and checks the requested action against it — revoked or expired
-  authority is denied rather than inherited from a still-valid identity.
+- **Identity is not authority.** An agent can have its own identity independent of how it receives
+  authority. When authority is delegated, Proofable records the grant separately and evaluates its
+  current state at the action boundary. An agent can be authenticated and still lack the authority to
+  act.
+- **Authority is evaluated at the action boundary.** For this delegated-authority scenario, the
+  dispatch path resolves the selected grant from current state and checks the requested action against
+  it — revoked or expired authority is denied rather than inherited from a still-valid identity.
 - **A denial is itself evidence.** A refused dispatch produces a signed authority-decision record
   (`outcome`, `reason`, `policyVersion`), not only a silent failure.
 - **The record is portable.** The same signed record can be carried to another relying party, which
-  applies its own appraisal; disclosure is separate from evidentiary validity, so the full delegation,
+  applies its own appraisal; disclosure is separate from evidentiary validity, so the full grant,
   runtime policy, and internal execution state need not be disclosed.
+- **Layers stay separate.** Proofable treats identity, authority, execution evidence and appraisal as
+  distinct layers. Authority may be native or delegated; the proof/receipt is the evidence layer that
+  connects them, not an authorization model in itself.
 
 Authority policy version: `authority-policy.v1`.
 

public/evidence/aaif/authority-at-dispatch/2026-10-06/manifest.json

@@ -10,7 +10,7 @@
   "custody": "SELF (author-operated; ordinary non-admin Pro review tenant)",
   "boundary": "authority \u2192 decision \u2192 dispatch \u2192 effect/outcome \u2192 receipt",
   "authority_policy_version": "authority-policy.v1",
-  "authority_policy_boundary": "identity grants no authority; a separate delegation carries bounded authority and is re-evaluated from current state at dispatch",
+  "authority_policy_boundary": "identity is independent of how authority is received; authority may be native or delegated, and when delegated the grant is evaluated from current state at the action boundary",
   "results": {
     "binding_veto": "SUPPORTED",
     "revoked_stale": "SUPPORTED",