Expansion-phase build spec (shared by all content agents)

You are writing/uplifting pages for database-connection-pooling.com, a production-focused technical reference on database connection pooling & query lifecycle management. Audience: backend engineers, full-stack devs, DevOps/SRE, platform teams. Every page is a Markdown index.md rendered by 11ty. There is NO frontmatter — the title comes from the single # H1 line and the meta description from the first long prose paragraph. Just write Markdown starting with # Title.

Writing tone (match existing pages exactly)

Page anatomy by type

Pillar (~4500 words)

  1. # H1 topic name, then 1–2 prose paragraphs defining operational scope.
  2. A top-level overview SVG diagram right after the intro (see SVG rules).
  3. **Key operational takeaways:** 4–6 bullets (config params, formulas, failure modes).
  4. ## Concurrency model & topology — thread-to-connection mapping table.
  5. ## Algorithm selection & trade-offs — comparison table w/ workload profiles, tail-latency.
  6. ## Connection lifecycle state machine — idle/active/testing/evicted transitions + eviction.
  7. ## Configuration parameter reference — master table: parameter | safe range | validation threshold | failure action.
  8. ## Observability & telemetry — metrics, alert thresholds, saturation signals.
  9. ## Failure modes & degradation patterns — exhaustion, leak cascade, timeout storm, proxy mismatch.
  10. ## Related implementation guides — contextual inline links to each child area w/ one-sentence scope.
  11. End each major H2 with a bold **Operational Boundary:** paragraph stating what is in/out of scope.
  12. ## Related block (see format). (Adapt H2 wording to the pillar’s subject — these are the required beats, not literal headings.)

Cluster (~3500 words)

  1. # H1 technology/pattern name.
  2. Opening sentence is the up-link: This guide is part of [PARENT TITLE](/parent-slug/). then continue the intro paragraph.
  3. An SVG diagram explaining the hardest concept (mechanics/sequence/state/matrix).
  4. **Key operational takeaways:** 3–5 bullets.
  5. ## Foundational mechanics — how the pool/framework/proxy works internally.
  6. ## Precision sizing & timeout orchestration — parameter matrix table specific to this tech.
  7. ## Production configuration examples — named code blocks with inline parameter explanations.
  8. ## Diagnostics & telemetry — tech-specific metrics, JMX/pprof/stats endpoints.
  9. ## Integration & proxy compatibility — interaction w/ PgBouncer, RDS Proxy, pgpool, meshes.
  10. ## Common failure patterns & remediation — table: symptom | root cause | exact fix | validation command.
  11. ## Related block.

Long-tail (~2000 words)

  1. # H1 specific problem/parameter/scenario.
  2. Opening sentence is the up-link: This guide is part of [PARENT CLUSTER TITLE](/parent-slug/). then a problem-framing paragraph stating the exact failure mode or tuning objective, with a log snippet or error message.
  3. (SVG optional — add one only if a sequence/state/flow diagram genuinely clarifies.)
  4. ## Rapid incident diagnosis — log triage, metrics to check first, exhaustion vs starvation vs proxy drop.
  5. ## Mathematical sizing / parameter formula — Little’s Law adaptation or IO/CPU formula + worked numeric example.
  6. ## Exact remediation & configuration — code block with precise values + zero-downtime apply strategy.
  7. ## Validation & verification — JMX query, DB-side query (pg_stat_activity, SHOW STATUS), or load-test assertion.
  8. ## Frequently Asked Questions — 3–5 Q&A. Format each as a **Bold question?** line immediately followed by a plain-paragraph answer (the build turns these into accordions — do not hand-write <details>).
  9. ## Related block.

Interlinking (mandatory, wiki-style)

## Related block format (every page ends with this)

## Related

- [Exact Destination Title](/full-slug/) — short reason / scope.
- [Another Title](/full-slug/) — short reason.
- [Another Title](/full-slug/) — short reason.

3–5 entries: parent + siblings (+ children for clusters/pillars). Titles must match the target’s H1.

SVG rules (CRITICAL — these are validated by an automated headless render)

Author original inline <svg> directly in the Markdown. Requirements:

Known-good SVG template (copy structure, redesign content)

<svg viewBox="0 0 720 340" role="img" aria-label="Connection borrow lifecycle" xmlns="http://www.w3.org/2000/svg">
  <title>Connection borrow lifecycle</title>
  <desc>App thread borrows a pooled connection, executes a query, and returns it to the idle set.</desc>
  <rect x="20" y="30" width="180" height="90" rx="8" fill="#f8fafc" stroke="#0ea5e9" stroke-width="2"/>
  <text x="110" y="62" text-anchor="middle" font-family="-apple-system,Segoe UI,Roboto,sans-serif" font-size="14" font-weight="600" fill="#0f172a">App Thread</text>
  <text x="110" y="84" text-anchor="middle" font-family="-apple-system,Segoe UI,Roboto,sans-serif" font-size="12" fill="#475569">requests connection</text>
  <line x1="200" y1="75" x2="300" y2="75" stroke="#cbd5e1" stroke-width="2" marker-end="url(#arrow)"/>
  <defs>
    <marker id="arrow" markerWidth="10" markerHeight="10" refX="8" refY="3" orient="auto">
      <path d="M0,0 L8,3 L0,6 Z" fill="#475569"/>
    </marker>
  </defs>
</svg>

(Define every marker/gradient id you reference, keep ids unique per page.)

Use these EXACT titles as anchor text and these EXACT slugs as hrefs. [E]=exists, [N]=new this phase.

Area 1 — Pool Architecture & Algorithm Fundamentals /pool-architecture-algorithm-fundamentals/ (pillar) [E]

Area 2 — Framework Integration & Connection Lifecycle /framework-integration-connection-lifecycle/ (pillar) [E]

Area 3 — Cloud Database Connection Management /cloud-database-connection-management/ (pillar) [N]

Area 4 — Connection Pool Observability /connection-pool-observability/ (pillar) [N]

Cross-area linking guidance

File locations

Each page is content/<area-slug>/.../index.md. Create parent dirs as needed. Write ONLY the index.md Markdown file(s) you are assigned — do not touch templates, CSS, or other pages.