Next-Generation Digital Transformation
There are literally billions 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 code into consideration.
We will describe three paths from software to WantWare below and the general steps involved in deciding the best path to meet the needs of organizations and end users.
Digital Transformation in 3-steps
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), to access platform-specific fixed-code (made from programming languages), and to generate machine instructions on demand (bypassing programming languages).
Agent Core Abilities
Agents contain 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 Meaning Coordinates 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 – Optimize
Purpose: Integrate existing software with WantWare for reducing maintenance, obsolescence, interoperability, and security challenges that are intrinsic to software.
Method:
Software engineers use the SecureSync Aptiv to setup a high-trust development and distribution environment.
Software engineers use the Aptivs within Elevate.wantverse to combine fixed source code with Meaning Coordinates to create new Aptivs.
Code Types:
- APIs
- Drivers
- Codecs
- AI/ML
- Emulators
- Any code in a supported programming language
Supported Programming Languages
C (11), C++(23), Python2/3, Lua, Javascript, WASM, Objective-C
Anything with an open source (e.g. Ruby) can be quickly added.
Supported Chipsets
CPU: x86_64, ARM64 (aarch64), RISC-V
GPU: PTX (Nvidia), GCN (AMD), and SPIR-V (intel?/generic?)
Media-Chips: vdpau
Path 2 – Modernize
Purpose: Lowering maintenance and operating costs, and increasing software quality.
Method:
Software engineers use the SecureSync Aptiv to setup a high-trust development and distribution environment.
Software engineers use the Chameleon Aptiv to transform source code from a programming language to a new one.
New source code can be used as-is or it can be repackaged as WantWare (optimized for leveraging the benefits of Essence Agents) using Path 1.
Supported Programming Languages
C (11), C++(23), Python2/3, Lua, Javascript, WASM, Objective-C
Anything with an open source (e.g. Ruby) can be quickly added.
Supported Chipsets
CPU: x86_64, ARM64 (aarch64), RISC-V
GPU: PTX (Nvidia), GCN (AMD), and SPIR-V (intel?/generic?)
Media-Chips: vdpau
Path 3 – Futureproof
Purpose: Replace software with WantWare to eliminate or reduce code maintenance, obsolescence, interoperability, and security challenges that are intrinsic to software.
Method:
Software engineers use the SecureSync Aptiv to setup a high-trust development and distribution environment.
Software engineers use the Synergy and Maven Aptivs to create products made purely from Meaning Coordinates, not programming languages.
Supported Chipsets
CPU: x86_64, ARM64 (aarch64), RISC-V
GPU: PTX (Nvidia), GCN (AMD), and SPIR-V (intel?/generic?)
Media-Chips: vdpau
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 Meaning Coordinates)
- 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 Meaning Coordinates)
- 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 Meaning Coordinates
Does not require:
- Fixed code
- Testing code
- Integrating code
- Maintaining code
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.
Watch the video – Jewel Prototype in Creator Mode
