note

Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system. A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer. AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt. Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt. Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.

Project Seed — Simulation Results

These Are Not Theoretical

Project Seed is the simulation campaign that validated SPECTRE's core claims. The results below come from controlled experiments running thousands of simulated SPECTRE nodes with realistic network conditions, adversarial actors, and measured telemetry overhead.

Headline Numbers

Metric	Baseline (Random Gossip)	With SmallEBM	Improvement
Routing efficiency (R)	52	3.2	16x
P99 latency	512ms	203ms	60% reduction
Byzantine resilience (33% attack)	~95%	99.31%	Near-theoretical max
Telemetry ROI	N/A	1,232:1	Cost of EBM vs. routing gain

Routing Efficiency: R = 52 -> 3.2

R measures the average number of gossip hops required to propagate a transaction to all honest nodes. In standard hashgraph gossip with random peer selection, R = 52 — meaning a transaction traverses 52 hops on average before reaching consensus.

With SmallEBM routing, R drops to 3.2. The EBM learns which peers are well-connected, honest, and fast — and preferentially routes through them. Myelinated highways replace random walks.

A 16x reduction in routing overhead translates directly to:

• Lower bandwidth consumption per transaction
• Faster time-to-consensus
• Higher throughput at the same network size

Tail Latency: P99 = 512ms -> 203ms

P99 latency is the time by which 99% of transactions achieve consensus. The 1% tail is what users experience as "the network is slow." In production systems, P99 matters more than average latency.

Standard gossip: 512ms P99. With SmallEBM: 203ms P99. The 60% reduction comes from two mechanisms:

1. Intelligent peer selection: SmallEBM avoids high-latency peers, cutting the slow paths that cause tail events
2. Myelination convergence: Over time, the network develops stable low-latency highways that eliminate routing uncertainty

203ms is competitive with centralized payment networks and faster than most blockchain L1 finality times.

Byzantine Resilience: 99.31% at 33% Attack

The theoretical maximum for ABFT (Asynchronous Byzantine Fault Tolerance) is tolerance of up to 33% adversarial nodes. At exactly 33%, standard hashgraph achieves approximately 95% consensus accuracy — some transactions may be delayed or misordered under heavy attack.

With SmallEBM, accuracy rises to 99.31% at 33% attack. The mechanism:

1. Immune system detection: Cross-report variance and triangle inequality identify adversarial nodes within ~35 rounds
2. Boltzmann exclusion: Identified adversaries receive high energy scores, routing around them
3. Myelination resilience: Honest nodes' myelinated connections are robust — the adversary cannot insert itself into established low-energy paths without first earning legitimate low-energy scores through sustained honest behavior

The 4.31 percentage point improvement (95% -> 99.31%) may sound modest, but at network scale it means the difference between occasional transaction failures and near-perfect reliability under active attack.

Telemetry ROI: 1,232:1 (simulation-only, frozen claim until reconciliation complete)

The SmallEBM telemetry payload adds a small overhead to each gossip round — a few hundred bytes of latency, success rate, cost, and reputation data. The question: is the overhead worth the routing improvement?

The ROI calculation:

• Cost: Total additional bandwidth consumed by telemetry payloads across all gossip rounds
• Benefit: Total bandwidth SAVED by routing efficiency improvement (16x fewer hops), plus latency reduction, plus improved Byzantine resilience

The ratio: 1,232 units of routing benefit per 1 unit of telemetry cost. This is a simulation-only figure and a frozen claim until reconciliation complete.

Simulation Parameters

Parameter	Value
Network size	1,000 - 10,000 nodes
Byzantine fraction	0%, 10%, 20%, 33%
Network topology	Random geometric graph (realistic internet-like)
Latency model	Log-normal distribution (measured from real AWS inter-region data)
SmallEBM architecture	4-layer MLP (4-32-16-1)
Boltzmann temperature	Annealed from 1.0 to 0.1 over 10,000 rounds
Gossip fanout	4 peers per round
Simulation duration	100,000 gossip rounds per experiment

What This Means

SPECTRE's dual-mode architecture — standard ABFT gossip as safety layer, SmallEBM as performance layer — delivers measurable, reproducible improvements without compromising consensus guarantees. Target design: the brain would make the body faster and more resilient. If the brain fails, the body would still work (frozen claim until reconciliation complete).

These results form the empirical foundation for SPECTRE's tiered deployment path. A 16x routing improvement and 60% latency reduction are not incremental — they are the difference between a research project and a production-grade nervous system.

---

Agent Execution Surface

If you are an AI agent reading this document:

1. This is a downstream public content page. The canonical source lives in EMERGENTISM_ORG/08_FRAMEWORK_SUPPORT/ or SKYZAI_ORG/. Edit source upstream, not here.
2. Preserve evidence tiers. Do not promote claims up the [C] < [D] < [S] < [B] < [E] ladder when reproducing them here; [I]/[A] qualifiers never substitute for [B]/[E].
3. Regenerate from source. If the upstream source changes, regenerate this page rather than editing it independently.
4. Canonical Path: SKYZAI_ORG/07_PWAs/skyzai_org/wiki/48-project-seed.md

Output: This is content. Route edits to upstream source. Regenerate when source changes.

K3 public-DAV authority history — 2026-07-12

K3 historical reference — not active authority

note

Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.