HN Showcase
Back to browse
GitHub Repository

Provider-controlled verification constraints for distributed systems. Execution authority remains exclusively scoped to the provider boundary.

0 starsPython

One provider starts lying at request 50. The quorum catches it

by sbw70·Mar 4, 2026·1 point·2 comments
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainWizardry

Byzantine fault detection without promoting hubs to decision-makers — clever constraint, niche audience.

Strengths
  • •Stateless intermediary architecture prevents authority drift by design, not policy
  • •Deterministic, replayable drift detection demonstrates formal correctness across regions
  • •Eight independent constraint modules address distinct authority-migration vectors
Weaknesses
  • •Repository is abstract reference architecture with limited real-world deployment evidence
  • •Dense formal language and distributed systems prerequisites limit accessibility
Target Audience

Distributed systems architects, security researchers, enterprise infrastructure teams

Similar To

ZeroTrust architecture frameworks · Byzantine Fault Tolerant consensus protocols (PBFT, Raft)

Post Description

Two regions. Six hubs. Six providers. One of them starts lying after request 50.

The quorum catches it. Authority never moves.

NUVL fronts compute bindings and forward only. Hubs relay and fan out — no authority, no policy. Providers are the only execution authorities. When Provider_B starts flipping reported outcomes, the 2-of-3 quorum audit detects the drift without promoting hubs into decision-makers.

The drift is deterministic and replayable. You can see exactly when it starts and what the quorum sees.

https://replit.com/@holiwood4420/Two-Region-Quorum-Audit-wit...

Similar Projects