Skip to content

report-intake — boundary record and attestations

Error-report intake service (their apps/report-intake): anonymous reports into the tenant's private tracker. The public hostname is the platform's first public-intake class member (ADR-0005 §13) — since §15 it rides the cf-public gateway through the tenant's public tunnel (sf-public-dev), not the shared listener.

Hostname Class Edge auth
reports.dev.screamingface.ai public-intake (§13) none — Turnstile in-app
reports-internal.dev.screamingface.ai user-facing dev (§11 shared AUD) Cloudflare Access

Environments (2026-09-30): dev (both doors); staging since #1378 (internal door hostname exists and answers 302 to Access; its route lands with the application's AUD; no public door — ADR-0005 §13 gate); production since #1380 (2026-10-03, after the owner's production Turnstile secret), internal door only; its hostname reports-internal.screamingface.ai follows the owner's tunnel row and Access application.

Platform half: kubernetes/apps/sf-report-intake-platform/ (namespace, quota, netpols, dev Postgres, both ExternalSecrets); edge: the route declarations kubernetes/tenants/screamingface/routes/dev/reports-public.yaml and reports-internal.yaml (both HTTPRoutes and the identity SecurityPolicy, rendered by the tenant-edge chart, ADR-0005 §14). Workload: tenants-charts ticket + values (chart's edge/netpol/SA templates off; fullnameOverride: reports — the Service name must never share the app's REPORT_INTAKE_ env prefix, scoreboard's service-link lesson).

Attestation record (the public hostname's boundary artifact)

The public hostname has no AUD, so its recorded boundary is this dated attestation set — facts that live in the tenant's Cloudflare dashboard and cannot be verified from git. Behavioral verification: the Gatus posture pair (public 403 without redirect; identity 302/401) watches the two facts that can drift silently.

Re-attestation triggers: Cloudflare plan change · tunnel change · any Access application change on the zone · any abuse incident on the public hostname.

# Fact Status Attested by Date
1 NO Access application covers reports.dev.screamingface.ai (checked directly; the PR-preview wildcard is *.preview.dev.screamingface.ai, one level deeper — no overlap). "No app", not a Bypass policy (Bypass is origin-identical but unlogged). ATTESTED owner (bitsofsteve) 2026-08-31
2 reports-internal.dev.screamingface.ai added to the fusion.dev Access app (shared dev-tier AUD, §11 list amendment in ADR-0005) ATTESTED owner (bitsofsteve) 2026-08-31
3 Turnstile widget for reports.dev.screamingface.ai, Managed mode, REAL keys (not Cloudflare's well-known always-pass test constants). Sitekey 0x4AAAAAAEjIHU_eaxfIZ-u6 (public, recorded for verifiability). Secret in Key Vault as sf-report-intake-dev-turnstile-secret (break-glass, zero standing access confirmed). ATTESTED owner (bitsofsteve) 2026-08-31
4 Zone plan: Free — a host- or method-scoped edge rate rule is not expressible (one path-only rule, 10s window, is the zone's whole budget) ATTESTED owner (bitsofsteve) 2026-08-31
5 Bot Fight Mode: ON, zone-wide, unscopable on Free; challenges BEFORE Turnstile. Decision at the first SDK acceptance test; no remedy pre-committed (ADR-0005 §13 risk 3). The forbidden lever: never toggled mid-incident. ATTESTED (status) owner (bitsofsteve) 2026-08-31
6 No pre-existing DNS record on either hostname ATTESTED owner (bitsofsteve) 2026-08-31
7 Tunnel Public Hostname rows (×2, both at the shared-proxy origin — platform-supplied over a direct channel, never in tenant-facing docs) — added after the edge slice merged (one row briefly typo'd reports-dev, corrected same hour; TLS cert auto-issued ~3 min later). Outside-in proofs same day: identity 302→Access with the shared AUD; public door answered through the edge, no redirect, no Bot Fight Mode challenge on a curl POST. Deleting the reports.dev row remains the kill switch. DONE owner (bitsofsteve) 2026-08-31

Open items

  • SDK Turnstile token (tenant): Turnstile is a browser widget; the hostname's primary caller is a headless Python SDK. Until the tenant ships a token story, the anonymous door 403s legitimate SDK reports (ADR-0005 §13 risk 4). The identity door is unaffected.
  • First image: dev-build-report-intake.yml exists in their repo but has pushed no image yet (screamingface-report-intake absent from ACR as of 2026-08-31). The workload ticket stays sentinel-blocked until a build lands.
  • Bot Fight Mode decision at the first SDK acceptance test (row 5).
  • §15 remaining items: re-attest rows 1, 6 and 7 after the tunnel move (no Access app; the route now on sf-public-dev; the "Remove visitor IP headers" managed transform OFF — cf-public fails closed without CF-Connecting-IP); the staging slice before any staging exposure.