Next-Generation Digital Transformation:

From Software to Wantware

Wantware solutions (products built with semantic units) have many unique and potentially world changing advantages over solutions based on software (products built with programming languages). There are literally trillions of lines of code in systems around the world. It would be ludicrous to suggest that a viable way ahead for the technology industry does not take into consideration legacy systems. We have given considerable thought to the question, what are the pathways from software to wantware? We will describe three paths below and the general steps involved in deciding the best path to meet the needs of end users.

Digital Transformation in 3-steps

Step 1 – Assess

Step 2 – Decide

Step 3 – Integrate or Replace

Step 1: Assess Fit

Establish if there is an Essence Agent for the target platform

The Essence Agent is the brains of the Essence Platform. Agents are singular executable programs with various operating system privileges when built for an external OS. The Agents’ role at startup is to load the Origin, Host, User-Style & User-History wantverses (a customizable Essence world), and to access platform-specific code on demand via the Essence Powers System.

Agent Core Powers

Agent Core Powers are 8 packages of ‘hard-coded’ instructions that utilize a knowledge-database and supporting data that has been trained and tuned for the specific platform, its generic and unique features, and all the caveats that must be observed to optimally regenerate machine instructions, and to run and evaluate fixed code on the fly.

Bootup & Spawn

Operating System specific process-launching/thread-spawning or Hardware UEFI/BIOS specific or both for startup process (~1 msec startup).

      

Resource Accessor

Handles initial processor/bus/memory assessment and resource pooling.

User Setup

Identity Confirmation and Location Probing (find current user, their last Essence session, along with style, rules, and history).

Authenticator

Manages a variety of verifications, guards, and runtime trust-checks. Only handles the other 7 Powers and itself but does so natively at startup.

Instruction Maker

Matches streams of Essence Atoms into foundation segments of hardware-machine code or emulation code for 1 or more boot-time chips such as CPUs, Bus-controllers, DSPs, Media-Codecs, and other chips available at startup or uniquely configured (SoC).

Executor

Handles connecting a series of ‘Code-Maker’ results with other Powers from other wantverses based on the platform’s prior runs and training/history data with ranges of scored (good/neutral/bad) results.

Referee

Manages issuing, assessing, and balancing various results of the Code Maker running across the currently available chip.

Terminator

Manages all shutdown or unrecoverable error states, blackbox logging, and cleanup issues specific to our Platform.

Step 2: Determine Migration Path

Path 1 Pros & Cons

Pros

  • Minimal change approach
  • Allows for narrowly focused use cases
  • Leverages existing source code
  • Supports customizable pacing
  • Increases quality of existing code
  • Improves security, risk management, compliance
  • Recommended for large legacy systems
  • No lock-in

Cons

  • Fixed code 
  • Flawed code
  • High maintenance
  • Vulnerabilities/Risks
  • Obsolescence built-in
  • Interoperability issues 
  • Limited composability
  • Not all platforms are supported

Path 2 Pros & Cons

Pros

  • Supports modernization of source code
  • Meets needs t modernize, without fully transitioning away from fixed source code
  • An exit ramp from legacy software
  • Provides improved robustness, efficiency, performance, interoperability, scalability, composability, explainability (via Essence Atoms)  
  • Should be considered for replacing large legacy systems
  • No lock-in

Cons

  • Fixed code
  • Flawed code (introduced by manual entry by coders)
  • Higher maintenance than path 3
  • Obsolescence built-in
  • Interoperability issues 
  • Limited composability
  • Not all platforms are supported
  • Not all programming languages are supported

Path 3 Pros & Cons

Pros

  • A fresh start approach
  • Adapts to changing operating environments and requirements
  • An exit ramp from legacy software
  • Eliminates all known vulnerabilities
  • Provides robustness, efficiency, performance, interoperability, scalability, full composability (via Essence Atoms)  
  • Best for creating new products
  • Should be considered for replacing large legacy systems
  • No lock-in

Cons

  • Will take time to establish trust
  • Not all OS platforms are supported

Step 3: Integrate

Example 1

Integrating browser engine source code with wantware

  • Unit Testing
  • Qualified Compiling
  • Post-quantum Encryption
  • Multi-stage Compression
  • Code-signing
  • Security, Risk, Compliance Hardening
  • Runtime Verification

In this example, we have the Jewel product that incorporates browser engines Webkit and Chromium. The browser engine source code needs to be packaged as Powers.

Step 3: Integrate

Example 2

