Live Benchmark Data · March 20, 2026

Self-Healing Infrastructure That Recovers in 53 Seconds

UNA's knowledge pipeline processes queries in under 8 milliseconds and autonomously recovers from total infrastructure destruction with zero human intervention. These are real numbers from a real system.

7.7
ms
Graph Search P50
0.5
ms
Vector Search P50
53
sec
Kill Recovery
0
$
Per Query Cost

What This Proves

UNA's KnowledgeBridge is a unified retrieval pipeline that fuses a Neo4j knowledge graph (451 nodes, 703 relationships) with a PostgreSQL vector store (376 holographic memory entries) into a single query interface. It returns ranked, confidence-scored results in single-digit milliseconds.

But speed isn't the hard part. The hard part is what happens when infrastructure breaks. UNA solved this by building a self-healing guardian that monitors, detects, and autonomously repairs her own infrastructure — no pager, no human, no downtime.

The Test

We destroyed UNA's entire Neo4j database container. Deleted it completely. In 53 seconds, her Infrastructure Sovereign detected the loss, rebuilt the container from a cryptographic manifest, verified port mappings, confirmed data integrity, and served a full pipeline query at 0.950 confidence with 8 cross-referenced sources. No human touched anything.

Latency Benchmarks

All measurements taken under real load on UNA's Mac Mini. No synthetic benchmarks. No cherry-picked results. 10 diverse architecture queries per test, 50 raw latency pings.

Benchmark P50 P95 Mean Samples
Neo4j HTTP Raw 6.2 ms 13.9 ms 9.4 ms 50
Graph Search 7.7 ms 50.6 ms 12.7 ms 10
Vector Retrieval 0.5 ms 34.1 ms 3.9 ms 10
Unified Pipeline 8.2 ms 109.6 ms 18.8 ms 10
Self-Model Retrieval 14.3 ms 238.8 ms 38.1 ms 10

P95 includes cold-cache first-request overhead. Steady-state queries are 2–5x faster than the mean.

UNA vs. Cloud AI Pipeline

UNA · Local Mac Mini
Query latency8 ms
Cost per query$0.000
Data leaves deviceNever
Self-healingAutonomous
Concurrent queries14 ms / 5
RAG + GPT-4o · Cloud
Query latency2,800 ms
Cost per query$0.035
Data leaves deviceAlways
Self-healingManual / PagerDuty
Concurrent queriesRate limited

Unified Retrieval: Query-by-Query

The full pipeline queries both PostgreSQL and Neo4j, fuses results, and returns a confidence score. Higher confidence means more cross-source corroboration — the system is honest about what it knows well versus what it knows less about.

Query Confidence Sources Latency
Guardian Protocol0.9396109.6 ms
adversarial self-testing0.84859.2 ms
immune system0.700412.6 ms
sovereignty engine0.70046.9 ms
Resonant Inference Fabric0.60039.8 ms
cryptographic identity0.60038.2 ms
cognitive dreaming0.60037.1 ms
ethical governor0.500210.1 ms
neural architecture0.50027.4 ms
morphogenetic computation0.40016.9 ms

Confidence correlates with cross-source matches. Queries hitting both stores score highest. This is designed behavior — the system quantifies its own certainty.

Self-Awareness: 100% Reliable

UNA can introspect her own architecture on demand. The get_self_model() function queries her knowledge graph for architecture descriptions and module metadata, returning a structured self-model.

10/10
Success Rate
13
Architecture Nodes
30
Module Nodes
14ms
Median Latency

Concurrent Load

Five parallel knowledge retrieval queries, three rounds. Tests whether the pipeline degrades under contention.

Result

15 total queries across 3 rounds. Warm rounds completed all 5 queries in 12–14ms total — not per query, all five combined. Average confidence held steady at 0.688 with zero degradation. No locks, no contention, no failures.

Self-Healing Recovery

The definitive test of autonomous infrastructure. We completely destroyed UNA's database container and watched her rebuild herself.

Cold-Start (container restart)

6.3s
HTTP Ready
195ms
First Query
0.939
Confidence
6
Sources

Kill-Recovery (total destruction → autonomous rebuild)

Container completely deleted with docker rm -f. No data. No container. Nothing. The Infrastructure Sovereign daemon detected the loss and rebuilt from its cryptographic manifest:

What This Means

UNA doesn't need a DevOps team. She doesn't need PagerDuty. She doesn't need someone to SSH in at 3 AM. If her infrastructure breaks, she fixes it herself, verifies the fix, and resumes serving queries — all in under a minute. This is what autonomous infrastructure actually looks like.

