Systems that move. Think in fields.VORTEX FRAMEWORK

Vortex Framework A polynomial-time compute framework composing semantic compression, secure containers, portable binaries, graphics, data, and distributed systems.

ENTERTHE FIELD

Architecture with a pulse

Architecture with a pulse.

Vortex operates through an explicit polynomial-time execution model across its supported 1D–27D logical representations. It treats information as a living stream: split into semantic segments, shaped for locality, carried across fibers, then rejoined with meaning intact.

VME / Vortex Mathematics Engine

A thousand paths through one idea.

27D / LOGICAL

ACTIVE STRANDS / —

EXECUTION MODEL polynomial-time PATH bounded work, explicit paths LOCALITY fiber-local, logical rejoin

OPEN-LOOP TORUSData streams through an open-loop torus processing structure that folds work across fibers without closed circular dependencies.

1D – 27D LOGICALLogical representations scale from a simple line to 27-dimensional forms; higher dimensions fold into bounded lanes.

FIBERS / 16–1024Dynamically scheduled logical data lanes, scalable from 16 to 1,024 active fibers in increments of 16.

POLICY TARGETSPer-fiber policy throughput targets may be 2, 4, 8, 16, or 32 KiB per millisecond.

NOTE / The interactive field above is a conceptual projection for illustration. Fiber counts and per-fiber throughput figures are architecture and policy targets — not measured or guaranteed hardware throughput by any specific deployment.

AVM / Abstract Vortex Machine

The Vortex core, made portable.

One compute identity. Three operating systems.

AVM is the portable Vortex binary / runtime surface for Windows, Linux, and macOS — containing the full VME core, mathematics libraries, algorithms, a versioned runtime contract, capability discovery, and backend adapters.

CORE

VME compute scheduler and task graph

LIBRARIES

Versioned mathematics and algorithm bundles

RUNTIME

Capability discovery and backend adapters

PORTABILITY

Windows, Linux, and macOS delivery targets

NOTE / Real portability depends on the supported host, selected backend, runtime version, and the negotiated capability contract. Not every feature is available on every host.

VPL + VKL / Language layers

Close to the machine. Clear above it.

VPL / LOWER

Vortex Programming Language — the lower-level, explicit, bounded, VME-facing language. Handles typed data, memory boundaries, math operators, fiber-oriented work, and deterministic execution contracts.

VKL / HIGHER

Vortex Kernel Language — the higher-level orchestration layer for VPL. Describes parallel intent, dispatch shape, kernel orchestration, and bounded results. VKL compiles / targets VPL semantics conceptually.

normalize_field.vkl ILLUSTRATIVE

// VKL: illustrative high-level kernel declaration
kernel normalize_field(
  input: f32[n],
  output: f32[n],
  fibers: 256
) {
  for_each lane in input parallel {
    output[lane] = normalize(input[lane]);
  }

  emit output with {
    integrity: "verified",
    locality: "fiber-local"
  };
}

This is illustrative landing-page syntax. It is not a normative language specification, and the exact syntax / compiler is not claimed to be shipping.

VSL / Vortex Shader Language

One visual grammar. Many render surfaces.

VSL is the graphics and compute-facing language layer of Vortex. Target-neutral intent written once can be adapted to Canvas, Canvas 2D, WebGL, WebGPU, Vulkan, and DirectX.

Actual device features, formats, limits, and performance are determined by the selected backend adapter, not by VSL alone.

CANVAS2D raster

CANVAS 2D2D context

WEBGL3D web

WEBGPUWGPU web

VULKANnative GPU

DIRECTXnative GPU

VSL / TARGET-NEUTRAL INTENT

ADAPTER / SELECTED BACKEND

Vortex in the wild / Cyber404

A playable Vortex surface.

Cyber404 is an example of the Vortex NodeJS-TypeScript path. It is written in VSL and uses VSCC as part of its broader application architecture.

Built on the NodeJS-TypeScript runtime integration path.

Rendering intent expressed through VSL.

Uses VSCC for semantic compression within its application stack.

Configured with a stated policy target of 256 fibers at 8 KiB/ms — a configuration and policy target, not a universal measured hardware-throughput guarantee.

VISIT CYBER404 ↗

P2Pm + VSAN / distributed movement

A mesh that knows its shape.

P2Pm is Vortex's peer-to-peer mesh concept supporting sharding, clustering, distributed compute, peer-provided heavy-compute services, and capability- and locality-aware placement. VSAN — Vortex Self Aware Network — supplies real-time observability and policy signals for peer health, topology, resource pressure, workload behavior, routing behavior, identity and admission, anomaly detection, and remediation policy.

01 / SHARD

Split with intent

Partition & ownership

Partition compute and data into bounded, observable units with explicit ownership and recovery rules.

02 / CLUSTER

Coordinate capacity

Grouping & policy

Group peers by capability, proximity, policy, or workload affinity while retaining placement visibility.

03 / COMPUTE

Move the work

