Update specs-and-limits.md

[miguelgabrielass95-dev]

No description provided.

[rw-growth-check]

Growth check — AMH estimate

#1326 @ 4ea61cb — advisory only. Judgment ranges, ≤2 significant figures; SEO and AEO legs are never summed (AMH_RULES v2.2, constants v2.3 (2026-08-06)).

Files considered:

• content/docs/networking/public-networking/specs-and-limits.md (modified)

SEO leg (Google surface)

no estimate (see caveats)

AEO leg (AI assistants)

2–6 visits/mo

Gates

• SERP page type(s): unknown
• AI Overview present: absent
• Gated to zero: no
• Gauge topic: no Gauge topic matched (mean-default)

Keyword candidates for the AMH panel

None found for this content.

Caveats & verification stamps

• Current-traffic baseline (modified pages): /networking/public-networking/specs-and-limits: 4322 pageviews, 3457 visitors (10 AI-referred) over ~2mo.
• Verification pass: PostHog rates are stamped person- vs event-level — visitors are person-level (uniqExact person_id), pageviews are event-level (AMH_RULES §5/§8).
• SERP page-type gate could not be evaluated (no SERP page-type data) — verify winnability manually before pricing (AMH_RULES §2.2).
• SEO leg: no on-subject keyword volumes found — no estimate (derive seeds manually and re-check).
• Verification pass: the AEO Δ is a labeled ASSUMPTION (+1pt; caps +2 pts/quarter, +6 pts/12mo — AMH_RULES §3.5).

How to go deeper

Ask an agent with the railway-internal MCP (the gauge_* / ahrefs_* / posthog_* tools) or the amh-growth skill for observed-anchor pricing, live SERP inspection, topic curation, and citation checks.

Ahrefs cost: 200 API units · How AMH is calculated