DBRaven

Knowledge Coverage

Live health report of the knowledge base. Tracks entity counts against target ranges, confidence distribution per domain, relationship density, and scenario type coverage. No fabricated metrics, all data is computed from the live YAML knowledge pipeline.

Knowledge Hub →

146

Total Entities

patterns + tech + failures + workloads

126

Relationships

target 50–150

10 / 10

Scenarios Covered

scenario types with ≥1 entry

97%

Overall Coverage

avg across all domains vs targets

Domain Coverage

Architecture Patterns

Browse →

39

39 loadedtarget 2540

Confidence

100% high

Technology Profiles

Browse →

25

25 loadedtarget 2030

Confidence

100% high

Failure Modes

Browse →

67

67 loadedtarget 3050

Confidence

100% high

Workload Profiles

Browse →

15

15 loadedtarget 1525

Confidence

100% high

Trust & Review Status

DDIA-caliber depth and red-team review state per family, from `content_quality` / `review_state` on each entity. A family with no tracked entities shows "not yet tracked" rather than a fabricated zero.

Family

DDIA-Caliber

Red-Team Pending

Red-Team Approved

Patterns

9 / 39

6

3

Browse →

Technologies

4 / 25

4

0

Browse →

Failure Modes

25 / 67

19

6

Browse →

Workloads

not yet tracked

Scenarios

0 / 25

0

2

Browse →

Awaiting Human Review, 29 entities

Columnar Storage(Patterns, red team pending)
Competing Consumers(Patterns, red team pending)
Inbox Pattern (Idempotent Consumer)(Patterns, red team pending)
Index Table(Patterns, red team pending)
LSM-Tree Storage(Patterns, red team pending)
Leader Election(Patterns, red team pending)
Apache Cassandra(Technologies, red team pending)
ClickHouse(Technologies, red team pending)
MySQL(Technologies, red team pending)
PostgreSQL(Technologies, red team pending)
Buffer Pool Churn(Failure Modes, red team pending)
Checkpoint Amplification(Failure Modes, red team pending)
Clock Skew(Failure Modes, red team pending)
Disk I/O Saturation(Failure Modes, red team pending)
Dual-Write Inconsistency Between Systems(Failure Modes, red team pending)
Event Ordering Violation(Failure Modes, red team pending)
LSM Compaction Debt(Failure Modes, red team pending)
Network Partition(Failure Modes, red team pending)
Replica Divergence(Failure Modes, red team pending)
Replication Lag Cascade(Failure Modes, red team pending)
Schema Drift(Failure Modes, red team pending)
Schema Migration Lock(Failure Modes, red team pending)
Schema Version Mismatch Between Services(Failure Modes, red team pending)
Secondary Index Write Saturation(Failure Modes, red team pending)
Split-Brain(Failure Modes, red team pending)
Table and Index Bloat(Failure Modes, red team pending)
WAL Saturation(Failure Modes, red team pending)
Write Amplification Cascade(Failure Modes, red team pending)
Write Skew Anomaly(Failure Modes, red team pending)

Relationship Coverage

126 typed relationships total. Density = average relationships per entity. Higher is richer, but relationship quality matters more than count.

Entity Type

Outbound

Inbound

Avg Density

Patterns

48

58

2.2×

Technologies

41

6

1.7×

Failure Modes

2

59

0.9×

Total

91

126 loadedtarget 50150

Scenario Type Coverage

Each of the 10 canonical scenario types should have at least one concrete scenario. 25 scenarios loaded across 10/10 types.

Read-Heavy Application

moderate complexity

Write-Heavy Application

moderate, high complexity

Event-Driven System

high, moderate complexity

Realtime Collaboration

high, expert complexity

Analytics Pipeline

high complexity

Multi-Tenant SaaS

high, moderate complexity

Search-Heavy Application

high complexity

AI / RAG Application

high, expert complexity

Financial Ledger

high, expert complexity

Marketplace Platform

high, expert complexity