Integrating driver source code with wantware

  • Unit Testing
  • Qualified Compiling
  • Post-quantum Encryption
  • Multi-stage Compression
  • Code-signing
  • Security, Risk, Compliance Hardening
  • Runtime Verification

In this example, we have the illumin8 product running on multiple devices. There’s a device driver update that needs to be packaged as a Power. 

Step 3: Replace

Example 3

Replacing source code with semantic units (Atoms)

APIs
Drivers
Codecs
AI/ML
Emulators
Browser Engines
Virtual Macines
Etc.

A sample app showing wantware using NLP (Natural Language Processing), NLD (Natural Language Dialogue), transforming meaning into different representations (non-technical, technical, and machine instructions) that results in a working app.  

What’s Inside of a Wantware-powered Browser?

Jewel is a revolutionary new way to experience the web. We will use it as an example Aptiv.

Jewel is an Aptiv used to browse, analyze, and extract information from webages using HTML5, JavaScript, CSS, and WebGL with DOM (document object model).  Simply put, users of Jewel can create/interact/control their experiences without being a coder.

The Essence Agent Powers, the platform-specific Powers, Essence Atoms (a sample), and required Wantverses used by Jewel are described below.

1 – Essence Agent Core Powers

Operating System(OS) specific process-launching/thread-spawning or Hardware UEFI/BIOS specific or both for startup process (~1 msec start)

Handles initial processor/bus/memory assessment and resource pooling.

Identity Confirmation and Location Probing (find current user, their last Essence session, along with style, rules, and history)

Manages a variety of verifications, guards, and runtime trust-checks. Only handles the other 7 Powers and itself but does so natively at startup.

Matches streams of Essence Atoms into foundation segments of hardware-machine code or emulation code for 1 or more boot-time chips such as CPUs, Bus-controllers, DSPs, Media-Codecs, & other chips available at startup or uniquely configured (SoC).

Handles connecting a series of ‘Code-Maker’ results with other Powers from other Wantverses based on the platform’s prior runs and training/history data with ranges of scored (good/neutral/bad) results.

Manages issuing, assessing, and balancing various results of the Power04:Code-Maker running across the currently available chip.

Manages all shutdown or unrecoverable error states, blackbox logging, & cleanup issues specific to the Platform.

2 – Powers

Enables management and throttling of tasks for our platform, the resources requested, and load balancing everything requested by the user. Includes core threading or multitask models, parallel scheduling, and memory models for read/write of cached RAM, direct RAM (like HP), transactional or quantum units.

Enables ciphers, obfuscation, and other encryption affiliated tech, including ledgers (e.g., blockchain).

Sense can be traditional controllers or classic input signals. Sensors enable discreet Communication between a user and a device, such as Touchscreens, Keyboards or Gyro meters.

Sense Powers also gather analog signal data that may be processed or resampled, such as Cameras, Mics, or Thermometers.

Enables detecting connections, finding locations, and verifying successful transfer of timely data to storage connections.

Enables translation between external data formats and network protocols, separate from the Store approach.

Run a simulation’s update as a step in time. Includes software and hardware emulation running former or imagined computer hardware, video game consoles, operating system configurations, virtual machines, web browsers, or other software applications as interfaces.

Editing covers the add, modify, and remove cycles for a domain of data, such as database editing, scene placement, stage directions, or presentation crafting. Note that text-editing/word-processing occurs here for the atomic units of text/words/documents but the specifics of text, as symbol-streams, is handled by Symbolize.

Enables field processing math equations across dimensions of streams of numbers.

Note: There are likely 20+ additional Powers used by every one of the Powers above.

3 – Skills

Natural Language Processing | Natural Language Dialog

Synergy takes sloppy English or other natural or even made up languages and maps it to “meaning units” that an Essence computer can represent and express as data and machine instructions (binaries, not programming languages). Thus, it converts “your unique wants into what your hardware (phone, tablet, PC, smart watch, etc.) can do. The user interface, math functions, data models, algorithms, etc. are accessed via the appropriate possibility boxes and regenerative machine instructions made in real-time and then deleted, like SnapChat messages. An example of interacting with Jewel, the corresponding Atoms (combined to form compounds) and the corresponding meanings is below.

4 – Wantverses

Startup Wantverses