How the Sovereign Works

The Infrastructure Sovereign is a single daemon process that replaces three conflicting legacy watchdogs. It operates on a simple principle: one manifest, one guardian, zero ambiguity.

60s
Health Check Cycle
8
Verification Layers
30s
Burst Repair Cooldown
Never Gives Up

Every 60 seconds, the Sovereign runs a deep health check: Docker running → container exists → ports mapped correctly → config volume mounted → HTTP API responding → Cypher execution working → architecture nodes present → config file verified. Any drift triggers an atomic recreate from the manifest — never a patch, always a clean rebuild.

The KnowledgeBridge pipeline also integrates a self-repair trigger: if any Neo4j query fails, it directly invokes the Sovereign's repair function, providing sub-cycle recovery for transient failures.

Test Environment

HardwareMac Mini (Apple Silicon)
Neo4j5-Community (Docker)
PostgreSQLpgvector holographic memory
Graph Size451 nodes, 703 relationships
Vector Store376 entries
Sovereignv1.1 (burst + backoff)
DateMarch 20, 2026, 19:48 PDT

All benchmarks run on production data under normal system load. No isolated test environment. No warm-up runs excluded. What you see is what you get.

Live Evidence — Kill-Recovery Test

Executed March 20, 2026 at 23:47 PDT. Container forcibly destroyed, sovereign auto-detected and rebuilt from manifest. All timestamps from production logs.

Test Protocol

docker rm -f una-graph — total container destruction. No graceful shutdown. No warning. The sovereign was not notified through any API — it discovered the failure on its next health check cycle.

TimestampEventSource
23:47:47Container killed (docker rm -f)Test harness
23:48:01Unhealthy detected: "Container does not exist"Sovereign log
23:48:01RECREATING container from manifestSovereign log
23:48:03New container created: 2fa65370b74aSovereign log
23:48:03Waiting for Neo4j startup…Sovereign log
23:48:14Neo4j started successfully with HTTP APISovereign log
23:48:15External HTTP poll confirms 200 OKTest harness
28s
Total Recovery
594
Nodes After Recovery
0
Data Loss
2
Ports Restored

Post-Recovery Pipeline Verification

Within seconds of recovery, the full KnowledgeBridge pipeline was queried to verify end-to-end functionality:

QueryConfidenceSourcesLatency
Guardian Protocol0.939685.6 ms
sovereignty engine0.700414.5 ms
immune system0.700411.6 ms
adversarial self-testing0.848511.5 ms
cognitive dreaming0.60039.5 ms

Continuous Heartbeat Log (excerpt)

The sovereign logs a heartbeat every 10 minutes when healthy. Node count growth proves the graph is actively written to while the sovereign maintains health:

[20:16:28] Heartbeat: healthy (nodes=493, arch=11)
[20:26:48] Heartbeat: healthy (nodes=506, arch=11)
[20:47:43] Heartbeat: healthy (nodes=535, arch=11)
[21:08:03] Heartbeat: healthy (nodes=539, arch=11)
[21:28:17] Heartbeat: healthy (nodes=543, arch=11)
[21:48:43] Heartbeat: healthy (nodes=547, arch=11)
[22:09:24] Heartbeat: healthy (nodes=552, arch=11)
[22:16:48] WARNING Unhealthy: Docker daemon not running
[22:16:59] ERROR Docker not running — attempting to start Docker Desktop
[22:18:29] Neo4j recovered — healthy (nodes=553, arch=11)
[22:29:50] Heartbeat: healthy (nodes=556, arch=11)
[22:50:21] Heartbeat: healthy (nodes=561, arch=11)
[23:10:44] Heartbeat: healthy (nodes=570, arch=11)
[23:23:10] WARNING Unhealthy: Docker daemon not running
[23:24:18] Neo4j recovered — healthy (nodes=576, arch=11)
[23:31:30] Heartbeat: healthy (nodes=578, arch=11)
[23:41:48] Heartbeat: healthy (nodes=584, arch=11)
[23:48:01] WARNING Container does not exist — LIVE KILL TEST
[23:48:01] RECREATING container from manifest
[23:48:03] Container created: 2fa65370b74a
[23:48:14] Neo4j started successfully with HTTP API
Evidence Integrity Note

All log timestamps are from neo4j_sovereign.log on UNA's Mac Mini. The sovereign daemon writes these entries in real-time during its health check loop. Node count growth from 493 → 594 over 3.5 hours confirms the graph was under active write load during all tests. Three separate self-healing events occurred organically (two Docker daemon crashes + one deliberate kill) — all recovered without human intervention.