Field Project
Architecture as counter-force to entropy
10 particles. 12 laws. One canonical path.
The Canonical Pipeline
Every event follows the same path. No step may be skipped. No step may absorb the responsibility of another.
An Event Traverses the Field
Each particle activates in sequence.
Boson
External system sends a webhook. Boson validates identity, assigns CorrelationId, wraps into EventEnvelope, signs with HMAC. Returns 202.
Fermion
Fermion verifies HMAC, invokes Quark to parse the typed domain event, then consults Higgs for policy.
Higgs
“Tenant X wants to execute Action Y — allowed?” Higgs evaluates and returns PolicyDecision with effective config and redaction rules.
Hadron
Fermion builds the ActionPlan, records step state in Hadron for durability, emits decision record to Neutrino.
Photon
For each Action in the plan: Photon resolves credentials, executes the typed connector, classifies the result.
Neutrino
Every decision, action, and outcome is recorded in Neutrino’s append-only audit ledger. Full trace available.
The Names Are Not Decorative
Each name encodes what the service does and — critically — what it must never do.
Neutrinos don’t interact with matter. Neutrino observes; it does not mutate.
Bosons carry forces; they don’t decide trajectories. That’s Fermion’s job.
Photons execute; they don’t govern. Higgs governs.
Fermions are stateless deciders. Hadron holds durable state.
The Higgs field gives particles their properties. Tenant config lives in Higgs.
Entropy Is the Default
Without a field — without canonical paths, enforced boundaries, and immutable audit — systems trend toward disorder.
AI Governance
Route AI requests through a governed pipeline. Policy is evaluated before execution. Every decision, action, and outcome is auditable.
Event-Driven Platform
Build internal automation — CI/CD orchestration, incident response, approval workflows — on a governed event backbone.
Explore the Field
The particles, the laws that govern them, and the philosophy behind the architecture.