diff --git a/docs/superpowers/specs/2026-10-07-oilgas-job-portal-adapters-design.md b/docs/superpowers/specs/2026-10-07-oilgas-job-portal-adapters-design.md
new file mode 100644
index 000000000..67f18a868
--- /dev/null
+++ b/docs/superpowers/specs/2026-10-07-oilgas-job-portal-adapters-design.md
@@ -0,0 +1,137 @@
+# Oil & gas job portal adapter: EnergyJobline
+
+**Date:** 2026-10-07
+**Status:** design approved, scope narrowed after a Rigzone feasibility spike
+
+## The problem
+
+The user supplied ~40 oil & gas domains (agencies, job portals, majors, EPC/service
+companies) to evaluate as new ingest sources. Recon across all of them, plus a pass over
+the live `boards` table, narrowed things down fast:
+
+- 18 majors/EPC/service companies sit on a known ATS. 13 were already boarded
+ (Shell, BP, Baker Hughes, Eni, ExxonMobil, Fluor, Halliburton, KBR, McDermott, SLB,
+ TechnipFMC, Wood, Worley). 5 were added via `cmd/add-board` on 2026-10-06 (Subsea7,
+ Bechtel, ADNOC, QatarEnergy, TotalEnergies). Aramco is excluded — its site TCP-blocks
+ automated requests and the platform could not be confirmed.
+- Of the 7 general/niche job portals (Rigzone, Oilcareers, EnergyJobline,
+ OilAndGasJobSearch, Bayt, GulfTalent, NaukriGulf, Laimoon — 8 names, 7 distinct
+ backends since Oilcareers shares Rigzone's infrastructure):
+ - **Bayt and GulfTalent already have adapters**, already registered, and already have
+ live `boards` rows. Nothing to build.
+ - **Laimoon's jobs backend is dead** — confirmed stub/kill-switch across the whole
+ `jobs.laimoon.com` subdomain, no link from the live homepage. Out of scope.
+ - **NaukriGulf and OilAndGasJobSearch are unreachable at the network level** from both
+ this environment and the prod host (tar-pit / connection refused). Out of scope.
+ - **Rigzone** looked buildable on first recon (AWS WAF challenge, same shape as
+ Bayt/GulfTalent's Cloudflare challenge) but a feasibility spike invalidated that — see
+ below. Moved to the deferred group.
+ - **EnergyJobline** is the one portal this design covers.
+
+## Rigzone feasibility spike (2026-10-07) — INVALIDATED for now
+
+Before committing to build Rigzone alongside EnergyJobline, its one open risk (would the
+project's existing Chrome-fingerprint transport, `fingerprinthttp.go`, clear Rigzone's bot
+defense the way it clears Bayt's and GulfTalent's?) was spiked directly against the live
+site, using the actual transport code rather than a guess:
+
+- **Plain fingerprint transport (`newFingerprintHTTP`, the same one `bayt.go`/
+ `gulftalent.go` use):** both `https://www.rigzone.com/` and `/sitemap.xml` returned a
+ flat `HTTP 403 Forbidden` (nginx-style, "a padding to disable MSIE and Chrome friendly
+ error page" body) with no `x-amzn-waf-action` header at all — i.e. not the solvable
+ "challenge" response seen from a plain `curl`, but a harder block that offers nothing to
+ pass. This matches the pattern this repo's own `firecrawltier.go` documents for
+ Bayt/GulfTalent/Wellfound: "the refusal comes before any challenge is offered" — a
+ datacenter-IP-level block, not a fingerprint check.
+- **Proxied fingerprint transport (`newProxiedFingerprintHTTP`, over this repo's existing
+ `SOURCES_PROXY_URL`):** untestable — the proxy account returned `402 Payment Required`.
+ Determining whether a non-datacenter egress clears Rigzone's block would require
+ topping up that account first, a real spend decision.
+- The further escalation this repo already has for exactly this shape of wall — the hosted
+ Firecrawl tier (`firecrawltier.go`) — also costs money per page and was not attempted.
+
+**Verdict: INVALIDATED within the current budget.** The free tier (fingerprint spoofing
+alone) flatly fails, and the next tier that might work costs money to even test. Asked
+directly, the user chose not to spend to find out — so Rigzone joins NaukriGulf and
+OilAndGasJobSearch in the deferred group rather than being forced through. It can be
+revisited later specifically because it is a 100%-on-topic oil & gas board (unlike Bayt/
+GulfTalent, whose broad general listings make the hosted tier's cost/relevance trade-off
+much worse) — if the user later wants to fund a proxy top-up or a Firecrawl trial, this
+spike's numbers are the starting point, not a dead end.
+
+## EnergyJobline
+
+Confirmed with a plain `curl` (Googlebot UA, no cookies, no JS) — no bot defense observed:
+
+- `https://www.energyjobline.com/sitemap.xml` is an open sitemap **index** of 4
+ sub-sitemaps.
+- A live posting, `https://www.energyjobline.com/job/controls-engineer-atlanta-31835232`,
+ server-renders three `