- I01RULE SHIFTERS
- I02429 SWARMLINGS
- II03CLAIM CRAWLERS
- II04MIMIC WARDENS
- III05GREY FOG
- III06THE FUNNEL
- IV07PUPPETEER HUNTERS
- V08INFRINGER LEDGER
THEY REWRITE THE PHYSICS OVERNIGHT
Rule shifters are the platform itself, moving. Specs, limits and policies change — sometimes announced in a changelog nobody reads, sometimes discovered only as a new kind of rejection. Pipelines built on yesterday's rules break in production, at publish time.
YOUR PIPELINE ENCODED THE RULES. THE RULES MOVED.
Every automated pipeline is a frozen copy of the platform's rules on the day it was written: container specs, duration limits, field formats, content policies. Platforms change these on their own schedule, for their own reasons, with wildly uneven notice. The failure arrives at the worst possible layer — production, at publish time, wearing an error message that names a symptom instead of the change.
- R1
The shift
A spec or policy changes upstream — a new encode requirement, a tightened limit, a policy category redrawn. Effective date: sometime.
- R2
The mismatch
Your pipeline keeps emitting yesterday's format. Nothing fails in testing, because your tests encode the same stale rules.
- R3
The pileup
Publishes start bouncing in production. Diagnosis burns a day, because the error describes the rejection, not the rule that moved.
A BEAM THAT SWEEPS AHEAD OF THE FLEET
Sentinel is a spec registry and policy radar: the platform's rules read as data, with effective dates, versioned like the code that depends on them. Gate 02 validates every ship against the current registry — so when the rules move, the pipeline learns it from the registry update, before enforcement, not from a rejection after.
STATUS: BEING BUILT — CAPABILITIES LANDING WITH TESTS, GAPS DOCUMENTED. SEE THE FULL MANIFEST →One place the truth lives
Specs stop being folklore scattered through code and become a registry with versions and effective dates — diffable, reviewable, testable.
Notice before enforcement
The beam's whole job is the gap between "announced" and "enforced". Work happens in that gap on your schedule, instead of during an outage on theirs.
Rejections that name the rule
When something is held at validation, the message points at the registry entry that changed — the diagnosis is included in the failure.
The platform owes you nothing — not stability, not notice, not sympathy. A system that survives on someone else's world does it by reading the weather, not by petitioning it.
WHY THE LIGHTHOUSE FACES OUTWARD