Wantverses are containers that have many possibility boxes inside of them. The Essence Agents’ role at startup is to load 4 Wantverses—the Origin, Host, User-Style & User-History to create a customizable Essence world.

  1. Origin – Origin is the starting wantverse filled with foundational ideas and abilities for all platforms. It includes all the foundation Ideas, Records, Actions, and SpaceTimes for interfacing between human and machine.
  2. Host – a specific wantverse with as many device specific capabilities exposed as possible.
  3. User-Style – an individual users’ wantverse of the style/design/terms/etc.  and personal wants on particular machine, not everywhere
  4. User-History – a wantverse storing the users’ past events.

Jewel Browser Specific Wantverses

The Technology Wantverses

(Available for everyone’s collective use)

The starting wantverse filled with foundational ideas and abilities for all platforms. It includes all the foundation Ideas, Records, Actions, and SpaceTimes for interfacing between human and machine.

A specific wantverse with as many device specific capabilities exposed as possible.

An individual users’ wantverse of the style/design/terms/etc.  and personal wants on a particular machine, not everywhere.

The Design Wantverses

(Available for everyone’s collective use)

Your Everywhere Shared Designs is a Wantverse storing shared rules, styles, and configuration preferences for this user across all computer hosts.

A wantverse storing the users’ past events.

The Story Wantverses

(Available for everyone’s collective use)

Your Live_Events is a Wantverse storing your live events.

Your Story_History is a Wantverse storing your past events.

The Experience Wantverses

(Available for everyone’s collective use)

The Home Experience Wantverse delivers your packaged possibilities available for use.

The Browser Experience Wantverse lets users find experiences and match desired capabilities or learn about possibilities.

The Trader Experience Wantverse manages how to trade possibilities in a market place with other users.

The Maker Experience Wantverse lets users modify or create worlds using design-focused capabilities.

About Possibility Boxes

The Nebulo approach to data management provides an opportunity to move away from the legacy approach of files and databases with their fixed and limited formats for locating and referencing information. Moving data between systems is often possible. However, this is typically with varying degrees of compromise. This happens because there is generally no easy way to take both data and code behaviors that exist in one system to another. Nebulo changes that by enabling both data and code behaviors to become like Lego Bricks.

Data storage and access are separate from the data structure of the ‘Thing’ (uniquely named entities/objects) itself for a variety of reasons. We have 8 types of ‘possibility boxes’ (described below) based on how we can scale data (lossy-signal, exact-record, rolling-queue history, belief-certainty thoughts, etc.).

Granular security/access issues are handled by each ‘Essence Possibility Box’ so whether you can edit or read-only or just name-only or ‘nothing/no-awareness’ is determined from within each Box…not a central (potentially hackable) system.

Think Box

Cognitive possibility existing in thought

Record Box

Groups of sequences of items represented as discrete ideas

Signal Box

Forms of continuous ideas sampled in multiple dimensions

Ability Box

Groups of context specific actions that change things in spacetime

Chronical Box

Collections of events that recreate an experience in spacetime

Spacetime Box

Collections of scenes containing things that change with time

Belief Box

Ongoing collections of observations, opinions and predictions

Idea Box

Collections of ideas that form a unique concept

Products in Development

The Democratization of Computing

We’ve done the heavy lifting, which involves patented transformative breakthroughs in mathematical approaches to generating algorithms and meaning representation that goes beyond (human and machine) languages.

WantWare enables the many products in our own roadmap, to be developed rapidly and to require far less maintenance than is required by the current software development process. The functionality needed to create those and an endless number of products already exists within the abilities of the Essence Agent. It totally makes sense once it is understood that WantWare is fundamentally about intent translated and transformed into machine instructions, in real-time.

The products in development above are just the tip of an enormous iceberg. There’s much more underneath the surface. Software evolved is wantware!

Get ready to create at the speed of thought.

Wantware Inside

Introduction to Wantware – Understanding Scale and Scope of Wantware as a Solution

From Software to Wantware – Learn How Software Becomes Wantware

The Essence Platform – Democratizing Web3 and Computing in General

The Essence Aptiv – A New Way to Harden Code by Reducing Code

The Essence Agent – The brains of the Essence Platform

The Essence Powers System – A New Code and Data Packaging System

The Essence Skills System – All the ways that humans interact with WantWare-powered machines

Nebulo® – Translatable data structures for adaptively managing data and code with semantic intelligence

Essence Atoms, a way to map intent to meaning to regenerative machine instructions, not fixed code.

MorpheusTM – A pathway to platform agnostic computing based on platform-specific regenerative machine instructions

Maestro® – Balancing sensory quality in response to latency and user-level choices, in real-time

As we discuss our technology with engineers, we will post answers to their questions on our website.