The 10 Particles

Every service in the Field is modeled after a physics particle. The name encodes what it does — and what it must never do.

I — The Canonical Pipeline

Six particles in strict order. Every event traverses this path — no step may be skipped.

Boson→Fermion→Higgs→Hadron→Photon→Neutrino

FIG 1.1

Boson

Ingress & Canonicalization

Force carrier — mediates interactions between systems

Accepts external inputs (webhooks, API calls, scheduled triggers), validates identity, wraps payloads into canonical EventEnvelopes with CorrelationId and HMAC signatures. Returns 202 immediately — never blocks on downstream processing.

FIG 1.2

Fermion

Decisioning & Orchestration

Matter particle — gives the system its structure

Core routing engine. Evaluates pipeline rules against incoming EventEnvelopes, consults Higgs for policy evaluation, produces ActionPlans — ordered, declared lists of Actions. Dispatches to Photon for execution. Supports dry-run mode as a first-class concept.

FIG 1.3

Higgs

Governance Brain

The Higgs field gives particles mass — defines observable properties

Owns tenant configuration, evaluates policy rules: allow/deny/filter for any proposed action, connector, model, or target. Operates on allowlists by default. Provides redaction transforms and data classification.

Hadron

Durability & State Machines

Composite particle — durable, structured, persistent

Durable job store persisting workflow state across restarts. Manages step state machines (pending → dispatched → executing → succeeded/failed), retry logic with exponential backoff, dead letter queues, and persistent idempotency.

FIG 1.4

FIG 1.5

Photon

Connectors & Egress

Carries electromagnetic force to the outside world

Typed connectors to external systems — HTTP APIs, message queues, LLM providers, SaaS platforms. Resolves credentials from vault at execution time. Classifies errors as transient, permanent, or rate-limited.

FIG 1.6

Neutrino

Audit, Observability & Explainability

Passes through matter without interacting — observes but does not change outcomes

Append-only audit ledger recording the full processing chain for every event. Provides cost/latency accounting, decision explainability, trace views, and queryable event history.

II — Field Operators

Four specialized operators that act on events without entering the canonical path. They type, compose, schedule, and sandbox.

FIG 2.1

Quark

Domain Objects

Fundamental building block — typed constituents inside composite structures

Parses raw event payloads into typed domain events (PR, Ticket, Invoice, LLMRequest). Provides shared vocabulary for pipeline matching. Purely interpretation and typing.

FIG 2.2

Gluon

Workflow Composition

The strong force that binds quarks into hadrons — composition and binding

Workflow graph / DSL with fan-out, fan-in, conditional branching, and compensation logic. Workflows are declared, serializable, and versioned data, not embedded code.

FIG 2.3

Graviton

Time & Scheduling

Mediates gravity — the force defined by spacetime

Cron triggers, delays, SLA timers, polling schedules. All time-derived events re-enter the field through the canonical path as EventEnvelopes.

FIG 2.4

Muon

Sandbox Execution

Heavier cousin of the electron — exists briefly, does work, decays

Safe execution of user-defined transforms and logic within strict sandbox boundaries. Resource-limited, no network access by default, deterministic execution.

← Back to the Field