The Wantverse [.wv] Format
A [.wv] stream is not a file in the conventional sense. It is a structured container of executable meaning, composed of modular units called Aptivs, governed by Meaning Coordinates, and designed to adapt at runtime rather than execute fixed instructions.
This page describes the design. Today, only the GPU optimization build at adaptwithchameleon.com runs. File-based output is re-established during the first 30 days of funded milestone work, and the OS-hosted runtime, illumin8 and the other Aptivs return when the milestones are complete. Wantware is not about writing or generating code as applications.
What a [.wv] stream contains
Every [.wv] stream is built from Aptivs, self-contained units that encode logic, behavior, data, policy, signal handling, or user interaction using Meaning Coordinates. Unlike a compiled binary or a serialized data file, the components inside a [.wv] stream are semantically structured: they declare what they are for, not just what they do.
This means a [.wv] stream can be inspected, validated, composed with other streams, and updated without rebuilding or redeploying the surrounding system. Trust enforcement and access policy travel inside the stream itself, not as a separate security layer applied afterward.
Streams are registered with IANA as application/vnd.wantverse
and carry no hard limits on size. Latency is minimized through on-demand
processing and level-of-detail control. Per-stream encryption is applied
dynamically on each read/write event via StreamWeave.
How [.wv] differs from conventional formats
The closest conventional format categories each fall short in a different direction. Executables are platform-locked. Serialization formats carry data but not behavior. Containers encapsulate complexity without resolving it. AI model formats store weights but have no policy, interface logic, or runtime adaptability.
| Format type | Examples | Where it falls short |
|---|---|---|
| Executable packages | .app · .apk · .exe | Locked to platform, language, and behavior fixed at compile time |
| Virtualization formats | .ova · .docker · .vmdk | Encapsulate complexity but behavior is still defined by internal code |
| Data serialization | .json · .xml · .protobuf | Represent data, not behavior, interaction, or trust |
| Media containers | .mp4 · .mkv · .dcm | Static playback; no meaning, optimization, or simulation logic |
| AI / ML model formats | .onnx · .pt · .pb | Store weights and logic only; no policy, UI, or runtime adaptability |
Capability comparison
| Capability | [.wv] | Conventional |
|---|---|---|
| Encapsulates executable behavior and meaning | Yes | No |
| Generates live machine instructions on demand | Yes | No |
| Enforces embedded trust policies | Yes | No |
| Evolves over time without rewrites | Yes | No |
| Adapts to hardware and execution context at runtime | Yes | No |
| Handles live signal streams | Yes | Partial |
| Composable with other streams without middleware | Yes | No |
Deployment scope
A [.wv] stream contains everything needed to execute: intent, logic, policy, and optimization instructions. It requires no external build step, no platform-specific binary, and no separate security layer. The same stream deploys across cloud, on-premises, edge, and mobile environments without modification.
| Environment | Notes |
|---|---|
| Cloud | AWS, Azure, GCP, private cloud; no container orchestration required |
| On-premises | Air-gapped systems, industrial controllers, private servers |
| Edge / IoT | Streams include only the Aptivs needed; no bloat for constrained devices |
| Mobile | Tested on phones running Linux; Android, iOS, and other POSIX systems still ahead |
| OS environments | Linux (50+ distros) available; Windows and other POSIX systems still ahead |
Availability signals
Only the GPU optimization build runs today. File-based output is re-established during the first 30 days of funded milestone work. Other capabilities depend on the funded milestones, Synergy and StreamWeave.
| Capability | Status |
|---|---|
| SPIR-V generation at runtime via Chameleon (file export not yet available) | Available now |
| File-based [.wv] export (Chameleon path) | Re-established during the first 30 days of funded milestone work |
| OS-hosted runtime execution (Morpheus path) | Returns when the milestones are complete |
| StreamWeave per-stream encryption | In development |
| SecuriSync continuous trust enforcement | In development |
| Synergy dialog-based stream creation (codeless path) | In development |
| Full [.wv] product deployment across all Aptiv types | Pending Synergy milestone |
A [.wv] stream is the deployment unit of Wantware, carrying behavior, policy, and execution instructions in a single adaptive structure. It is not a replacement for existing build pipelines; Once file-based output is re-established, exported artifacts are designed to integrate with standard CI/CD. The runtime capabilities that make streams fully adaptive depend on Synergy and StreamWeave, which are in active development.