Meta-Version Tracking for Verifiable Multi-Source Artifacts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face challenges in independently verifying results across different entities and managing complex information systems with independently changing data and software versions, leading to inefficiencies in storage and verification processes.
Innovation Solution
A meta-version tracking system (MVTS) that classifies and tracks three types of sources—persistent, non-persistent with version tracking, and non-persistent without version tracking—enables independent verification and productization of complex information systems by preserving a cohesive state of computational systems through meta-version labels, allowing entities to recreate and verify results accurately.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current systems store and manage data and software versions independently, then each entity can maintain its own version, but verification between entities becomes complex and storage space increases
Solution Approach 1:
The patent merges the version management of multiple independent entities into a unified meta-versioning system. The meta-version tracking system consolidates version information from different data sources and software components, allowing entities to verify results against a common reference framework without requiring duplicate storage of all versioned artifacts.
Solution Approach 2:
The meta-version tracking system acts as an intermediary between different entities that need to verify results. It maintains a centralized registry of meta-versions that reference actual data and software versions, enabling verification without requiring entities to store complete copies of all versions themselves.
2Adaptability or versatility
If data and software versions change independently across different entities, then each entity can update its components, but maintaining coherent verification becomes difficult
Solution Approach 1:
The patent segments the versioning process into two independent layers: entity-level versions (data and software) and meta-versions (system-wide snapshots). This segmentation allows entities to update their components independently while the meta-versioning system tracks the coherence relationships between these updates, maintaining verification consistency.
Solution Approach 2:
The meta-version tracking system performs preliminary recording of version relationships before changes occur. By establishing meta-versions that capture the state of multiple entities simultaneously, the system creates a reference framework that maintains verification consistency even as entities independently update their versions.
3Measurement precision
If the system tracks all versions of data and software, then complete verification is possible, but system complexity increases
Solution Approach 1:
The patent extracts the essential verification information from the complete version history and represents it through meta-versions. Instead of tracking every individual version detail, the system identifies and stores only the critical version snapshots that represent coherent states of multiple entities, reducing complexity while maintaining verification accuracy.
Data Source
AI summary
Systems and methods for verification of a result of execution of a computational system, including generating the result by executing elements of a computational system by a developer party, saving the result in a computer storage, preserving a current state of elements of the computational system by creating a meta-version label in a meta-version tracking system for the meta-version of the computational system and linking the elements of the computational system to the meta-version label, sending to the meta-version tracking system a request to verify the result of the computational system by a verifying party, recreating and deploying elements of the computational system by transferring information to an external device, generating a verification result, and comparing the verification result to the result previously generated.