VOIDMETRIC ARCHITECTURE
The Decoupled Dual-Metric & Stateless Edge Pipeline Architecture
Document ID: VM-ARCH-2026.08 // Classification: Open Core
— 1. OPEN-CORE STRATIFICATION MAP
To guarantee mathematical neutrality while preserving security and privacy, VoidMetric splits operations into strictly isolated repository boundaries underpinning enterprise and open-source platforms.
Houses the Astro UI layer, manual simulation sandboxes, and headless mathematical algorithms (structure, formulas, constraints). Accessible to academic peers and client infrastructure architects for code auditing. Tenant identity records and per-tenant hyperparameters are not part of this boundary.
Isolated edge worker handles raw enterprise IdP, SIEM, and telemetry webhooks (Okta, Tenable, Sentinel, et al.). Validates tokens, decrypts payloads, applies tenant-scoped normalization parameters ($fnorm$ hyperparameters: decay rate, drift volatility, sigmoid shape, priority coefficients, enabler weights, spectral scale, breaker thresholds), and transforms raw signals into the 4×3 matrix state. Per-tenant tuning keys are stored in a private KV namespace and never committed to the public repository.
Customer domain-to-identity-provider records (tenant IDs, OIDC endpoints), per-tenant hyperparameters, and latest raw telemetry snapshots are held exclusively in a private Cloudflare KV namespace, populated out-of-band during onboarding. Never committed to the public repository. The lookup logic that queries this data is open-core; the records themselves are not.
— 2. STATELESS DATA EXTRACTION PIPELINE
VoidMetric does not preserve database state for telemetry or computed metrics. Data passes directly through serverless threads at the edge, mitigating data footprint exposure.
[ Raw Inbound Telemetry Stream ] <-- Pushed via automated enterprise webhooks
│
▼
┌───────────────────────────┐
│ Private Ingestion Node │ <-- Validates token, decrypts payload,
│ (Void Worker) │ applies tenant-scoped f_norm
└─────────────┬─────────────┘
│ 12-node paddedStream + hyperparams + threat vector
▼
┌───────────────────────────┐
│ Cloudflare Queue │ <-- "voidmetric-events"
└─────────────┬─────────────┘
│
▼
┌───────────────────────────┐
│ SSII Consumer │ <-- Pure compute, zero-persistence
│ (Stateless V8 Isolate) │ runScoringEngine(stream, params)
└──────┬─────────────┬──────┘
│ │
▼ ▼
[ METRIC A ] [ METRIC B ]
Linear Additive Multiplicative Core
(Strategic (Operational
Posture) Blueprint)
│ │
└──────┬──────┘
▼
[ DIAGNOSTICS ]
WI · HF · Identity 1
│
▼
[ Structured Log ] <-- Logpush → alerting
— 3. VERIFICATION FIELD CONSTRAINTS (4×3 MATRIX)
Every log entry maps dynamically into specific coordinates inside the $4 \times 3$ verification fabric. The engine ensures that administrative checkmarks can never subsidize critical technical flaws.