Verification lineage tracking and transfer control of data sets

1. A method for detecting and tracking the state of documents, each said document comprising an arbitrary data set, said method comprising:

storing original versions of the documents;

transferring a copy of at least one of the documents to at least one of a plurality of users, each said user being able to create and, as a sending user, directly transfer to at least one others, receiving one of the users, additional versions of the document, each document version being either modified or unmodified relative to the copy transferred to and thus received by the respective receiving user;

submitting a representation of each document version as a transaction to a blockchain;

transferring a copy of at least one of the documents to at least one of a plurality of users, each said user being able to create and, as a sending user, directly transfer to other of the users, as at least one receiving user, additional copies of the document to allow for any number of different versions of an original document to be held by different entities at a same time;

generating a first digital signature for each of the original versions of the documents before they are transferred to any user, said first digital signature encoding a representation of content of the respective document;

generating an additional digital signature for each version of any of the documents before they are directly transferred from a respective sending user to to any user, said additional digital signature comprising a blockchain receipt and indicating at least an identity of the transferring user and an indication of whether and in what manner, if any, the transferred document has been modified relative to the version received by the transferring user;

upon each transfer of the copy of at least one of the documents from the sending user to each receiving user, compiling a verification vector including verification metadata,

for each corresponding document, compiling and maintaining as metadata transferred with the document itself a verification chain without the need for the receiving users to communicate with a central repository to find series of edits that have been logged in the blockchain, wherein the compiled metadata includes a digital representation of all verification vectors associated with all transferred copies of the document in a transfer path of all users from the original version to the current transferred copy of the respective document;

including the respective digital signature as part of the verification metadata for each of the documents transferred directly from the sending user to each receiving user such that the each receiving user can verify that each of the transferred documents is authentic by recomputing an uppermost hash tree value from the respective digital signature of the transferred document itself;

for each current transferred copy of any of the documents, submitting a verification request;

upon each verification request, updating a verification vector including verification metadata and, for each corresponding document, compiling and maintaining a verification chain that includes a representation of all verification vectors associated with all transferred copies of the document in a transfer path of all users from the original version to the current transferred copy of the respective document; and

verifying correctness of any of the documents by examining the respective verification chain and, upon detection of a verification failure, initiating a remedial action.

2. The method as in claim 1 , in which modification of the received version of a document is chosen from the group: addition or deletion of a portion of the received version, splitting the received version into two or more separate documents, and merging the received version of the document with the received version of at least one other document.

3. The method of claim 2 , further comprising:

designating a data perimeter within which an administrative system supervises document flow; and

for any copy of any of the documents passing from within the perimeter to a user located outside the perimeter, altering data included in the corresponding digital input record such that verification will fail for the out-of-perimeter copy and any derivative thereof.

4. The method of claim 1 , in which the verification chain for each copy of each document includes an indication of whether each copy of the respective document was successfully verified, as a function of its signature, for all copies in its respective transfer path.

5. The method of claim 1 , in which the remedial action is that no further copy of the corresponding document is transferred.

6. The method of claim 5 , in which the remedial action is taken in an intermediate system between an originating device and a user device.

7. The method of claim 1 , further comprising, within an administrative system, compiling and storing a verification tree for each document, said verification tree comprising the verification chains for all transfer paths of each document.

8. The method of claim 1 , further comprising:

receiving the verification requests in an administrative system from any of the plurality of users; and

requiring authorization by the administrative system before any user is allowed to process copy of any document, said authorization including performing an updated verification and extending the corresponding document's verification chain with metadata of the updated verification.

9. The method of claim 8 , further comprising authorizing at least one of the users to modify a copy of any of the documents, re-signing any modified copy to obtain an updated signature, and updating the corresponding verification metadata to indicate modification of downstream copies of the modified document and to include the updated signature, said authorized, modified copy thereby becoming the reference version of all subsequent copies of the document derived from the authorized, modified copy.

10. The method of claim 1 , in which the original version of each document is its corresponding reference version.

11. The method of claim 1 , further comprising:

designating a data perimeter within which an administrative system supervises document flow; and

for any copy of any of the documents passing from a location outside the perimeter to a location within the perimeter, re-verifying the copy and taking the remedial action upon re-verification failure.

12. The method of claim 1 , further comprising:

designating a data perimeter within which an administrative system supervises document flow; and

for any copy of any of the documents passing from within the perimeter to a user located outside the perimeter, marking the corresponding verification metadata accordingly.

13. The method of claim 1 , further comprising generating a graphical display illustrating the transfer history and verification chain of at least one of the documents.

14. The method of claim 1 , further comprising:

issuing a command to a data store to delete the original version of the respective document; and

including in the verification chain for the respective document a signed indication of the command.

15. The method of claim 14 , further comprising including in the verification chain for the respective document a signed indication of deletion confirmation from the data store.

16. The method of claim 14 , further comprising including in the verification chain for the respective document a signed indication of local deletion.

17. The method of claim 1 , further comprising:

issuing a command to delete a selected copy of the document;

deleting at least a substantial portion of the selected document and entering in the verification chain an indication of deletion.