What problem does it solve? API routes that bypass the sequencer Durable Object can silently drop the authorization gates the sequencer would have enforced, letting drivers post GPS positions or physical facts for shipments they are not assigned to, under devices they do not own, or without consent. ## Core Features & Use Cases - Gate Parity Enforcement: Requires every API-reachable write of a gated physical fact (raw GPS, stop.arrived/departed, POD, custody, appointments) to re-invoke the same predicates the sequencer DO applies, per REQ-030. - Shared Predicate Module: Factors assignmentOf, deviceOwnedBy, and streamPrior into one module imported by both the route and the DO so authorization cannot drift between paths. - Static Lint Design: Provides a CI lint specification that fails the build when a write path persists a gated fact without calling the required predicates, including detection of unregistered stealth bypass routes. - Use Case: When adding a positions ingestion route that skips the sequencer for throughput, apply this Skill to add driver-assignment, device-ownership, and consent-before-GPS checks with server-derived operating state before the INSERT. ## Quick Start Review the new positions write route and add the assignmentOf, deviceOwnedBy, and assertConsentBeforeGps checks before its INSERT so it matches the sequencer gates.
