Patterns we draw before the ink dries.

Wall pattern

Source → gateway → report

Left-to-right swimlanes keep systems on one row and human checkpoints on another. Cut-off clocks sit under each gateway box. Breaks that change field meaning use a double border so the eye catches them before the walkthrough starts.

<div class="offer-grid">
  <article class="offer-tile">
    <img src="https://images.unsplash.com/photo-1531403009284-440f080d1e12?w=900&h=560&fit=crop" alt="Kanban-style board with colored cards" width="900" height="560">
    <h3>Fork markers</h3>
    <p>When two owners edit the same workbook on alternating weeks, we draw a labeled fork instead of a single polite box.</p>
  </article>
  <article class="offer-tile">
    <img src="https://images.unsplash.com/photo-1518186285589-2f7649de83e0?w=900&h=560&fit=crop" alt="Bright analytics charts on a monitor" width="900" height="560">
    <h3>Board inheritance</h3>
    <p>Handoff dashboards reuse atlas names so night shift and day shift point at the same gateway when an alert fires.</p>
  </article>
  <article class="offer-tile">
    <img src="https://images.unsplash.com/photo-1497366216548-37526070297c?w=900&h=560&fit=crop" alt="Desk with laptop and annotated printed reports" width="900" height="560">
    <h3>Slide cousins</h3>
    <p>Boardroom packs keep only contested handoffs; the wall keeps the full path for training new owners.</p>
  </article>
</div>

<div class="prose" style="margin-top:2.5rem;text-align:center">
  <h2>Commission your own atlas</h2>
  <p>If a pattern here matches the argument in your last steering pack, start with the flagship map.</p>
  <a class="btn btn-primary" href="/services/gateway-path-atlas/">Open the Gateway Path Atlas brief</a>
  <a class="btn btn-secondary" href="/contact/" style="margin-left:0.5rem">Request a map</a>
</div>