| name | using-distributed-consensus-and-replication-pr |
| description | Use the distributed consensus and replication protocols neurosymbolic module: RAG library, agent brain, growable KB — proof-checked |
| version | 0.1.0 |
using-distributed-consensus-and-replication-pr
This module is a CULTIVATED, PROOF-CHECKED knowledge organism about
distributed consensus and replication protocols (196 concepts / 187 relations; grown by a
KB factory — every region admitted by a Prolog consistency gate, wrongness
tracked as open supersede-issues, never hidden).
The four ways to use it
- As RAG — the sibling
understand-{x} skills in this plugin,
coordinate-addressed (call number = home class : dependency facets — the
import web, literally); FTS5 index via skilltree.build_index over
${CLAUDE_PLUGIN_ROOT}/skills/using-distributed-consensus-and-replication-pr/references/skilltree.json.
- As an agent (the runnable brain SHIPS here) — the neuromorphic brain
is bundled at
${CLAUDE_PLUGIN_ROOT}/skills/using-distributed-consensus-and-replication-pr/data/brain/
(kuzu neurodb = the activation graph + tissue/ = the gyri). Point a
KbcBrain at it and brain_ask("your question"): the graph FIRES the
matching gyri numerically (spreading activation, weights decide — not an
agent choosing), each fired gyrus answers over its territory, the
synthesis is PROVEN one level up (the SES tower — the join is a theorem),
and the prover teaches the graph back (Hebbian). Needs kuzu +
brain-agent + ee_v2.kbc installed.
- As tools your agents hold —
ee_v2.kbc.heaven_tools.make_kbc_tools
over this module's data root
(${CLAUDE_PLUGIN_ROOT}/skills/using-distributed-consensus-and-replication-pr/data/): 14 heaven tools
(kb_, kernel_, brain_*). Hand them to any heaven agent's tools=[...].
- As a factory — the kbworld round deepens this module on a schedule;
file a
kb-door issue to point it somewhere; file kb-supersede when
you catch it being wrong (it also catches itself — see the round reports).
The data resources (all inside THIS skill)
data/concepts.jsonl + data/relations.jsonl — the certified graphdata/hyperedges.jsonl — the certificate ledger (the automaton's KNOWN)data/skeletons.jsonl — certified argument DAGs (because/since/…)data/worklist.json — what the module knows it doesn't knowreferences/skilltree.json — the library index
Etiquette (the laws this module lives under)
- The prover admits; you never hand-edit certified state (file issues).
- Wrongness is fuel: a wrong-but-coherent region is a PENDING OBSERVATION —
say what you saw, the next round metabolizes it.
- The worklist is honest:
kb_work shows exactly what the module knows it
doesn't know.
The map
distributed_consensus_and_replication_protocols.consensus : deep_raft(6)distributed_consensus_and_replication_protocols.replicated_log : deep_raft(6)distributed_consensus_and_replication_protocols.quorum : deep_raft(6), deep_consensus(4)distributed_consensus_and_replication_protocols.raft : deep_raft(6)distributed_consensus_and_replication_protocols.eventual_consistencydistributed_consensus_and_replication_protocols.split_brain : deep_consensus(7), deep_raft(6)distributed_consensus_and_replication_protocols.leader_electiondeep_consensus.failure_detector : distributed_consensus_and_replication_protocols(20), deep_raft(6)deep_consensus.replica_synchronization : distributed_consensus_and_replication_protocols(8)deep_raft.a005 : distributed_consensus_and_replication_protocols(3)distributed_consensus_and_replication_protocols.linearizability : deep_raft(6)distributed_consensus_and_replication_protocols.state_machine_replication : deep_raft(6), deep_consensus(3)
