Conpack E2E Eval Results

Generated: 1772164344s-since-epoch

Summary

No Ctx WORST
0.0%
confidence  |  pass rate: 0%
0.2s
avg time  |  p95: 0.2s  |  p99: 0.2s  |  best: 0.2s

Comparison

MetricNo Ctx
Avg Confidence0.0%
Pass Rate0%
Avg Time0.2s
Time P950.2s
Time P970.2s
Time P990.2s
Best Time0.2s
Success Rate0/3
Timeouts0
Errors3

Coverage Matrix (Strategy × Vertical)

StrategyNo Ctx
fts0% (0/1)
vector0% (0/1)
cascade0% (0/1)

Seed Routing

SeedStrategyTarget Upstream
zephyr-query-protocolftselasticsearch-fts
conpackdb-ring-bufferftselasticsearch-fts
conpack-cluster-terraformftselasticsearch-fts
prismoid-cache-coherenceftselasticsearch-fts
vortex-ingestion-pipelinevectorqdrant-vector
helix-embedder-trainingvectorqdrant-vector
obsidian-vault-syncvectorqdrant-vector
crystalline-tensor-decompositionvectorqdrant-vector
nexara-meridian-consensuscascade(cascade — priority order)
auralis-service-meshcascade(cascade — priority order)
spectral-query-analyzercascade(cascade — priority order)
solaris-event-meshcascade(cascade — priority order)
12 seeds: 4 FTS, 4 vector, 4 cascade

Per-Strategy Recall

StrategyNo Ctx
fts-
vector-
cascade-

Per-Query Confidence

QueryStrategyNo Ctx
q-001What is the Zephyr Query Protocol and how does its three-phase handshake work?ftsERR
q-004How do you configure the Vortex ingestion pipeline stages and dead-letter handling?vectorERR
q-003Explain the Meridian consensus protocol used by Nexara and its temporal sharding approachcascadeERR

Query Details

q-001 No Ctx — What is the Zephyr Query Protocol and how does its three-phase handshake work?
Expected: eval-001 — Zephyr Query Protocol v3.2 Specification
The Zephyr Query Protocol (ZQP) v3.2 introduces scatter-gather query routing with adaptive fan-out. ZQP uses a three-phase handshake: DISCOVER, NEGOTIATE, STREAM. The DISCOVER phase broadcasts topology probes to all registered shards using multicast group 239.17.42.0/24. NEGOTIATE selects optimal shards based on affinity scores computed via the Kessler-Huang ranking algorithm. STREAM delivers results using chunked transfer with backpressure signaling via ZQP-FlowControl headers. Configuration requires setting zqp.scatter_factor (default 3), zqp.negotiate_timeout_ms (default 150), and zqp.stream_window_size (default 64KB). The protocol supports both synchronous request-response and asynchronous push modes controlled by the zqp.mode parameter.
VerticalDocMatchConfidenceTimeMatched Terms
No Ctxeval-001NO0.0000.2s
Agent Responses
No Ctx — FAILED

No response captured

q-004 No Ctx — How do you configure the Vortex ingestion pipeline stages and dead-letter handling?
Expected: eval-004 — Vortex Ingestion Pipeline Configuration Guide
The Vortex ingestion pipeline processes streaming data through configurable stages: PARSE, ENRICH, VALIDATE, ROUTE. Each stage runs as an isolated actor with bounded mailboxes (vortex.stage.mailbox_size, default 4096). The PARSE stage supports JSON, Avro, Protobuf, and custom formats via pluggable deserializers registered in vortex.parsers[]. ENRICH applies transformation rules defined in vortex.enrichment_rules[], supporting field mapping, regex extraction, and lookup joins against reference tables. VALIDATE enforces schema contracts using Vortex Schema Language (VSL) files referenced by vortex.schema_path. ROUTE distributes validated records to downstream sinks based on content-based routing rules in vortex.routing_table[]. Dead-letter handling sends invalid records to the vortex.dlq_topic (default 'vortex-dlq'). Backpressure propagates upstream when any stage's mailbox exceeds 80% capacity.
VerticalDocMatchConfidenceTimeMatched Terms
No Ctxeval-004NO0.0000.2s
Agent Responses
No Ctx — FAILED

No response captured

q-003 No Ctx — Explain the Meridian consensus protocol used by Nexara and its temporal sharding approach
Expected: eval-003 — Nexara Consensus: The Meridian Protocol
Nexara implements the Meridian consensus protocol, a Byzantine fault-tolerant algorithm designed for geo-distributed clusters. Meridian operates in three rounds: PROPOSE, CERTIFY, COMMIT. Unlike traditional BFT protocols, Meridian uses a rotating committee of 2f+1 validators selected via verifiable random functions (VRFs). The protocol achieves 50,000 TPS in WAN configurations with 100ms finality. Key parameters include meridian.committee_size (default 7), meridian.vrf_threshold (0.67), and meridian.proposal_timeout_ms (default 200). Meridian introduces the concept of 'temporal sharding' where consensus rounds are partitioned across time slots to reduce message complexity from O(n^2) to O(n*log(n)). The Nexara implementation uses the Ed25519 signature scheme for vote signing.
VerticalDocMatchConfidenceTimeMatched Terms
No Ctxeval-003NO0.0000.2s
Agent Responses
No Ctx — FAILED

No response captured