Abstract: A financial institution computing system includes an account database with a plurality of transaction parameters with respect to a financial account of a customer, a receptiveness metrics circuit structured to extract the plurality of transaction parameters from the account database, the transaction parameters including at least one financial transaction record, and indicative of a mode of the customer, and determine one or more receptiveness metrics attributed to the customer based on the mode of the customer, the one or more receptiveness metrics indicating likelihoods of the customer converting an interaction from the financial institution, wherein the interaction includes an avatar that is an aged version of the customer, and an interaction generation circuit structured to transmit the interaction to the customer at an optimal time based on the one or more receptiveness metrics.

Abstract: Systems, methods, and apparatus related to a multi-level error correction architecture used for copying data in memory devices. In one approach, user data is stored in the first partition of a non-volatile memory. First error correction code data is generated for the user data and stored with the user data in the first partition. Second error correction code data is generated for the user data and stored outside the first partition. The second error correction code data provides an increased error correcting capability that is compatible with the error correction algorithm used with the first error correction code data. A copyback operation is used to copy the user data and the first error correction code, but not the second error correction code, to a second partition of the non-volatile memory. The second error correction code can be selectively used if there is a need to recover portions of the user data stored in the first partition.

Abstract: A method includes determining, by a processing device, a value of a memory endurance state metric associated with a segment of a memory device in a memory sub-system; determining a target value of a code rate based on the value of the memory endurance state metric, and adjusting the code rate of the memory device according to the target value, wherein the code rate reflects a ratio of a number of memory units designated for storing host-originated data to a total number of memory units designated for storing the host-originated data and error correction metadata.

Abstract: The present disclosure relates generally to systems and methods of managing normally independent or unassociated business artifacts using an integrated business artifact management system (IBAMS) to deliver a cohesive, linked, and traceable network of related and integrated artifacts that supports improved business knowledge and impact analysis. A disclosed IBAMS includes a collection of integrated business artifacts stored in a memory of the IBAMS and a plurality of links, each associated with a respective data island of a plurality of data islands. Each link includes a set of instructions that, when executed by a processor of the IBAMS, cause the processor to: receive business artifacts from the respective data island; generate representations that are abstractions of the business artifacts received from the respective data island; and store and integrate the representations in the collection of integrated business artifacts.

Abstract: A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

Abstract: A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

Abstract: A method may include: retrieving a particular blank universal form based on a universal form template, the particular blank universal form having a universal form identifier, and the particular blank universal form created by a universal form creator; providing the particular blank universal form to a universal form filler; receiving a verified form from a universal form filler, the verified form corresponding to the particular blank universal form; and providing the verified form to the universal form creator.

Abstract: A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

Abstract: A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

Abstract: A method may include: maintaining one or more attributes of a first user; maintaining a risk profile scheme configured by the first user, the risk profile scheme comprising a passive permission table indicating whether a second user has permission to the one or more attributes; allowing the first user to grant dynamic permissions to the second user to access the one or more attributes in accordance with the risk profile scheme; allowing the first user to perform content blobulation of the one or more attributes; and allowing the first user to perform content reblobulation of the one or more attributes in accordance with the risk profile scheme.

Abstract: Granting permissions for attributes in a distributed data store involves implementing a federated control system. The system can include dynamic permissions granted to content blobs. Acknowledgment of dynamic permissions facilitates identification of users that receive content to enable restoring data on a machine following data loss. Acceptance of dynamic permissions can further facilitate automatic updates to data, or providing content blobs in response to changes in user attributes.

Abstract: Creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The technique enables a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.

Abstract: The present invention is a modular stock system for rifles. The system replaces the rifle's buffer tube with a modified one containing a mount for a constant cheek weld and a rail track for adjustment. A stock module then mounts on the replacement buffer tube. The stock module is interchangeable depending on the user's needs. Various configurations of the stock module are discussed, including adjustable stocks, fixed stocks, and specialized stocks. The stock module may be made even further modular by the addition of rail system.

Abstract: Granting permissions for attributes in a distributed data store involves implementing a federated control system. The system can include dynamic permissions granted to content blobs. Acknowledgment of dynamic permissions facilitates identification of users that receive content to enable restoring data on a machine following data loss. Acceptance of dynamic permissions can further facilitate automatic updates to data, or providing content blobs in response to changes in user attributes.

Abstract: Creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The technique enables a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.

Abstract: A computer system and methods for creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The system and methods allow a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.

Abstract: A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

Abstract: A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

Abstract: A technique for distributed management of attributes includes propagating attributes based upon attribute-granularity permissions. An example of a system according to the technique may include a server, coupled to a first client and a second client, that includes a module that receives attribute data from the first client; a permissions database where first permissions associated with the first client are set at the individual attribute level for the second client; an engine for updating the permissions database and for validating the first permissions for the second client; and an engine for distributing first client updates based on validated permissions to destinations associated with the one or more second destination stores.

Abstract: A computer system and methods for creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The system and methods allow a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.