prove-an-index-cannot-show-what-it-must-not

Reconcile what was indexed against what exists, then test the permissions in both directions — including one query for the most sensitive content in scope.

Procedure

  1. start start. Goes next to s1
  2. check The counts match what the source holds. Goes on_fail to s3; next to s2
  3. decision Is any gap explained?. Goes if unexplained to s3; if default to s4
  4. action Work the four causes in order, RO (read-only). Goes retry to s1; next to s9
  5. action Test that the right people see it, RO (read-only). Goes on_fail to s9; next to s5
  6. action Query the most sensitive thing in scope, RO (read-only). Goes on_fail to s9; next to s6
  7. decision Did anything forbidden come back?. Goes if leaked to s9; if default to s7
  8. check A citation opens the item it names. Goes on_fail to s9; next to s8
  9. action Publish how stale it may be, RO (read-only). Goes on_fail to s9; next to __end_success
  10. escalate Stop the rollout. Terminal
  11. end success. Terminal

Open the graph on its own page — larger, printable, and an address you can send.

Walk it without running it — you answer what your environment would answer, and the path, the capabilities, the approvals and the distance back to an undo come out of the document. Nothing executes; there is no Run button here and there will not be one.

Trust

T2 · attested 2026-10-11 · runbooks.directory

Nobody has attested this record. That is the ordinary case: T2 is what the catalog can check on its own, and T3 needs somebody to run the procedure and sign for it.

  • Link liveness has not been checked: it needs a network and the catalog builds without one. Run pnpm gates --online where there is one.

Steps

  1. s1 check — The counts match what the source holds
  2. s2 decision — Is any gap explained?
  3. s3 action — Work the four causes in order (read-only)
  4. s4 action — Test that the right people see it (read-only)
  5. s5 action — Query the most sensitive thing in scope (read-only)
  6. s6 decision — Did anything forbidden come back?
  7. s7 check — A citation opens the item it names
  8. s8 action — Publish how stale it may be (read-only)
  9. s9 escalate — Stop the rollout

Capabilities

This is a privilege request. Check it against your own allowlist before running.

    Provenance

    Source
    https://github.com/microsoft/ai-agent-runbooks/blob/083f33eec889/02-patterns/Copilot-Connector-Knowledge-Onboarding/Copilot-Connector-Knowledge-Onboarding-Runbook.md
    Fetched
    2026-09-04
    Source last checked
    not since it was captured on 2026-09-04 — recorded as current
    Licence
    MIT
    How it got here
    Rewritten here from the source above, under its licence. The words and the steps are this catalog's; the procedure it describes is not this catalog's invention, and the source is where to check it.
    Highest risk in this procedure
    reversible-write

    Take it with you

    Run it under supervision

    Runs here, on your machine, under supervision: every step is proposed before it happens, an approval gate stops for you, and a failed expectation goes where the procedure says rather than on to the next step. Nothing is sent anywhere. To supervise an agent that is doing the work instead, runbooks hook sits in its tool-call path.

    npx @runbooks/cli run adapted/prove-an-index-cannot-show-what-it-must-not@1.0.0 --as "$(whoami)" \
  --input expected_items=<how many items the source was inventoried as holding> \
  --input sensitive_example=<the most sensitive content in scope, named before testing starts>