AGENT SKILL

distributed-systems

Distributed Consensus & Fault Tolerance: CAP theorem, PACELC, distributed transactions (2PC, 3PC), Paxos, Raft consensus protocol, vector clocks, Byzantine fault tolerance (BFT), and eventual consistency.

License 许可
MIT
最近更新
2026-11-09
Stars
★ 0
Forks
0

01 前言 Front Matter

name
distributed-systems
risk
low
domain
computer-science
license
MIT
version
1.0.0
category
computer-science
platforms
[ "claude-code", "cursor", "codex", "gemini", "antigravity", "copilot" ]
subdomain
core-systems
description
Distributed Consensus & Fault Tolerance: CAP theorem, PACELC, distributed transactions (2PC, 3PC), Paxos, Raft consensus protocol, vector clocks, Byzantine fault tolerance (BFT), and eventual consistency.

03 SKILL.md 正文

Distributed Consensus & Fault Tolerance

CAP theorem, PACELC, distributed transactions (2PC, 3PC), Paxos, Raft consensus protocol, vector clocks, Byzantine fault tolerance (BFT), and eventual consistency.

Standard Operating Procedure & Methodology

1. Conceptual & Theoretical Foundations

Formulate the theoretical principles governing distributed consensus & fault tolerance:

  • Identify formal mathematical models, RFC standards, POSIX specifications, or architecture references.
  • Establish invariant state conditions, memory/algorithmic complexity bounds, and resource lifecycle rules.
  • Define unambiguous operational constraints and diagnostic telemetry signals.

2. Implementation & Analytical Steps

  1. Architectural Scoping: Map the subsystem boundaries, interface contracts, and hardware/software execution layer.
  2. Deterministic Algorithm Execution: Implement optimized algorithmic paths or low-level system calls with zero undefined behavior.
  3. Stress & Boundary Testing: Evaluate worst-case edge inputs, resource starvation scenarios, race conditions, and error recovery.
  4. Performance & Profiling: Validate operational efficiency (latency, cache hit ratios, throughput, asymptotic guarantees).

3. Verification & Compliance Contract

Every operational execution must verify:

  • Complete absence of memory leaks, deadlocks, race conditions, or unhandled system exceptions.
  • Deterministic behavior across target platforms and compilers.
  • Conformance with canonical RFC, POSIX, IEEE, or architectural standards.

Reference Architecture & Standards

Applies formal mathematical proofs, low-level kernel abstractions, and standardized wire protocol specifications to deliver deterministic, high-efficiency execution across agentic and distributed systems.

04 同仓库更多 Skills