The three comparison pages open on the bars, not the prose

learn/compare/cheapest-way-to-verify-and-gate.mdx

@@ -5,6 +5,11 @@ description: "Identity vendors charge you on every check. See what a reusable pr
 icon: coins
 ---
 
+<img className="evid-light evid-wide" src="/images/evidence/save-reuse-light.svg" alt="Bar chart comparing the time to redo a finished job, 2.79 seconds, with the time to check a Proofable receipt, 3.7 milliseconds" />
+<img className="evid-dark evid-wide" src="/images/evidence/save-reuse-dark.svg" alt="Bar chart comparing the time to redo a finished job, 2.79 seconds, with the time to check a Proofable receipt, 3.7 milliseconds" />
+<img className="evid-light evid-tall" src="/images/evidence/save-reuse-stacked-light.svg" alt="Bar chart comparing the time to redo a finished job, 2.79 seconds, with the time to check a Proofable receipt, 3.7 milliseconds" />
+<img className="evid-dark evid-tall" src="/images/evidence/save-reuse-stacked-dark.svg" alt="Bar chart comparing the time to redo a finished job, 2.79 seconds, with the time to check a Proofable receipt, 3.7 milliseconds" />
+
 Cheapest depends on how many times the same fact gets checked. A per-check vendor bills again on each visit. A proof is created once, then read without a fee, so the more places that need the same answer, the wider the gap between the two.
 
 ## Which to choose

learn/compare/proofable-or-a-policy-engine.mdx

@@ -5,6 +5,11 @@ description: "A policy engine applies your rules. Proofable adds delegation, spe
 icon: scale-balanced
 ---
 
+<img className="evid-light evid-wide" src="/images/evidence/stop-tools-light.svg" alt="Bar chart of AgentGovBench, where Proofable handles 48 of 48 governance scenarios, against 43 for a gateway and 13 for agent tools on their own" />
+<img className="evid-dark evid-wide" src="/images/evidence/stop-tools-dark.svg" alt="Bar chart of AgentGovBench, where Proofable handles 48 of 48 governance scenarios, against 43 for a gateway and 13 for agent tools on their own" />
+<img className="evid-light evid-tall" src="/images/evidence/stop-tools-stacked-light.svg" alt="Bar chart of AgentGovBench, where Proofable handles 48 of 48 governance scenarios, against 43 for a gateway and 13 for agent tools on their own" />
+<img className="evid-dark evid-tall" src="/images/evidence/stop-tools-stacked-dark.svg" alt="Bar chart of AgentGovBench, where Proofable handles 48 of 48 governance scenarios, against 43 for a gateway and 13 for agent tools on their own" />
+
 Keep your rules in your policy engine. Add Proofable when an agent runs somewhere you don't own, when more than one party relies on the outcome, or when someone outside your system has to trust the decision. A policy engine with a log is enough only when one team owns the rules, every caller, and everyone who reads the log.
 
 ## What each one answers

learn/compare/proofable-or-an-identity-provider.mdx

@@ -5,6 +5,11 @@ description: "Proofable can serve as sign-in and as the authority check. An iden
 icon: scale-balanced
 ---
 
+<img className="evid-light evid-wide" src="/images/evidence/stop-exfil-light.svg" alt="Bar chart of a hijacked-agent test, where an all-purpose key let 6 of 6 attempts send private data out and an owner-scoped permission let 0 of 6 through" />
+<img className="evid-dark evid-wide" src="/images/evidence/stop-exfil-dark.svg" alt="Bar chart of a hijacked-agent test, where an all-purpose key let 6 of 6 attempts send private data out and an owner-scoped permission let 0 of 6 through" />
+<img className="evid-light evid-tall" src="/images/evidence/stop-exfil-stacked-light.svg" alt="Bar chart of a hijacked-agent test, where an all-purpose key let 6 of 6 attempts send private data out and an owner-scoped permission let 0 of 6 through" />
+<img className="evid-dark evid-tall" src="/images/evidence/stop-exfil-stacked-dark.svg" alt="Bar chart of a hijacked-agent test, where an all-purpose key let 6 of 6 attempts send private data out and an owner-scoped permission let 0 of 6 through" />
+
 ## Which to use
 
 Use Proofable when an agent acts on its own schedule, when the permission check has to happen at each call, or when a customer, auditor, or downstream agent must confirm the decision afterwards. Proofable can also be the sign-in. One account across every app, with passkeys, email codes, social accounts and wallets, and each check a person passed reused instead of repeated. Keep an existing identity provider only when an organization requires it, and let it issue the session while Proofable decides what runs under it. An identity provider alone covers only agents that act inside a signed-in person's session and never need a spend cap, an expiry, or a record of the action.