RPCShield is a static analysis tool to detect dependency relations (fail-close/fail-open) between microservices.
-
Updated
Sep 2, 2026 - Go
RPCShield is a static analysis tool to detect dependency relations (fail-close/fail-open) between microservices.
Reference architecture for fail-open, witness-only evidence systems with independent verification and public settlement.
Pi-hole–style DNS sinkhole on the ESP32-S3 — fail-open, DoT fail-closed, OTA rollback. MIT.
Portable System-1 decision layer for agent harnesses with host-owned routing, receipts, replay, and fail-open integrations.
Ultra-fast, fail-open advisory decisions and verbatim extractive reading view for AI coding agents and CLI pipelines
Detector failures become recorded gaps, never synthetic clean results. Zero dependencies.
Real-time authorization decisions measured under injected failure: timeouts, caching, graceful degradation and a kill switch, measured rather than asserted. Whether a timeout bounds the tail, what fail-open versus fail-closed costs once both errors are priced, and whether webhook-driven decisioning is idempotent under replay.
Security control failure & detection lab: an authorization fail-open, its exploit, root cause, fix, detection rule and regression test. Local red/blue lab, synthetic data only.
SYSTEM-ARCHITECTURE-PROJECT-02 RateGuard : A horizontally scalable API Gateway demonstrating distributed systems concepts. Implements Token Bucket rate limiting via Atomic Redis Lua scripts, fail-open resiliency, and NGINX Docker DNS resolution.
Operational security controls with forensic guarantees
Long-term memory plugins for Oh My Pi (OMP) and DSH (WIP), designed for TencentCloud/TencentDB-Agent-Memory. Fail-open, out-of-band architecture.
A client-agnostic, multi-stage rate limiting policy engine for TypeScript, powered by @upstash/ratelimit.
Defensive publication: two-stage RAG ranker whose LLM rerank stage fails open to a deterministic base.
Block network ads and trackers by running a DNS sinkhole on an ESP32-S3 microcontroller.
To associate your repository with the fail-open topic, visit your repo's landing page and select "manage topics."