Document orchestration system for processing digital consent information

A method of improving the performance of a computer system, the method comprising the steps of:

• reactivating dormant system resources required to execute, on a remote computer system, a plurality of default security applications, the resources comprising electricity, processing power, and auxiliary systems;
• transferring a first profile from a device to the remote computer system, the first profile containing a device identity, a device user, an account record, and a transaction scheme associated with the account record;
• activating a consent scheme on the remote computer system, the consent scheme comprising the steps of:
• identifying information which must be disclosed to the device user prior to enacting the transaction scheme using the device identity, determining if the information has previously been provided to the device user, and if not provided, transmitting the information to the device and storing a record of the transmission in the remote computer system;
• identifying an interaction which must occur with the device user prior to enacting the transaction scheme using the device identity, determining if the interaction has previously occurred with the device user, and if it has not occurred, initiating the interaction via the device and storing a record of the interaction in the remote computer system;
• identifying a contract which must be executed via the device user prior to enacting the transaction scheme using the device identity, determining if the contract has been executed previously via the device user, and if not executed, supplying a version of the contract to the device, executing the contract via the device, and storing a record of the executed contract in the remote computer system;
• and
• indicating that consent is present when records of all the required information, interaction, and contract, have been stored;
• activating a security scheme on the remote computer system, the security scheme comprising:
• when a pre-established security token is detected in the remote computer system, generating a security token by duplicating the pre-established security token;
• when a pre-established security token is not detected in the remote computer system:
• generating a list of security applications associated with the first profile,
• deactivating running system resources of security applications absent from the list,
• activating dormant system resources of non-running security applications present on the list,
• executing the active security applications and thereby assigning a validity weight to the first profile, and
• generating a security token that is proportional to the validity weight of the first profile;
• transferring a second profile to the remote computer system, the second profile containing a replacement security token for the generated security token;
• converting the replacement token into the pre-established security token when consent is present and when the generated security token meets a first predetermined criterion;
• and
• when, over the course of a 30-day period, a default security application is deactivated by the security scheme more times than a non-default security application is activated by the security scheme, replacing the default security application with the non-default security application in the plurality of default security applications.