Expansion-phase authoring brief (read this fully before writing)

You are writing/upgrading ONE markdown page for multi-tenant-saas.com, a technical reference site for SaaS engineers on multi-tenant data isolation, auth, routing, billing and compliance. Tone: dense, expert, declarative, no fluff, no marketing. Match the existing pages' voice (short authoritative sentences; concrete tools, SQL, config).

Hard rules

  1. Output is a single content/.../index.md file. Keep the frontmatter layout and add the full frontmatter block (below). Do not touch other files.
  2. No Mermaid. This site no longer renders Mermaid. Any diagram MUST be a hand-authored inline <svg> using the figure pattern below. If you are uplifting a page that contains a ```mermaid block, REPLACE each one with an equivalent inline-SVG figure.
  3. Code blocks use a real language identifier (typescript, sql, go, python, ini, yaml, bash, json) — never code or blank. Every code block must be runnable and specific, not pseudocode.
  4. No internal IA jargon in visible prose. Never write the words pillar, cluster, long-tail, hub, spoke, supporting page. (A Kafka/DB "cluster" in the infrastructure sense is fine.)
  5. FAQ format is plain markdown — the site JS turns it into accordions. Write each Q&A as:
    ## FAQ
**Question text ending in a question mark?**
Single-paragraph answer on the next line.

**Next question?**
Answer.
    One blank line between pairs. Do NOT write <details> or accordion HTML yourself.

Frontmatter (every page)

---
layout: content-page.njk
title: "<Page Title>"
description: "<145-160 char meta description, specific, no fluff>"
slug: <the-last-url-segment>
type: <pillar | cluster | long_tail>
breadcrumb: "<short breadcrumb label>"
datePublished: 2026-06-21
dateModified: 2026-06-21
---

(For pages being uplifted that already have datePublished, keep the original and set dateModified: 2026-06-21.)

Interlinking (mandatory)

URL map (use exact paths)

Pillars:

Auth children:

DB children:

Data-routing children:

Billing children:

Compliance children:

Page anatomy by type

pillar (~4500 words)

cluster (~3500 words)

long_tail (~2000 words)

Inline-SVG figure pattern (REQUIRED for every diagram)

Use this exact wrapper. Hand-author the SVG specific to the page content. Rules:

Template to adapt:

<figure class="diagram" role="img" aria-label="Concise description of the diagram">
  <svg viewBox="0 0 760 360" xmlns="http://www.w3.org/2000/svg" font-family="Inter, system-ui, sans-serif">
    <rect x="0" y="0" width="100%" height="100%" fill="#0b1220"/>
    <title>Short title</title>
    <desc>One-sentence description of what the diagram shows.</desc>
    <!-- arrow marker -->
    <defs>
      <marker id="arrowGold" markerWidth="10" markerHeight="10" refX="8" refY="3" orient="auto" markerUnits="strokeWidth">
        <path d="M0,0 L8,3 L0,6 Z" fill="#c9a84c"/>
      </marker>
    </defs>
    <!-- a node -->
    <rect x="40" y="40" width="200" height="60" rx="8" fill="#1a2d50" stroke="#c9a84c" stroke-width="1.5"/>
    <text x="140" y="75" text-anchor="middle" fill="#e2e2d8" font-size="14">Edge Ingress</text>
    <!-- a connector -->
    <line x1="240" y1="70" x2="360" y2="70" stroke="#c9a84c" stroke-width="1.5" marker-end="url(#arrowGold)"/>
  </svg>
  <figcaption>What the reader should take away from this diagram.</figcaption>
</figure>

CRITICAL: do NOT put any blank line ANYWHERE between <figure class="diagram"> and </figure>. A blank line ends the markdown HTML block and the browser orphans the rest of the SVG geometry (the diagram renders empty/broken). Keep the entire figure contiguous — no empty lines inside it. Also ensure label text contrasts with its box: light text (#e2e2d8 / #e8c97a) only on the dark fills (#0f1f3d / #1a2d50), never on light fills.

IMPORTANT: every id you reference (markers, gradients) must be DEFINED in the same SVG, and ids must be UNIQUE within the page (suffix them per-diagram, e.g. arrowGold-2). Aim for one strong diagram per page (pillars may have the overview plus at most one more).