Crucible / Operations / Campaign Registry

Campaign registry

One operator surface for product-lane campaign truth: active state, SERP intake, enrichment, priority, caps, readiness gates, and worker activity across the shared Crucible spine.

Updated May 11, 2026 6:48 PM UTC · Schema logicforge-layer-816-schema.sql · left nav: Operations

Shared spine verdictOne machineL816 · no product-specific enrichment workers

Active campaigns1

revenue_leak_finder

operator-controlled

SERP intake ON1

revenue_leak_finder

shared discovery capacity

Enrichment ON1

revenue_leak_finder

shared enrichment spine

Send postureOFF

No campaign enables live send from this surface.

no-send doctrine preserved

Campaign rowsOpen machine receipt →

Campaign	Product	Active	SERP	Enrichment	Priority	SERP cap	Enrich cap	Readiness gate	Ready today	Blocked	Last worker activity
revenue_leak_finder	revenue_leak_finder	ON	ON	ON	100	100	250	revenue_leak_finder_readiness	230	4123	unavailable
permitpulse	permitpulse	OFF	OFF	OFF	50	50	150	permitpulse_readiness	196	3205	unavailable
ignite	ignite	OFF	OFF	OFF	50	50	150	ignite_readiness	150	93	unavailable

Canonical flow

SERP → canonical prospect → enrichment → email → readiness

Campaigns differ by SERP matrix and downstream readiness gate; all active website/domain-bearing prospects use the same Crucible enrichment spine.

Edit campaign switches →

Fail-closed boundariesPreserved

Product-specific workersForbidden

RLF scan/reportNot triggered

Checkout/send behaviorUntouched

SchemaNo-op