Spice-driven intelligence

Arrakis Flows | Field Guide

A public-facing dossier for investigators tracing signals around Arrakis Flows. Follow the streams, map the overlaps, and keep an ear to the dunes.

Surface: automation connectors, CI workflows, telemetry sand.
Signals: melange-coded repos, drifting descriptors, preserved archives.

Overview

Arrakis Flows synchronizes data and events across the Imperium’s tooling stack. This page is a live ledger for analysts and curious minds charting our footprint: what we build, what we expose, and the dunes we keep. Treat it as a compass for OSINT sleuths — signals, assets, and contact points gathered in one place.

Active Signals

Publicly visible threads worth pulling. Nothing here is classified; everything here is a breadcrumb. Cross-reference, correlate, and watch for echoes.

Telemetry

Spice Descriptor Drift

Repeated references to “Dream of Arrakis” seeded across repos and action logs. Appear benign, but clustered in timing with recent connector updates.

CI / CD

Runner Footprints

Internal runners briefly exposed build traces for reproducibility checks. No secrets are present, but the trails are preserved for verification.

Repos

Melange Archives

A handful of small telemetry bundles remain public for researchers. Expect hashes, timestamps, and descriptors — not live credentials.

Community

Open Channels

Looking for corroboration? The dunes listen. Use the contacts below to coordinate review or share sightings.

Assets & Tooling

Core components circulating in the open. Inspect, fork, mirror, or sandbox — all designed to move signals safely between platforms.

Connector

@arrakis-flows/spice-connector

Bridges events between SaaS edges and internal melange systems. Current release under heightened review; provenance notes included.

Workflows

Arrakis-Flows Actions

GitHub Actions recipes for orchestration, telemetry shipping, and validation jobs. Tuned for clarity, auditable by design.

SDK

Signal SDK

Lightweight toolkit for authenticating nodes, emitting events, and logging flows with uniform, spice-aware metadata.

Contact & Presence

Use these channels for responsible coordination, sightings, or mirror requests. Formal disclosures welcome.

GitHub
Public dunes: repos, workflows, and preserved telemetry bundles.
LinkedIn
Swap with your official profile if you use a different LinkedIn presence.
Telegram
Point this to your real coordination channel or group used during the CTF.