Abstract: Systems and methods are provided for publishing immutable references to geospatial data. In embodiments, a method includes identifying geospatial data of a data provider, wherein the geospatial data is associated with a grid element of a discrete global grid (DGG); generating, in a grid element data store, an immutable reference in time to the geospatial data, the immutable reference including a pointer to a unique label of the grid element of the DGG and a storage location of the geospatial data; receiving a data request from a user, the data request including location information identifying the grid element; and providing a response to the user including the storage location of the geospatial data associated with the grid element to enable access of the geospatial data by the user, wherein the immutable reference provides a guarantee that the geospatial data is originating from the data provider.

Abstract: Verifiable test case workflow is provided by creating a secure database for actions taken regarding a source file that is stored on a first computer; creating a test executable from one or more source files and storing it on the first computer; finalizing the source file for test on a second computer different from the first computer; hashing a test environment related to the source file and the second computer; and in response to determining that a version of the test executable provided to the second computer matches a version of the test executable provided to the secure database: executing the test executable on the second computer; hashing test results from testing the source file on the second computer; and adding the test executable as hashed and the test results as hashed to the secure database to actions already stored in the secure database.

Abstract: Verifiable test case workflow is provided by creating a secure database for actions taken regarding a source file that is stored on a first computer; creating a test executable from one or more source files and storing it on the first computer; finalizing the source file for test on a second computer different from the first computer; hashing a test environment related to the source file and the second computer; and in response to determining that a version of the test executable provided to the second computer matches a version of the test executable provided to the secure database: executing the test executable on the second computer; hashing test results from testing the source file on the second computer; and adding the test executable as hashed and the test results as hashed to the secure database to actions already stored in the secure database.