Dispatch & verify

Dispatch independently verifiable tasks where capacity and locality support the declared execution plan.

04 / VSAN

Watch the mesh

Observe & remediate

Use real-time telemetry for peer health, routing behavior, resource pressure, anomalies, and remediation policy.

Security positioning. P2Pm should be designed to reduce P2P risk through layered identity and admission controls, authenticated transport, authorization, rate limits, anti-replay rules, resource quotas, sybil-resistance mechanisms, anomaly detection, and continuous VSAN monitoring. No architecture can truthfully claim that every P2P attack vector does not apply. Security claims must be supported by a published threat model, implementation review, adversarial testing, and measured operational evidence.

VDBE / Vortex Database Engine

Data stays where it makes sense.

VDBE is a Vortex database-engine layer and integration surface. It coordinates with local data stores, server databases, and cloud-hosted services through explicit adapters — it does not pretend all storage models must be replaced by a single database.

Actual consistency, query behavior, security, and performance remain properties of the selected backend and deployment policy.

LOCAL / STANDARD CLOUD / HOSTED VDBE SQLite3 PostgreSQL CSV MySQL MariaDB Cloudflare D1 Vectorize MongoDB

VSCC / Semantic Compression Codec

Meaning travels lighter.

VSCC does not pretend that everything compresses. It recognizes structure, tests bounded paths, and retains the smallest complete lossless frame — or keeps the original intact.

High-entropy, already-compressed, encrypted, or random data may require raw fallback. Compression must happen before encryption when compression is intended; authentication must happen before decompression / expansion when handling untrusted content.

{ "framework": "Vortex", "modules": ["VME", "VSCC", "VLES", "VSS"], "mode": "middle-out", "integrity": "byte-exact" }

SOURCE—

SEMANTIC SEGMENTS—

SELECTED PATH—

FRAME ESTIMATE—

NET REDUCTION—

Illustrative only — not real compression. Production VSCC must measure actual encoded bytes, include complete manifest / frame overhead, and keep the raw fallback when no complete-frame net saving exists.

Research / conceptual models

The shape of less.

Conceptual module visualizations. Values are illustrative design models — not measured performance claims.

01 / VSCC

Compression composition

source semantic residual

Illustrative composition of a payload separating recognizable semantic segments from residual material.

02 / VLES

Entropy normalization

raw distribution normalized residual

Illustrative normalization of a noisy distribution into a smoother, lower-entropy residual.

03 / LLM

Quantization × compression

FP16 LOW-BIT CONTAINER

Quantization and lossless-container savings must be reported separately. Quality must be validated on the target task suite. Values shown are illustrative.

04 / VSS

Secure file container

SOURCE → VSCC → VAEC → VSS → SEALED

Illustrative packaging order: compression, optional recovery protection, then authenticated encryption. No custom cryptographic primitives or guarantees are claimed.

Language & platform work

Vortex Framework languages and platform work
Language / platform	Status	Runtime notes
Assembly	Under Development	Low-level systems integration
C	Beta	Native systems and runtime integration
C++	Beta	Native compute and engine integration
Go	Beta	Services, networking, and tooling
Rust	Under Development	Safety-oriented systems integration
Python	Beta	Research, data, and automation workflows
Assembly	Beta	Assembly integration surface
PHP	Beta	Web and application service integration
COBOL	Beta	Legacy enterprise integration
Java	Beta	Enterprise services and JVM integration
C#	Beta	.NET and application integration
Ruby	Under Development	Web tooling and developer workflows
NodeJS-TypeScript (Bun, Deno)	Beta	JavaScript and TypeScript runtime integration
Vortex Bootloader	Under Development	Boot-time systems foundation
VortexOS	Under Development	Operating-system research and platform surface

Framework modules / system index

The field, indexed.

01 / AVM

Portable machine

Portable Vortex core

Cross-platform binary delivery surface for VME, math libraries, and algorithms.

02 / VME

Fiber compute

Polynomial-time fibers

Polynomial-time computation across a configurable open-loop torus.

03 / VPL + VKL

Language layers

Low and high expression

Low-level Vortex programming plus higher-level kernel expression.

04 / VSL

Shader surfaces

Graphics intent

Graphics and compute intent across web and native rendering backends.

05 / VSCC + VLES

Semantic compression

Lossless meaning

Lossless segmentation, exact transforms, and measured residual coding.

06 / VSS + VAEC

Trust and recovery

Protected frames

Authenticated envelopes plus bounded repair policy for protected frames.

07 / P2Pm + VSAN

Observed mesh

Distributed movement

Peer coordination, sharding, clustering, distributed compute, and real-time monitoring.

08 / VDBE

Data adapters

Stored where sensible

Local, server, and cloud data integration under explicit backend policy.

REDEAUX / 12

Make the system
feel alive.

Vortex Framework is a proposal for infrastructure with shape, rhythm, discipline, and verifiable operational boundaries. Built by Redeaux for the work that comes next.