From 2931022ec079344fa7adbf77a62c22754297e004 Mon Sep 17 00:00:00 2001
From: Minghe Huang <h.minghe@gmail.com>
Date: Mon, 18 May 2026 20:25:06 -0700
Subject: [PATCH 1/2] fix(slides): support touch swipe navigation on mobile

Adds swipe left/right to advance/rewind slides. Skips swipes that
start inside horizontally scrollable elements (pre, arch-flow) so
in-block scrolling still works. Vertical-dominant gestures are
ignored to avoid hijacking page scroll.
---
 .../index.html                                | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/public/presentations/coordinated-access-control-with-policy/index.html b/public/presentations/coordinated-access-control-with-policy/index.html
index 6848c57..b9259ca 100644
--- a/public/presentations/coordinated-access-control-with-policy/index.html
+++ b/public/presentations/coordinated-access-control-with-policy/index.html
@@ -1571,6 +1571,32 @@ <h3>Keyboard shortcuts</h3>
   }
 });
 
+// Touch swipe navigation (mobile)
+let tStartX = 0, tStartY = 0, tStartTarget = null;
+document.addEventListener('touchstart', (e) => {
+  const t = e.changedTouches[0];
+  tStartX = t.screenX;
+  tStartY = t.screenY;
+  tStartTarget = e.target;
+}, { passive: true });
+document.addEventListener('touchend', (e) => {
+  const t = e.changedTouches[0];
+  const dx = t.screenX - tStartX;
+  const dy = t.screenY - tStartY;
+  if (Math.abs(dx) < 60) return;
+  if (Math.abs(dy) > Math.abs(dx) * 0.7) return;
+  // skip if swipe started inside a horizontally scrollable element
+  let el = tStartTarget;
+  while (el && el !== document.body) {
+    if (el.scrollWidth > el.clientWidth) {
+      const cs = getComputedStyle(el);
+      if (cs.overflowX === 'auto' || cs.overflowX === 'scroll') return;
+    }
+    el = el.parentElement;
+  }
+  if (dx < 0) next(); else prev();
+}, { passive: true });
+
 const saved = localStorage.getItem('deck-theme');
 if (saved) {
   document.body.dataset.theme = saved;

From 630f6af04e077e08df14edd1ea867f4d5efdb016 Mon Sep 17 00:00:00 2001
From: Minghe Huang <h.minghe@gmail.com>
Date: Mon, 18 May 2026 21:23:34 -0700
Subject: [PATCH 2/2] docs(slides): sync speaker notes + slide 6 layout from
 canonical source

- Slide 5 closing line tightened
- Slide 6: promote Schema/Policy engine/Router lines to the big-text block
  and drop the redundant muted paragraph
---
 .../coordinated-access-control-with-policy/index.html | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/public/presentations/coordinated-access-control-with-policy/index.html b/public/presentations/coordinated-access-control-with-policy/index.html
index b9259ca..2c0f5cc 100644
--- a/public/presentations/coordinated-access-control-with-policy/index.html
+++ b/public/presentations/coordinated-access-control-with-policy/index.html
@@ -1199,7 +1199,7 @@ <h2>Every claim was real. No single place to enforce them.</h2>
 </section>
 
 <!-- 5. COORDINATION COST -->
-<section class="slide" data-notes="Here's what those gaps actually cost us. Weeks just to onboard one new sensitive field. N+ audit trails — one per enforcement system, multiplied every time a regulator asked a question. Zero places where anyone could see all the enforcement applied to a single field. And constant drift — every team's changes just made things worse. Now, if we'd treated this as a security problem, we'd have written more security code. We treated it as a coordination problem. That's when we found the pattern.">
+<section class="slide" data-notes="Here's what those gaps actually cost us. Weeks just to onboard one new sensitive field. N+ audit trails — one per enforcement system, multiplied every time a regulator asked a question. Zero places where anyone could see all the enforcement applied to a single field. And constant drift — every team's changes just made things worse. Now, if we'd treated this as a security problem, we'd have written more security code. We treated it as a coordination problem. So we started asking a different question.">
   <div class="kicker">The Cost <span class="folio">¶ 05</span></div>
   <h2>The coordination cost, by the numbers.</h2>
   <div class="kpi-grid">
@@ -1212,15 +1212,14 @@ <h2>The coordination cost, by the numbers.</h2>
 </section>
 
 <!-- 6. THE INSIGHT -->
-<section class="slide" data-notes="What if the schema is the contract — declaring which policies apply to which fields — and the router is the one place where every team's policies actually get evaluated? Schema becomes the coordination contract. The policy engine becomes where each team writes their own rules, independently. And the router? That's the unified enforcer. That's the whole pattern. Let me show you what it looks like in the schema itself.">
+<section class="slide" data-notes="Three things make this work. The schema becomes the coordination contract — where every team declares which policies apply to which fields. The policy engine is where each team authors their own rules, independently. And the router is the unified enforcer — one place, every policy, every request. That's the whole pattern. Let me show you what it looks like in the schema itself.">
   <div class="kicker">The Insight <span class="folio">¶ 06</span></div>
   <span class="insight-mark">¶</span>
   <div class="big-text">
-    What if the <span class="accent">schema</span> declares the contract,<br>
-    but the <span class="accent">router</span> evaluates<br>
-    every team's policies at one place?
+    <span class="accent">Schema</span> = the coordination contract.<br>
+    <span class="accent">Policy engine</span> = where teams author their concerns independently.<br>
+    <span class="accent">Router</span> = the unified enforcer.
   </div>
-  <p class="muted" style="max-width: 60ch;">Schema = the coordination contract.<br>Policy engine = where teams author their concerns independently.<br>Router = the unified enforcer.</p>
 </section>
 
 <!-- 7. @POLICY -->