Self-tracking documents

Abstract

The disclosed systems and methods pertain to the field of electronic document management, addressing the technical problem of maintaining control and security over distributed digital documents. The approach introduces a method for creating self-tracking documents that autonomously monitor and record events associated with their lifecycle, access, and interactions. This method involves identifying events, storing event information, receiving access requests, and providing event information, all executed by the document itself. The method enables document owners to maintain control, manage access permissions dynamically, and monitor interactions in real-time, enhancing security and compliance.

Description

SELF-TRACKING DOCUMENTSPRIORITY CLAIMS TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No.63 / 661,534 filed June 18, 2024, U.S. Provisional Patent Application 63 / 668,068 filed July 5,2024, U.S. Provisional Patent Application 63 / 674,793 filed July 23, 2024, U.S. ProvisionalPatent Application 63 / 680,061 filed August 6, 202.4, U.S. Provisional Patent Application63 / 685,234 filed August 20, 2024, U.S. Provisional Patent Application 63 / 693,173 filedSeptember 10, 2024, U.S. Provisional Patent Application 63 / 707,992, filed October 16, 2024,U.S. Provisional Patent Application 63,713,200, filed October 29, 2024, U.S. Provisional PatentApplication 63 / 714,009 filed October 30, 2024, U.S. Provisional Patent Application63 / 723,471 filed November 21, 2024, U.S. Provisional Patent Application 63 / 736,568, filedDecember 19, 2024, U.S. Provisional Patent Application 63 / 738,639, filed December 24, 2024,U.S. Provisional Patent Application 63 / 774,949, filed March 20, 2025, U.S. Provisional PatentApplication 63 / 794,007, filed 24 April, 2025, U.S. Provisional Patent Application 63 / 794,564, filed 25 April, 2025, and U.S. Provisional Patent Application 63 / 800,869, filed 6 May, 2025, and U.S. Provisional Patent Application 63 / 822,629, filed 12 June, 2025, which are each incorporated herein in their entirety by these references which are each incorporated herein in their entirety by these references.BACKGROUND

[0002] In the modern digital era, electronic documents are ubiquitous, serving as essential tools for communication and information exchange across various sectors. These documents, often stored in formats such as PDF, Word, or Excel, are typically shared and accessed through local, shared, or cloud storage systems. However, once these documentsare distributed, the original owner or creator frequently loses control over them, leading to potential security risks and unauthorized dissemination. This ioss of controi is particularly concerning for organizations that handle sensitive information, as they rely heavily on the goodwill of recipients and the legal system to ensure compliance with confidentiality agreements and data protection policies.

[0003] Despite the availability of document management systems and access control mechanisms, these solutions often fall short in providing comprehensive control and security. They typically offer pseudo-control through policies and procedures, which can be easily circumvented. Moreover, the proliferation of electronic documents across various platforms and devices exacerbates the challenge of maintaining a single, true version of a document, leading to issues with version control and data integrity. There is a pressing need for a more robust system that enables document owners to maintain control over their documents, ensuring secure access and interaction while preventing unauthorized distribution and modification.SUMMARY

[0004] As will be described in greater detail below, the present disclosure describes systems and methods for self-tracking documents. In some aspects, the techniques described herein relate to a method including: identifying, by a self-tracking document, an event associated with the self-tracking document; storing, by the self-tracking document, information about the event with the self-tracking document; receiving, at the self-tracking document, a request to access the information about the event; and providing, by the selftracking document and in response to the request, the information about the self-tracking document in response to the request.

[0005] In some aspects, the techniques described herein relate to a system including: one or more physical processors; and physical memory including computer- executable instructions that, when executed by the one or more physical processors, cause at least one of the one or more physical processors to: identify, by a self-tracking document, an event associated with the self-tracking document; store, by the self-tracking document, information about the event with the self-tracking document; receive, at the self-tracking document, a request to access the information about the event; and provide, by the self- tracking document and in response to the request, the information about the self-tracking document in response to the request.

[0006] In some aspects, the techniques described herein relate to a non-transitory computer-readable medium including computer-executable instructions that, when executed by at least one of one or more physical processors of a computing device, cause the computing device to: identify, by a self-tracking document, an event associated with the self- tracking document; store, by the self-tracking document, information about the event with the self-tracking document; receive, at the self-tracking document, a request to access the information about the event; and provide, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request.10007] These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The accompanying drawings illustrate 3 number of exemplary embodiments and are a part of the specification. Together with the following description, these drawings demonstrate and explain various principles of the present disciosure.

[0009] FIG. 1 is a system diagram iilustrating the architecture for self-tracking documents.

[0010] FIG. 2 illustrates a system diagram of a networked document management system in which aspects of this disclosure are implemented.

[0011] FIG. 3 illustrates a flow chart diagram of a method for a document performing self-tracking and self-reporting.

[0012] Throughout the drawings, identical reference characters and descriptions indicate similar, but not necessarily identical, elements. While the exemplary embodiments described herein are susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the exemplary embodiments described herein are not intended to be limited to the particular forms disclosed. Rather, the present disclosure covers all modifications, equivalents, and alternatives falling within the scope of the appended claims.DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

[0013] The concept of a document with embedded intelligence represents a unified approach to document management, where all relevant information about a document's lifecycle, interactions, and provenance is embedded directly within the document itself. This contrasts sharply with the traditional fragmented approach, where information about a document is scattered across multiple systems, such as email servers, cloud storageplatforms, and local databases. Fragmentation creates inefficiencies, as users must piece together disparate sources to understand a document's history or verify its authenticity.Adding embedded intelligence can eliminate this problem by consolidating all relevant data within the document, ensuring that it serves as a single, authoritative source of truth. This approach not only enhances security and transparency but also simplifies workflows by reducing reliance on external systems.

[0014] In the context of self-tracking documents, events are not merely recorded as metadata-- they are treated as verifiable facts that serve as the definitive source of truth.Each event, such as a document being accessed, modified, or shared, is accompanied by detailed information, including timestamps, user credentials, and geolocation data. This information can be used to independently verify the occurrence of the event, ensuring its authenticity and integrity. For example, if a document claims that it was signed by a specific user at a particular time, the embedded event data can be cross-referenced with external systems or cryptographic signatures to confirm its validity. By treating events as verifiable facts, self-tracking documents provide a robust framework for accountability and compliance, making them invaluable in industries where regulatory oversight is critical.

[0015] Self-tracking documents are designed to be the definitive record of all events associated with their lifecycle. Unlike traditional systems, where event data is stored externally in fragmented logs or databases, self-tracking documents embed this information directly within the document itself. This ensures that the document remains the single source of truth, eliminating the need to rely on external systems to reconstruct its history. For instance, in legal or compliance scenarios, the document can autonomously provide a complete audit trail, detailing every interaction, modification, and access attempt. Thiscapability not only enhances transparency but also reduces the risk of data tampering or loss, as the document itself becomes the authoritative record of its provenance.

[0016] Machine integration in the context of self-tracking documents ensures that all systems interacting with the document operate based on a single source of truth. Byembedding machine-readable data within the document, self-tracking documents enable seamless integration with external systems, such as Al tools, analytics platforms, and workflow management software. This eliminates discrepancies that often arise when different systems interpret the same document differently due to fragmented or inconsistent data. For example, a self-tracking document can provide standardized data to an Al system for analysis, ensuring that the insights generated are accurate and consistent. This unified approach to machine integration not only enhances operational efficiency but also ensures that all systems interacting with the document are aligned with its true state.

[0017] Self-tracking documents are capable of adapting to changing dimensions, both in terms of their content and their context. For instance, a marketing brochure may initially be distributed as a static document but later evolve to include interactive elements, such as embedded videos or real-time analytics dashboards. Similarly, the document's context may change based on its lifecycle—for example, a contract may initially serve as a draft but later transition into a legally binding agreement once signed. These changing dimensions are tracked and recorded within the document itself, ensuring that its history and current state are always accessible and verifiable. This adaptability makes self-tracking documents highly versatile, allowing them to meet the dynamic needs of modern digital environments.

[0018] Seif-tracking documents provide an unparalleled level of transparency and accountability, making them ideal for regulatory compliance. By autonomously recording every event associated with their lifecycle, these documents create a comprehensive audit trail that can be used to demonstrate adherence to regulatory requirements. For example, a compliance report can log all signatures, approvals, and reviews, providing regulators with a clear record of the document's journey. This proof of process not only simplifies audits but also reduces the risk of non-compliance, as all document-related activities are traceable and verifiable. In industries such as finance, healthcare, and manufacturing, where regulatory oversight is stringent, self-tracking documents offer a reliable solution for maintaining compliance.

[0019] Self-tracking documents can incorporate advanced access control mechanisms, such as paywalls with timing restrictions, to manage user interactions. For instance, a research paper may be made available behind a paywall, with access granted for a limited period after payment. The document itself tracks the timing of access, ensuring that users can only view the content within the permitted timeframe. Once the access period expires, the document autonomously revokes permissions, preventing unauthorized use. This capability not only enhances security but also provides document owners with granular control over how their content is accessed and monetized. By embedding these access control mechanisms directly within the document, self-tracking documents eliminate the need for external systems to enforce restrictions.

[0020] Self-tracking documents enable precise tracking of subcontractor interactions, including location-based access control. For example, a construction blueprint may be shared with a subcontractor for use at a specific job site. The document tracks thesubcontractor's location and ensures that access is granted only within the designated geographic area, if the subcontractor attempts to access the document outside the permitted location, the document autonomously revokes permissions, preventing unauthorized use.This iocation-based tracking capability is particularly valuable in industries where sensitive information must be protected, such as construction, defense, and healthcare. By embedding these controls within the document itself, self-tracking documents provide a robust framework for managing subcontractor interactions securely and efficiently.

[0021] Self-tracking documents extend their capabilities to hard copies by embedding unique identifiers, such as invisible machine-readable codes, during the printing process. These codes, which can include information about the document's origin, print timestamp, and user credentials, ensure that even physical copies remain traceable within the system of record. For example, a printed contract may include invisible codes that identify it as copy number three, printed by a specific user at a specific time. If the hard copy is later scanned or photographed, the embedded codes can be used to link it back to the original digital document, ensuring continuity and authenticity. This capability bridges the gap between digital and physical document management, providing a seamless way to track hard copies within the broader system of record.

[0022] As noted, self-tracking documents are a transformative approach to addressing the myriad challenges associated with traditional document management systems. In an era where digital information exchange is ubiquitous, the ability to maintain control and security over distributed documents is paramount. Self-tracking documents offer a solution by autonomously monitoring and recording events throughout their lifecycle, access, and interactions. This innovative capability empowers document owners with thetools necessary to maintain a comprehensive audit trail, providing detailed insights into who accessed the document, when it was accessed, and what actions were taken.

[0023] The functionality of seif-tracking documents may be particularly important in industries where data integrity and confidentiality are of utmost importance. Regulatory- requirements and organizational policies demand stringent compliance measures, and self- tracking documents facilitate this by ensuring that all document-related activities are transparent and traceable. By capturing and preserving information about each event, these documents provide a reliable record that supports legal verification and accountability, enhancing their utility in secure and dynamic management environments.

[0024] Moreover, the ability to autonomously manage document interactions reduces the risk of unauthorized access and data breaches. Self-tracking documents can employ advanced security measures, such as role-based access control, encryption, and multi-factor authentication, to ensure that only authorized users can view or modify the document. This dynamic management of access permissions not only safeguards sensitive information but also streamlines document management processes, allowing organizations to focus on strategic decision-making and performance evaluation.

[0025] Self-tracking documents can offer a framework for modern document management challenges, transforming traditional documents into active entities capable of self-monitoring and self-regulation. As organizations continue to navigate the complexities of digital information exchange, the adoption of self-tracking documents promises to streamline processes, safeguard sensitive data, and empower users with unprecedented control over their digital assets. This transformative approach not only enhances document security andmanagement but also supports compliance with regulatory requirements, ensuring that all document-related activities are transparent, traceable, and verifiable.

[0026] FIG. 1 shows a System 100, which is an architecture designed to manage electronic documents as smart digital objects. The System 100 includes code 102, which includes Identification Instructions 104, Storage Instructions 106, CommunicationInstructions 108, and Timeline Instructions 110. Each interface is designed to perform specific tasks that contribute to the ability of a Document 140 to track itself. The IdentificationInstructions 104 are responsible for recognizing and categorizing documents, ensuring that each document is distinctly identified within the system. The Storage Instructions 106 manage the storage of data, allowing for efficient retrieval and updating of document information.The Communication Instructions 108 facilitate the exchange of data between the system and external entities, ensuring that documents can be shared and accessed securely. The TimelineInstructions 110 provide functionality for tracking document-related activities, enabling users to view the history and interactions associated with each document.

[0027] The Identification Instructions 104 are responsible for identifying events associated with documents. These instructions interact with the Data Storage 120 to store identification information and with the Communication Instructions 108 to facilitate event tracking. The Storage Instructions 106 manage the storage and retrieval of information about events and other data associated with documents. The Storage Instructions 106 interact with the Data Storage 120, where Data 122 is stored, to ensure that document information is securely maintained and easily accessible. This interface also interacts with the TimelineInstructions 110 to store information about document-related activities, providing a comprehensive audit trail for each document.

[0028] The Communication instructions 108 ensure that documents can be shared and accessed securely, supporting the document's ability to manage remote access and interactions. The Communication Instructions 108 receives requests to access information about events associated with documents and responds to those requests. The TimelineInstructions 110 enables users to view a timeiine associated with document, providing a history of all events related to that document. The Timeline Instructions 110 work with theStorage Instructions 106 to store information about document interactions and with theCommunication Instructions 108 to share timeline data with authorized users.

[0029] The Data Storage 120 within the System 100 is responsible for maintaining the Data 122 associated with documents that determine their own characteristics. This component interacts with the Storage Instructions 106 to store and retrieve document information, ensuring that data is securely maintained and easily accessible. The Data Storage120 also supports the document's ability to manage versions and interactions.

[0030] The Data 122 stored within the Data Storage 120 represents the primary information associated with self-governing documents. This data includes document content, metadata, version history, and interaction records, providing a history of the document's lifecycle. The Data 122 is organized and maintained by the Storage Instructions 106. ensuring secure storage and easy accessibility. The Physical Processor 130 executes code of the Code102 to process data and manage document interactions and may be any suitable type or form of processor including one or more central processing units, one or more programmable processing units, one or more custom processing units, etc.

[0031] In some examples, the data of a self-determinative document can include two distinct components: content 124 and metadata 126, each serving a unique purpose inthe document's functionality and lifecycle. Content 124 refers to the core information of the document, such as text, images, tables, or other embedded elements that constitute the primary substance of the document. This content is immutable, meaning it cannot be altered once the document has been finalized or authenticated. The immutability of content 124 ensures the integrity and trustworthiness of the document, making it suitable for applications where the original state of the document must be preserved, such as legal agreements, financial reports, or medical records.

[0032] On the other hand, metadata 126 represents supplementary information about the document, such as timestamps, user interactions, access logs, version history, or contextual details. Unlike the immutable content, metadata 126 is mutable and can be updated or modified as the document evolves. For example, metadata can record the identity of users who accessed the document, the time and date of interactions, or the addition of comments or annotations. This mutability allows the document to dynamically track its lifecycle and provide real-time insights into its usage and provenance. By separating immutable content from mutable metadata, the document achieves a balance between preserving its core integrity and enabling flexibility for operational and contextual updates.This dual structure ensures that the document remains both reliable and adaptable, meeting the needs of secure and dynamic digital environments.

[0033] Metadata plays a central role in the functionality and transformative potential of smart documents (i.e., documents that are digital infrastructure). It provides a structured, machine-readable layer of information that goes beyond the visual representation of a document, enabling advanced computational interactions, dynamic workflows, and granular access control. Metadata can be categorized into several distinct types, each servinga unique purpose in enhancing the utility and intelligence of a document. These categories include process metadata, semantic metadata, and content-related metadata, among others.Below is a detailed explanation of these metadata types, with examples drawn from the discussion.

[0034] Process metadata captures the history and lifecycle of a document, recording every action, interaction, and workflow the document has undergone. This type of metadata serves as an audit trail, providing a comprehensive record of the document's journey and the processes it has been part of. For example, process metadata might include timestamps for when the document was created, edited, shared, or signed. It could also log the identities of users who accessed the document, the nature of their interactions (e.g., viewing, commenting, or editing), and any changes made to the document's content or metadata.

[0035] Semantic metadata describes the intrinsic characteristics of a document, answering the question of "what the document is" rather than "what the document contains."This type of metadata includes information about the document's type, ownership, and categorical classification. For example, semantic metadata might indicate that a document is an NDA (Non-Disclosure Agreement), a marketing presentation, or a financial report, it might also specify the document's owner, such as the individual or organization responsible for its creation and management.

[0036] Semantic metadata is particularly useful for organizing and categorizing documents within a system. For instance, in an enterprise setting, semantic metadata can be used to group all contracts under a "Legal Documents" category, all invoices under a "FinanceDocuments" category, and all marketing materials under a "Marketing Documents" category.This categorization enables efficient search and retrieval, as users can query the system to find all documents of a specific type or category.

[0037] Content-related metadata provides a structured representation of the document's content, breaking it down into machine-readable elements such as paragraphs, headings, tables, and images. This type of metadata enables advanced computational interactions with the document, such as semantic analysis, automated workflows, and dynamic rendering.

[0038] The computing devices and systems described and / or illustrated herein broadly represent any type or form of computing device or system capable of executing computer-readable instructions, such as those contained within the interfaces described herein. In their most basic configuration, these computing device(s) may each include at least one memory device and at least one physical processor.

[0039] FIG. 2 shows a system diagram illustrating a networked document management system 200. The system 200 comprises a Server 206, a Document 210, aNetwork 204, and a Computing Device 202, which includes a Physical Processor 220, Memory240, and an Interface 260. The Server 206 is connected to the Computing Device 202 through the Network 204, facilitating communication and data exchange between these components.The Server 206 is responsible for hosting the Document 210, which is a self-tracking document capable of autonomously monitoring and recording events associated with the document's lifecycle. The Document 210 is stored on the Server 206, allowing the document to be accessed and managed remotely. The Server 206 interacts with the Network 204 to enable the transmission of the Document 210 to the Computing Device 202, ensuring secure and efficient data exchange.

[0040] The Network 204 serves as the communication medium between theServer 206 and the Computing Device 202. This network facilitates the transfer of data, including the Document 210, between these components, ensuring that the document can be accessed and managed from different locations. The Network 204 supports various communication protocols to maintain secure and reliable connections. The Computing Device202 is equipped with a Physical Processor 220, Memory 240, and an Interface 260, which collectively enable the device to interact with Document 210. The Physical Processor 220 executes computer-readable instructions to process data and manage interactions with theDocument 210. The Memory 240 within the Computing Device 202 stores data and instructions necessary for managing the Document 210.

[0041] FIG. 3 illustrates a flow chart diagram of a method for creating and managing a self-tracking document with embedded intelligence that can make decisions independently. This figure outlines the sequential steps involved in the lifecycle of a selftracking document, highlighting its ability to autonomously monitor, record, and provide information about events associated with the document.

[0042] Step 310 in FIG. 3 involves the self-tracking document identifying an event associated with itself. For example, the document can identify access attempts by logging when a user tries to access it, whether successfully or unsuccessfully, including details such as the user's credentials, the time of access, and the location from which the access was attempted. It can also detect modifications to its content, such as edits, deletions, or additions, and log the nature of the modification, the user who made the change, and the timestamp of the modification. Additionally, the document can identify interactions with other documents or systems, such as data imports, exports, or integrations with externalapplications, recording the details of the interaction, including the source and destination of the data exchange.

[0043] The types of events that can be identified by the document include version creation, allowing it to track version history and maintain data integrity, and compliance checks, ensuring that it meets regulatory requirements. The document can also detect potential security breaches, such as unauthorized access attempts or suspicious activities, enabling it to alert users and take preventive measures. Furthermore, it can track user activity. such as viewing, printing, or sharing, providing insights into how the document is being utilized. By autonomously identifying these events, the self-tracking document enhances its utility in secure and dynamic document management environments, providing a comprehensive audit trail and ensuring compliance with organizational policies.

[0044] In the context of self-tracking documents, an "event” refers to any occurrence or action related to the document's lifecycle, access, or interactions that can be autonomously identified and recorded by the document’s embedded intelligence. Recorded events leave an audit trail, ensuring compliance, and enhancing security by providing insights into the document's usage and modifications. Examples of events that a self-tracking document can identify include user access attempts, successful logins, and failed login attempts. A self-tracking document can also track when it is opened or closed, as well as any content modifications, deletions, or additions. Version control events such as document version creation, deletion, and updates can also be recorded. Additionally, the document can log when it is shared with another user, printed, downloaded, uploaded, or viewed.

[0045] Other events include copying, moving to a different location, renaming, archiving, and restoring from an archive. Security-related events such as encryption,decryption, access permission changes, and user role changes may also be tracked.Compliance audits, security breach detections, and data imports or exports to and from other documents can be recorded as well. The document can also identify interactions with external applications, notifications sent, comments added, and metadata changes. Furthermore, it can log events such as digital signatures applied, workflow steps completed, deadlines set or met, reminders sent, and document expiration. Other examples include document retention policy updates, user feedback received, document flagged for review, collaboration sessions initiated, and document access through specific devices or locations. Tracking these events help a self-tracking document maintain a detailed record of its interactions and changes, providing valuable information for security, compliance, and management purposes.

[0046] Step 320 in FIG. 3 involves storing information about the event within the self-tracking document. This step enables maintaining a comprehensive record of all interactions and occurrences related to the document. By autonomously logging details of each identified event, the self-tracking document ensures that a complete audit trail is preserved, which can be invaluable for compliance, security, and data integrity purposes.

[0047] The process of storing event information involves capturing various details associated with the event, such as the type of event, the timestamp, the user involved, and any changes made to the document. This information is typically stored as metadata within the document, allowing for efficient retrieval and analysis. The ability to store event information securely and accurately enhances the document's utility in dynamic and secure document management environments, providing insights into its lifecycle and interactions.

[0048] By maintaining a detailed record of events, the self-tracking document supports organizational policies and regulatory requirements, ensuring that all document-related activities are transparent and traceable. This capability not only aids in compliance but also strengthens security measures by providing a reliable record of access and modifications, helping to prevent unauthorized actions and data breaches.

[0049] Information about an event can be stored with a document in various ways.One approach is to store event details such as the type of event, timestamp, user involved, and changes made as metadata within the document, allowing for efficient retrieval and analysis without altering the document's main content. Another method is maintaining a separate audit log within the document, which records a chronological list of events, providing a comprehensive history of interactions and modifications useful for compliance and security audits. Events can also be documented as embedded annotations within the document, offering context-specific information directly alongside the relevant content, which is particularly useful for tracking changes and comments. Additionally, certain events can trigger the creation of a new version of the document, with the event details stored in the version history, helping maintain data integrity and allowing users to revert to previous versions if needed.

[0050] For sensitive events, information can be stored in an encrypted format within the document, ensuring that only authorized users can access the details. Alternatively, events can be recorded as entries on a blockchain, providing a tamper-proof and transparent record of all document-related activities, thereby enhancing security and trustworthiness.Specific tags can be added to the document to categorize and identify events, facilitating quick searches and filtering based on type or importance. Event information can also be stored in an external database linked to the document, allowing for extensive data analysis and reporting while keeping the document lightweight. In some aspects, specialized in-documentapplications can capture and store event information, providing interactive and dynamic ways to view and manage events. In additional aspects, visual overlays can be used to display event information directly on the document's interface, offering an intuitive way to understand the document’s history and interactions without navigating away from the main content.

[0051] When storing information about an event within a document, various types of data can be captured to provide a comprehensive understanding of the event's context and impact. The specific category or nature of the event, such as access, modification, or sharing, is identified as the event type. The exact date and time when the event occurred is recorded as a timestamp, providing a chronological reference. Information about the user involved in the event, including username or user ID, is stored alongside their role or permissions at the time of the event, indicating their level of access. The geographical location from which the event was initiated, if applicable, can be noted, along with details about the device used to perform the event, such as device type or IP address. The document version at the time of the event can be tracked.

[0052] In some aspects, a description of the specific action performed during the event, such as editing or viewing, is documented, along with the state of the document before and after the event, providing context for changes. Any comments or notes added by the user during the event offer additional insights, while information about whether the event involved an approval process and its outcome can be recorded as approval status. The security measures in place during the event, such as encryption or authentication, can be recorded, along with details about any compliance checks performed as part of the event. References to other documents involved in or affected by the event can be recorded, as well as information about any data transferred to or from the document during the event. Detailsabout any notifications triggered by the event, including recipients, can be recorded, along with the nature of interactions with other systems or applications during the event. Any error messages generated during the event are recorded, indicating issues encountered, and steps taken to resolve any issues or complete tasks associated with the event are noted as resolution actions. These types of information provide a detailed record of each event, enhancing the document's audit trail and supporting security, compliance, and management efforts.

[0053] Step 330 in FIG. 3 involves the self-tracking document receiving a request to access the information about the event. This step demonstrates the document's capability to respond to inquiries regarding its history and interactions. When a request is made, the document's embedded intelligence processes the request to determine the appropriate information to provide, ensuring that only authorized users can access the event details. This step helps users retrieve specific information about past events, supporting transparency and accountability in document management. Step .340 involves providing the information about the self-tracking document in response to the request. Once the request is validated, the document autonomously retrieves and provides the relevant event information to the user.This step ensures that users can access a comprehensive audit trail of the document's lifecycle and interactions. By providing detailed insights into past events, the document supports informed decision-making and enhances its utility in dynamic document management environments.

[0054] Steps 330 and 340 can be performed in various contexts. For instance, in legal compliance audits, auditors may request access to the document's event history to verify compliance with regulatory requirements, and steps .3.30 and .340 ensure that auditors canaccess detailed records of document interactions, modifications, and access attempts. In security investigations, security personnel may request information about unauthorized access attempts or suspicious activities, and the document can provide a detailed log of such events, aiding in the investigation and resolution of security incidents. Project managers may request information about document version history to track changes and ensure data integrity, with the document providing insights into when new versions were created, who made modifications, and what changes were implemented. In an organizational setting, administrators may request access to user activity logs to monitor document usage and ensure compliance with internal policies, and the document can provide records of who accessed the document, when it was accessed, and what actions were taken. Lastly, in collaborative environments, team members may request information about document interactions to track the progress of a project, and the document can provide details about who contributed to the document, what changes were made, and how the document was shared among team members. These contexts demonstrate the versatility and importance of steps 330 and 340 in managing and utilizing self-tracking documents effectively.

[0055] In some aspects, the methods and systems described herein involve storing the information about an event as metadata of the self-tracking document, as noted above.By utilizing metadata, the document can maintain a structured record of events, supporting comprehensive audit trails and enhancing the document's utility in secure and dynamic management environments. Metadata generally refers to data that provides information about other data, essentially serving as a descriptive framework that helps organize, identify, and manage the primary data. In the context of self-tracking documents, metadata is used to store details about events associated with the document, such as access attempts,modifications, and interactions. This approach ensures that event details are efficiently organized and accessible within the document, allowing for streamlined retrieval and analysis. By utilizing metadata, the document can maintain a structured record of events, supporting comprehensive audit trails and enhancing the document's utility in secure and dynamic management environments.

[0056] In some aspects, the methods and systems described herein involve protecting the information about the event from ever being modified. This approach ensures that the event details remain immutable, preserving the integrity and authenticity of the document's audit trail. By safeguarding the information from alterations, the document can maintain a reliable record of all interactions and occurrences, which is crucial for compliance, security, and data integrity purposes. This method of protecting event information can support organizational policies and regulatory requirements, ensuring that all document- related activities are transparent and traceable, and preventing unauthorized changes that could compromise the document's reliability.

[0057] A self-tracking document can ensure that its provenance or history remains immutable through any suitable mechanism designed to preserve the integrity and authenticity of its audit trail. One approach is using a distributed ledger, where event information is recorded on a blockchain, making each entry immutable and tamper-proof due to its decentralized and cryptographic nature. Digital signatures provide another layer of security by cryptographically signing each event, ensuring that any attempt to modify the event details would invalidate the signature, thus verifying the authenticity of the document's history. Maintaining a detailed audit trail with precise timestamps provides a chronological record of all events, making it difficult to alter past events without leaving a trace. Strict accesscontrols and permissions ensure that only authorized users can view or append to the document's history, reducing the risk of unauthorized modifications, immutable logs, designed to be append-only, can record every interaction and change, preventing alterations to existing entries. Regular backups and redundant storage of event information can help preserve the document's history, allowing the original data to be restored in case of an attempted alteration. Version control systems track changes over time and maintain a history of all versions, enabling the restoration of previous versions if unauthorized changes are detected. Finally, encrypting event information ensures that even if unauthorized access occurs, the data remains secure and unreadable without the appropriate decryption keys.These are examples of mechanisms that can ensure that a self-tracking document's provenance and history remain immutable, supporting compliance, security, and data integrity requirements. Mention hash functions? The document will have the same hash if it has not been modified.

[0058] In some aspects, the methods and systems disclosed herein involve identifying a legal event associated with a self-tracking document. By capturing and preserving information about legal events, the document provides a reliable audit trail that can be used for legal verification and accountability purposes. The following examples of identifying and storing information about legal events associated with a self-tracking document include various scenarios, and aspects of this disclosure are not limited to these examples.

[0059] In one example, when a contract is signed, the document can identify this as a legal event and store details such as the parties involved, the date of execution, and any terms or conditions agreed upon. Similarly, the document can identify compliance audits orchecks as legal events, storing information about the audit process, findings, and any actions taken to address compliance issues. If the document is involved in legal proceedings, it can identify the receipt of litigation notices as legal events, capturing details such as the case number, parties involved, and the nature of the legal action. When amendments are made to legal documents, the self-tracking document can identify these changes as legal events, storing information about the modifications, the parties who approved them, and the date of amendment. Additionally, the document can identify filings related to intellectual property, such as patents or trademarks, as legal events, storing information about the filing date, jurisdiction, and the specific intellectual property rights involved.

[0060] The document can also track approvals required for legal compliance, such as environmental permits or business licenses, identifying these as legal events and storing relevant details. When disputes are resolved, the document can identify the resolution process as a legal event, capturing information about the settlement terms, parties involved, and the resolution date. Furthermore, the document can identify updates to organizational policies that have legal implications, storing information about the changes, the rationale behind them, and the date of implementation, it can also track consultations with legal advisors as legal events, storing information about the advice provided, the context of the consultation, and any resulting actions. Lastly, the document can identify training sessions related to legal compliance as legal events, capturing details about the training content, participants, and completion dates. These examples illustrate how a self-tracking document can effectively manage and store information about legal events, ensuring an audit trail that supports legal verification and accountability.

[0061] In some aspects, the methods and systems disclosed herein store information about compliance events. This approach ensures that the document maintains a detailed record of compliance-related activities, supporting adherence to regulatory- requirements and organizational policies. The following examples of identifying and storing information about compliance events associated with a self-tracking document include various scenarios, and aspects of this disclosure are not limited to these examples.

[0062] As an example, during a regulatory audit, the document can identify this as a compliance event and store details such as the audit date, the regulatory body involved, and the findings or recommendations made. Similarly, the document can track compliance training sessions as compliance events, capturing information about the training content, participants, and completion dates. If the document is subject to a compliance review, it can identify the review process as a compliance event, storing details about the reviewers, the scope of the review, and any corrective actions taken. When a compliance certification is obtained, the document can identify this as a compliance event, recording information about the certifying authority, the certification date, and the validity period.

[0063] Additionally, the document can track updates to compliance policies as compliance events, storing information about the changes, the rationale behind them, and the implementation date. The document can also identify compliance-related incidents, such as data breaches or violations, as compliance events, capturing details about the incident, the response actions taken, and any lessons learned. Furthermore, the document can track compliance reporting activities, such as the submission of reports to regulatory bodies, as compliance events, storing information about the report content, submission date, and any feedback received, it can also identify compliance audits conducted by internal teams ascompliance events, capturing details about the audit process, findings, and any follow-up actions required. Lastly, the document can track compliance-related communications, such as notifications from regulatory bodies, as compliance events, storing information about the communication content, sender, and any required responses. These examples illustrate how a self-tracking document can effectively manage and store information about compliance events, ensuring a comprehensive audit trail that supports verification and accountability.

[0064] In some aspects, the methods and systems described herein can provide an audit trail of the self-tracking document. By offering a partial or comprehensive audit trail, the document facilitates transparency and accountability, allowing users to review past events and make informed decisions based on the document's history. The following are examples of providing audit trails, and aspects of this disclosure are not limited to these examples.

[0065] In a legal context, a lawyer may request an audit trail to verify the authenticity and integrity of a contract, reviewing all modifications, access attempts, and approvals associated with the document. In a compliance setting, an auditor might request the audit trail to ensure that a financial report adheres to regulatory standards, examining the document's version history, user interactions, and any compliance checks performed. In project management, a team leader could request the audit trail to track the progress of a project plan, identifying who made changes, when they were made, and how they impacted the project's timeline. In an organizational environment, an administrator can request the audit trail to monitor document usage and ensure adherence to internal policies, reviewing access logs, user activities, and any security incidents. In a collaborative setting, team members may request the audit trail to understand the contributions of differentcollaborators, viewing edits, comments, and document sharing activities. These examples illustrate how providing an audit trail of a self-tracking document supports transparency, accountability, and informed decision-making across various contexts.

[0066] In some aspects, the methods and systems disclosed here involve receiving a request to access information about a plurality of events associated with the event and providing, by a self-tracking document and in response to the request, a timeline of the plurality of events. This approach allows users to view a comprehensive timeline of multiple events related to the document, supporting transparency and informed decision-making. By providing a detailed timeline, the document enhances its utility in dynamic and secure management environments, ensuring that all document-related activities are traceable and verifiable.[0067j One aspect of using self-tracking documents, as opposed to traditionalPDFs, is the ability to review a timeline associated with the self-tracking document. As core functionality associated with a self-tracking document, a user can access the timeline by interacting with an interface element when viewing an electronic version of the document.Alternatively, a user can perform similar actions on their device, such as a mobile phone, when reviewing a physical copy of a self-tracking document. In this scenario, a user can have a hard copy document in their hands, scan it with their mobile phone, and then view, to the extent authorized by the document owner, a history of multiple events associated with that document. If the document owner does not authorize full access to the history, the user will be able to see as much of the timeline as they are permitted to view. This capability supports transparency and informed decision-making by providing a comprehensive timeline of events,enhancing the document's utility in dynamic and secure management environments, and ensuring that all document-related activities are traceable and verifiable.

[0068] For example, the owner of the self-tracking document can authorize individuals they work with, such as their supervisor, to access the complete timeline of events associated with the document since its creation, while enabling others who receive the document to view selected portions of the timeline or none at all. Consider a scenario involving a marketing brochure distributed in both electronic and hard copy form by a corporation selling a product. Suppose an associate in the marketing department, Lucy, creates the brochure, and it is approved for distribution by her supervisor, Patty. The company then provides the brochure electronically to Charlie, the Purchasing Manager of one of their distributors, and mails a hard copy to Linus, an end user who may decide to purchase the product from Charlie's company. Each of Lucy, Patty, Charlie, and Linus may have different permissions regarding the parts of the timeline they can review.

[0069] Lucy, as the document creator and owner, can access the entire timeline.This includes, for example, (i) information about when she created the original version of the brochure, (ii) details about who in the company reviewed the brochure after Lucy initially created it, along with any comments these reviewers provided, and a timeline showing when these comments were received and how. if at all, the brochure was modified in response to each comment, (ill) information about when Patty gave final approval for the brochure's distribution, (iv) details about the distribution process, and (v) information about which distributors, end customers, and other nodes along the way received the brochure, and any actions they took. For instance, the timeline that Lucy views can inform her that Charlie received the electronic brochure at 2 p.m. on October 24th, viewed portions of it thatafternoon, spent more time reviewing it the next day, with particular attention given to the figure on page 3, and placed an order later that afternoon. It can also show her that Linus, who was mailed a hard copy of the brochure, accessed the hard copy on November 1st, and the next day, via his mobile, checked to see if there were any other versions of the product.

[0070] In addition to these direct data points, Lucy may also be able to access tangential information through the timeline of the self-tracking document. For example, she could view other documents that were approved or not approved by Patty. She might also see other documents received by Charlie and the activities or interactions Charlie had with these documents. The timeline could reveal if Charlie forwarded this brochure to others, as well as any previous brochures he may have forwarded. Lucy could access contact information associated with the parties to whom Charlie forwarded this or other brochures. Additionally, she could see information regarding other products purchased by Linus, whether fromCharlie, one of Charlie's competitors, or directly from the company. All these activities can be rendered via the timeline on a calendar or other graphic display, providing insights into trends that enable Lucy to make informed decisions.

[0071] Patty, Lucy's supervisor, may have access to the same information as Lucy and / or may be provided with higher-level synopses that aggregate information regardingLucy's brochure with data on other brochures created by Lucy's colleagues. This could be enhanced by a color scheme using red, yellow, and green, allowing Patty to guide her subordinates on which actions to take, avoid, or approach with caution. As a distributor,Charlie will likely not have access to information related to the internal process of creating the brochure and will probably only see details about the parties to whom he forwarded thebrochure. This information may be valuable to Charlie as he decides on next steps regarding these parties and could also be useful to Lucy and Patty as they make similar decisions.

[0072] Finally, Linus may be able to access information regarding this particular self-tracking document as well as information about other documents he has received in the past. For this specific document, he can view details about other parties to whom he forwarded the document. Since he accessed the hard copy, he can now use his device to forward the underlying electronic document. He can see what actions, if any, these parties have taken with the document. Additionally, he can access information about other similar documents, whether related to the same product, similar products, or the company Lucy andPatty work for. He can view product reviews and see where he could acquire the product, including from Charlie's company, other companies, or directly from Lucy and Patty’s company. Thus, based on the parameters programmed into the system, each of Lucy, Patty,Charlie, and Linus will see a timeline that is tailored to their relationship with the document.The level of interaction they can have with the timeline will be similarly tailored.

[0073] The timeline can be updated by in-document applications, such as those discussed in the related applications. For example, the description above included information about who within the company reviewed and approved the distribution of the document. This is part of the review in-document application, which allows Lucy (or Patty) to select the entities within the company, or specific individuals, who need to review and approve the document before Lucy can distribute it. The timeline will reflect that a particular review process was selected, the distribution path within the company mandated by that review process, and the exact date and time the draft document was provided to each party in the review process, whether simultaneously if set as a parallel process, or in a specific orderif mandated as a serial process, or a tailored combination of both. It will also reflect any comments made by the reviewing parties and any actions or resolutions taken in response to those comments. Thus, there will be a complete audit trail available on the timeline relative to the review process.

[0074] Timelines in the context of self-tracking documents can be presented in various ways to enhance user understanding and interaction. A straightforward chronological view can display events in the order they occurred, providing a dear and linear representation of the document's history, which is useful for tracking the progression of changes and interactions over time. Interactive graphical interfaces allow users to dick on specific events to view detailed information, enhancing user engagement and providing easy access to event details. Events can be categorized and color-coded based on their type, such as access, modification, or compliance, helping users quickly identify and focus on specific types of events. Timelines can also incorporate heat maps to highlight periods of high activity or significant changes, aiding in the identification of trends and patterns in document interactions. Multiple timelines can be layered to show different aspects of the document’s history, such as user interactions, version changes, and compliance checks, with users able to toggle between layers to focus on specific details. Integration with calendar views allows users to see events in the context of other scheduled activities, helping correlate document events with external deadlines or meetings.

[0075] A summary view can provide an overview of key events, highlighting major changes or interactions, which is useful for quick reviews and decision-making. Timelines can be customized based on user roles, displaying different levels of detail according to the user's permissions, ensuring that sensitive information is only accessible to authorized individuals.Users can apply filters to the timeline to focus on specific types of events or time periods, allowing for tailored views that meet individual needs. Additionally, timelines can be optimized for mobiie devices, ensuring that users can access and interact with document histories on the go, enhancing accessibility and convenience. These examples illustrate the versatility of timelines in presenting document histories, supporting transparency, informed decision-making, and efficient document management.

[0076] In some examples, the methods and systems described herein involve a marketing event associated with the document. For instance, when a marketing campaign is launched, the document can identify this as a marketing event and store details such as the campaign's start date, target audience, and promotional materials used. Similarly, the document can track customer engagement metrics as marketing events, capturing information about click-through rates, conversion rates, and customer feedback. If the document is part of a product launch, it can identify the launch event as a marketing event, storing details about the launch date, participating stakeholders, and media coverage.

[0077] When a marketing survey is conducted, the document can identify this as a marketing event, recording information about the survey questions, responses, and anaiysis results. Additionally, the document can track social media interactions as marketing events, storing information about posts, shares, likes, and comments related to the marketing initiative. The document can also identify trade show participation as a marketing event, capturing details about the event location, booth setup, and attendee interactions.Furthermore, the document can track email marketing campaigns as marketing events, storing information about email content, open rates, and recipient engagement. It can also identify promotional offers or discounts as marketing events, capturing details about the offerterms, redemption rates, and customer demographics. Lastly, the document can track influencer collaborations as marketing events, storing information about the influencers involved, content created, and audience reach. These examples illustrate how a self-tracking document can effectively manage and store information about marketing events, ensuring a comprehensive audit trail that supports strategic planning and analysis.

[0078] In some aspects, the methods and systems disclosed herein involve providing, by the self-tracking document, a non-chronological representation of the plurality of events that is organized in response to a context of the request instead of being organized chronologically. For instance, in a legal setting, a lawyer can request a view of all events related to compliance checks and approvals, regardless of their chronological order, to assess the document's adherence to regulatory standards. The document can present these events grouped by compliance category, highlighting any discrepancies or approvals that require attention. In a project management context, a team leader may request a view of all modifications made by a specific team member across different versions of the document.The document can organize these events by user, providing insights into individual contributions and facilitating performance evaluations.

[0079] For marketing analysis, a manager can request a representation of events related to customer engagement metrics, such as click-through rates and feedback, organized by campaign rather than by date. This enables the manager to assess the effectiveness of different marketing strategies and make informed decisions. In an organizational setting, an administrator could request a view of all security-related events, such as access attempts and permission changes, organized by risk level. This helps prioritize security measures and address potential vulnerabilities. In a collaborative environment, team members can requesta representation of all comments and interactions related to specific sections of the document, organized by topic or relevance. This facilitates focused discussions and enhances collaborative efforts.

[0080] In some aspects, the methods and systems described herein involve providing at ieast one of: information about a lead associated with the document; an engagement metric associated with the document; an interaction receipt associated with the document; and a marketing test result associated with the document. For instance, when a sales team requests information about a lead associated with a marketing brochure, the document can provide details such as the lead's contact information, interest level, and previous interactions with the company. Similarly, the document can offer engagement metrics, such as the number of times the document was viewed, the duration of each view, and the specific sections that received the most attention. If a marketing manager requests an interaction receipt, the document can provide a record of all interactions, including who accessed the document, when it was accessed, and any actions taken, such as sharing or downloading. Additionally, the document can present marketing test results, such as the outcomes of A / B testing on different versions of the document, highlighting which version performed better in terms of engagement or conversion rates. These examples illustrate how a self-tracking document can effectively provide detailed insights into its impact and effectiveness, supporting strategic decision-making and performance evaluation in dynamic and competitive business environments.

[0081] A smart document is designed to ensure the integrity, authenticity, and traceability of its content and associated audit trail through the use of immutability, a globalmarker, and embedded intelligence. This innovative structure addresses longstanding challenges in document management, auditing, and compliance.

[0082] Immutable Content

[0083] The content of a smart document is immutable, meaning it cannot be altered once finalized. This immutability is achieved through cryptographic techniques, such as hashing and digital signatures. When the document is created, its content is hashed to produce a unique cryptographic fingerprint. This hash is stored alongside the document and serves as a reference for verifying the integrity of the content. Any attempt to modify the content would result in a mismatch between the original hash and the hash of the altered content, immediately signaling tampering. Additionally, the document may be digitally signed using the creator's private key, ensuring that the content is not only unchangeable but also verifiable as originating from the authorized source.

[0084] Immutable Audit Trail

[0085] The audit trail of a smart document is equally immutable. The audit trail records every interaction with the document, including access, modifications, approvals, signatures, and other events. Each event in the audit trail is cryptographically secured and timestamped, ensuring that the sequence of events is preserved and cannot be altered retroactively. For example, when a user accesses the document, the system generates a cryptographic record of the access event, including the user's identity, the time of access, and the nature of the interaction. These records are stored in a manner that prevents deletion or modification, ensuring the audit trail remains a reliable source of truth. The audit trail is also linked to the document's content, creating a unified record of both the document and its history.

[0086] Immutable Connection to a Permanent Global Marker

[0087] Both the immutable content and the immutable audit trail are connected to an immutable global marker, which serves as the unique and unchanging identifier for the document. The global marker can be implemented as a universally unique identifier (UUID) or a cryptographic address, such as a hash-based identifier. This marker is permanent and does not change throughout the lifecycle of the document, regardless of how or where the document is accessed. The global marker ensures that the document can always be referenced and retrieved in its original form, providing a single source of truth.

[0088] The connection between the content, audit trail, and global marker established through cryptographic linking. The global marker is embedded in the document's metadata, and the metadata itself is cryptographically secured to prevent tampering. The audit trail is also linked to the global marker, ensuring that every recorded event is associated with the correct document. This triad-immutable content, immutable audit trail, and an immutable associated between the global marker and the content and audit trail— creates a robust framework that will revolutionize document management and control.

[0089] The immutability of the content, the audit trail, the global marker and of the link between the marker and the data (i.e., the content, the audit trail, and any other metadata) and the global marker, can have one or more of a variety of characteristics:

[0090] Unchangeable: Immutable refers to something that cannot be altered, modified, or edited once it has been created or finalized.

[0091] Permanent: Immutable signifies a state of permanence, where the object or data remains fixed and consistent over time.

[0092] Irreversible: Immutable describes a condition where changes are impossible, and any attempt to alter the object or data is invalid or rejected.

[0093] Fixed: Immutable means that the structure, content, or state of an object is locked and cannot be adjusted or updated.

[0094] Tamper-Proof: Immutable implies that the object or data is resistant to tampering, ensuring its integrity and authenticity.

[0095] Finalized: Immutable refers to an object or data that has reached its final form and cannot be reverted or reshaped.

[0096] Unmodifiable: Immutable describes a characteristic where the object or data is impervious to modification, whether intentional or accidental.

[0097] Consistent: Immutable ensures that the object or data remains consistent and reliable, unaffected by external influences or changes.

[0098] Secure: Immutable denotes a state of security where the object or data is safeguarded against unauthorized alterations or corruption.

[0099] indelible: Immutable refers to something that is permanent and cannot be erased, overwritten, or replaced.

[0100] Benefits of the immutable Structure

[0101] Integrity: The immutability of the content ensures that the document remains unchanged and trustworthy throughout its lifecycle.

[0102] Traceability: The immutable audit trail provides a complete and verifiable history of all interactions with the document.

[0103] Authenticity: The permanent global marker guarantees that the document can always be uniquely identified and retrieved, eliminating ambiguity.

[0104] Compliance: This structure simplifies regulatory compliance by providing a reliable and tamper-proof record of the document and its history.

[0105] Interoperability: The global marker enables seamless integration with external systems, ensuring that the document can be referenced and verified across different platforms.

[0106] In summary, a smart document achieves immutability of its content and audit trail while ensuring both are immutably connected to a permanent global marker. This design provides a transformative solution for document management, offering unparalleled integrity, authenticity, and traceability.

[0107] While in some examples of smart documents the content, the audit trail, and the link to the global marker are all immutable, in other examples one of or two of these three items may be immutable. In some examples, the entirety of the content and the audit trail are immutable, and in others only a portion of the content and / or the audit trail are immutable. Furthermore, a smart document may have content and an audit trail that are immutable while having other metadata that is changeable (e.g., comments, access rights, etc.)

[0108] In addition to the foundational features of immutability, smart documents possess embedded intelligence that enables them to actively interact with their environment, respond to requests, and perform actions autonomously. This intelligence transforms the document from a static repository of information into a dynamic, interactive entity capable of understanding and adapting to its context. Embedded intelligence in smart documents is achieved through the integration of executable code, metadata, and machine-readable content, all of which work together to create a responsive and self-aware system.

[0109] Features of Embedded Intelligence

[0110] Seif-Determination and Responsiveness: Smart documents are equipped with the ability to process requests and respond dynamically. For example, when a user or system queries a document, the embedded intelligence allows the document to access its metadata, audit trail, and content to determine the appropriate response. This responsiveness is not limited to simple data retrieval; the document can also perform complex operations, such as verifying its authenticity, providing access logs, or extracting specific information from its content.

[0111] Contextual Awareness: Smart documents can understand and adapt to their context. This includes recognizing the identity of the user accessing the document, the device being used, the location of the access, and the stage of the document’s lifecycle. For instance, a contract document may display different user interfaces depending on whether it is being accessed by the creator, a signatory, or a reviewer. Similarly, the document can adapt its behavior based on whether it is being accessed on a mobile device, desktop, or tablet.

[0112] Negotiation of Communication Protocols: Smart documents are capable of negotiating the manner in which they communicate with external systems. They can respond to requests using various protocols, such as RESTful APIs, gRPC, or even machine-specific languages like MCP (Machine Communication Protocol). This flexibility ensures that the document can seamlessly integrate with diverse systems and applications, making it highly interoperable.

[0113] Dynamic User Experience: The embedded intelligence enables smart documents to create personalized user experiences. For example, the document can present different panels, workflows, or visualizations depending on the user's role, the document'slifecycle stage, or the specific task being performed. This dynamic adaptability enhances usability and ensures that the document serves the needs of each stakeholder effectively.

[0114] Machine Learning and Predictive Capabilities: Smart documents can leverage machine learning algorithms to analyze their audit trail, content, and metadata to predict user needs or suggest actions. For instance, a smart document could identify patterns in user interactions and recommend next steps, such as suggesting additional documents that may be relevant to the current task or flagging anomalies in the audit trail for review.

[0115] How Intelligence is Embedded

[0116] The intelligence of smart documents is embedded through the integration of one or more components:

[0117] Executable Code: At the core of a smart document's intelligence is its embedded executable code. This code acts as the "brain" of the document, enabling it to process requests, perform actions, and interact with external systems. The code is designed to be lightweight and modular, allowing it to execute specific tasks efficiently without compromising the document’s performance.

[0118] Metadata: Metadata provides the document with contextual information about itself, such as its creation date, owner, version history, and access permissions. This metadata is stored in a machine-readable format and is cryptographically secured to ensure its integrity. The document's intelligence uses this metadata to make decisions and respond to queries.

[0119] Machine-Readable Content: Unlike traditional documents, which are primarily human-readable, smart documents store their content in a machine-readableformat. This allows the embedded intelligence to analyze the content, extract specific information, and perform operations based on the content's structure and meaning.

[0120] APIs for Interaction: Smart documents expose APIs (ApplicationProgramming interfaces) that allow external systems to interact with them. These APIs enable the document to receive requests, process them, and return responses in a structured format, such as JSON or XML. The APIs also facilitate integration with other applications and systems, making the document highly interoperable.

[0121] Cryptographic Infrastructure: The intelligence of smart documents is underpinned by cryptographic infrastructure, which ensures the security and authenticity of the document's interactions. For example, digital signatures and hash-based identifiers are used to verify the integrity of the document and its audit trail, while encryption protects sensitive data.

[0122] Machine Learning Models: Machine learning models can be embedded within the document or accessed through external systems to enhance its intelligence. These models enable the document to analyze patterns, predict outcomes, and adapt its behavior based on historical data and real-time inputs.

[0123] Examples of Embedded Intelligence in Action

[0124] Audit Trail Analysis: A smart document can analyze its audit trail to identify unusual patterns, such as repeated failed access attempts, and alert the owner to potential security risks.

[0125] Dynamic Rendering: When accessed on a mobile device, a smart document can automatically adjust its layout to optimize readability and usability, while providing additional features like touch-based navigation.

[0126] Workflow Management: A smart document associated with a workflow can track its progress and notify stakeholders of pending actions, such as signatures or approvals.

[0127] Content Extraction: A smart document can respond to a query by extracting specific information from its content, such as the total amount in an invoice or the number of items listed in a receipt.

[0128] Protocol Negotiation: A smart document can negotiate the format of its responses based on the preferences of the requesting system, such as providing data in JSON for web applications or XML for enterprise systems.

[0129] In summary, the embedded intelligence of smart documents is achieved through the integration of executable code, metadata, machine-readable content, APIs, cryptographic infrastructure, and machine learning models. This intelligence enables the document to interact dynamically with its environment, adapt to its context, and provide personalized experiences, making it a transformative innovation in document management.

[0130] The combination of immutability and embedded intelligence in smart documents creates a transformative paradigm for document management, offering unparalleled integrity, authenticity, traceability, and adaptability. Together, these features address longstanding challenges in document security, compliance, and usability, while enabling dynamic interactions and personalized experiences.

[0131] The Synergy of immutability and Embedded intelligence

[0132] The combination of immutability and embedded intelligence creates a powerful synergy that revolutionizes document management. Immutability provides the foundation of trust, ensuring that the document's content and history are secure, authentic, and tamper-proof. Embedded intelligence builds on this foundation, enabling the documentto interact dynamically with its environment, adapt to its context, and provide personalized experiences.

[0133] Enhanced integrity and Authenticity: Immutability ensures that the document's content and audit trail remain unchanged, while embedded intelligence enables the document to verify its authenticity and respond to queries about its provenance.Together, these features create a system where trust is inherent and verifiable.

[0134] Dynamic Traceability: The immutable audit trail provides a complete history of interactions with the document, while embedded intelligence allows the document to analyze and interpret this history. This dynamic traceability enables stakeholders to understand not only what happened to the document but also why and how.

[0135] Personalized Compliance: Immutability simplifies regulatory compliance by providing a reliable and tamper-proof record of the document and its history. Embedded intelligence enhances this by adapting the document's behavior to meet specific compliance requirements, such as displaying relevant panels or workflows based on the user's role or jurisdiction.

[0136] Interoperability and Adaptability: The permanent global marker ensures seamless integration with external systems, while embedded intelligence enables the document to negotiate communication protocols and adapt its responses to different platforms. This combination ensures that the document can function effectively in diverse environments.

[0137] Predictive Security and Usability: Immutability protects the document from tampering, while embedded intelligence leverages machine learning to predict potentialsecurity risks and suggest preventive actions. This proactive approach enhances both security and usability, ensuring that the document serves the needs of its stakeholders effectively.

[0138] Real-World Applications

[0139] The synergy of immutability and embedded intelligence has transformative implications across industries:

[0140] Legal and Compliance: Smart contracts can ensure the integrity of agreements while dynamically adapting to regulatory changes.

[0141] Finance: Immutable audit trails and intelligent analysis can enhance fraud detection and streamline reporting.

[0142] Healthcare: Patient records can remain secure and authentic while providing personalized access to authorized stakeholders.

[0143] Supply Chain: Immutable tracking and intelligent analysis can optimize logistics and ensure product authenticity.

[0144] In summary, the combination of immutability and embedded intelligence in smart documents creates a revolutionary framework for document management. By ensuring integrity, authenticity, and traceability while enabling dynamic interactions and personalized experiences, this synergy addresses longstanding challenges and unlocks new possibilities for innovation and efficiency.

[0145] Alternative Terminology

[0146] The term "smart document" or "smart electronic document" can also be referred to as a self-determinative document, a self-tracking document, a self-assimilating document, a document with executable code, a document with embedded code, and / or in a variety of other ways depending on the context and on the features of the smart document.In any example, a smart electronic includes three elements, at minimum— data (e.g., content, audit trail, other metadata, etc.), executable code (e.g., an API), and a globally unique marker.[0147) The methods described herein leverages the foundational features of self- tracking documents to address technical problems inherent in traditional document systems, such as the lack of integrated event tracking, limited accessibility to historical data, and the inability to autonomously manage interactions. By embedding intelligence into the document and enabling it to identify, store, and provide information about events, the method transforms the document into a dynamic and interactive entity capable of managing its lifecycle and interactions autonomously.

[0148] The process begins with the self-tracking document identifying an event associated with itself. This capability addresses the technical problem of fragmented and inconsistent event tracking in traditional systems, where interactions with documents are often recorded externally in separate logs or databases. The self-tracking document eliminates this fragmentation by autonomously identifying events, such as access attempts, modifications, approvals, or signatures, and recording them as part of its internal metadata.For example, when a user accesses the document, the self-tracking document identifies the event and captures details such as the user's identity, the time of access, and the nature of the interaction. This ensures that all events associated with the document are recorded in a unified and consistent manner, providing a reliable source of truth for the document's lifecycle.

[0149] The method further involves storing information about the identified event within the self-tracking document. This step addresses the technical problem of limited accessibility to historical data in traditional systems, where event information is oftenscattered across multiple platforms or lost due to inadequate tracking mechanisms. By storing event information directiy within the document, the method ensures that the document serves as a single repository for all interactions, eliminating duplication and maintaining consistency. The information is stored as structured metadata, allowing the document to organize and categorize events in a way that is easily accessible and actionable. For example, the document can store details about a signature event, including the identity of the signatory, the timestamp, and the method of authentication. This capability enhances the document's utility and ensures that its event history remains reliable and secure.

[0150] The method also involves receiving a request to access the information about the event. This capability addresses the technical problem of limited accessibility and control in traditional document systems, where users often struggle to retrieve specific event information due to fragmented storage or lack of integrated access mechanisms. The selftracking document's embedded intelligence allows it to process requests autonomously, ensuring that users can access event information directly from the document without relying on external systems. For example, a user can request information about a specific modification event, and the document can retrieve and present the relevant details, such as the nature of the change, the identity of the user who made the modification, and the timestamp. This capability enhances transparency and accountability, ensuring that users can access the information they need to make informed decisions.

[0151] The final step of the method involves providing the information about the self-tracking document in response to the request. This capability addresses the technical problem of inefficient and inconsistent data retrieval in traditional systems, where users often face delays or inaccuracies when attempting to access event information. The self-trackingdocument's embedded intelligence allows it to respond to requests in real time, ensuring that users receive accurate and relevant information without unnecessary delays. For example, the document can provide a complete audit trail of all interactions, including access attempts, modifications, approvals, and signatures, allowing users to analyze the document's lifecycle and verify compliance with regulatory requirements. This capability enhances the document's utility and ensures that its event history remains accessible and actionable.

[0152] The method also leverages the immutable structure of self-tracking documents to address technical problems related to tampering and inconsistency. The document's content and audit trail are cryptographically secured, ensuring that they remain unchanged and trustworthy throughout its lifecycle. When the document identifies and stores event information, it uses cryptographic techniques, such as hashing and digital signatures, to secure the data and prevent unauthorized modifications. For example, the document can hash the details of an access event to produce a unique cryptographic fingerprint, which serves as a reference for verifying the integrity of the event information.These measures ensure that the document's event history remains reliable and tamper-proof, providing a transparent and verifiable record of interactions.

[0153] The permanent global marker embedded in the document's metadata further enhances its ability to address technical problems related to accessibility and traceability. This marker serves as a unique and unchanging identifier, allowing the document to maintain a single source of truth for its event history. The global marker ensures that the document can always be referenced and retrieved in its original form, eliminating ambiguity and enabling seamless integration with external systems. By leveraging this marker, thedocument ensures that its event information remains consistent and reliable across diverse platforms and applications.

[0154] The method also leverages the dynamic rendering capabilities of selftracking documents to enhance the accessibility and usability of event information. The document's embedded intelligence allows it to adapt its presentation based on the user's preferences and contextual factors, ensuring that event information is presented in a format that is easy to understand and analyze. For example, the document can provide a visual timeline of events, highlighting key interactions and categorizing them based on their nature, such as access attempts, modifications, or approvals. This capability enhances the document's utility and ensures that users can access event information in a way that aligns with their needs and objectives.

[0155] By leveraging the features of self-tracking documents, the method described in the claim addresses technical problems related to event tracking, data storage, accessibility, and retrieval. The ability to identify, store, and provide information about events transforms the document into a dynamic and interactive entity capable of managing its lifecycle autonomously. The cryptographic security and global marker ensure that the document's event history remains reliable and trustworthy, while the dynamic rendering capabilities enhance its accessibility and usability. This method redefines the role of digital documents, offering a solution that integrates content, context, and intelligence to create a robust framework for modern workflows.

[0156] Aspects of this disclosure address the technical problem of maintaining control and security over electronic documents once they have been shared beyond their original digital perimeter and the inefficient use of network and computing resourcesassociated with separate tracking of events, timelines, and audit trails. In traditional document management systems, once a document is distributed, the original owner or creator loses control over how the document is accessed, shared, or modified. Aspects of this disclosure provide a technical solution by introducing a method that provisions the document as self-tracking, embedding intelligence within the document itself. This intelligence enables the document to function as a smart digital object, allowing for remote management and control. The method includes identifying events associated with the document, storing information about these events, receiving access requests, and providing information— -all executed by the document. This approach ensures that the document's owner can maintain control over the document's content, manage access permissions dynamically, and monitor interactions in real-time, regardless of the document's location or the number of copies in existence. By transforming the document into an active, controllable entity, the invention provides a robust solution to the challenges of document security and control in modern digital environments.

[0157] For computing device hardware, the embedded intelligence enables the device to dynamically manage access to the document, reducing the need for additional intervention and minimizing processing overhead. This capability ensures that the device can adapt to changing security requirements and organizational policies, providing a more responsive and secure document management system. The intelligence also facilitates seamless integration with other systems and applications, allowing the device to interact with a broader digital ecosystem without compatibility issues, reducing the overhead of dealing with such issues. This integration supports enhanced functionalities such as automatedworkflows, data synchronization, and collaborative features, expanding the device's utility and efficiency in managing digital documents.

[0158] For networks, the solution reduces bandwidth consumption and improves data transmission by maintaining a single source of truth for each document. Instead of distributing multiple copies, the document is accessed and managed through a centralized system, ensuring consistency and reducing redundancy. This approach minimizes network load and enhances data integrity, allowing for more efficient use of network resources.Additionally, the ability to monitor document interactions in real-time provides immediate feedback on access attempts and changes, enhancing network security by enabling quick detection and response to unauthorized access or tampering.

[0159] A self-tracking document can be a transformative technical solution to the longstanding technical problem of maintaining control, security, and traceability over distributed digital documents. Traditional document systems often suffer from vulnerabilities such as unauthorized modifications, fragmented audit trails, and inconsistent access control, which compromise data integrity and operational efficiency. A self-tracking document can address these issues by incorporating immutable content and an immutable audit trail, both of which are immutably connected to an immutable global identifier. This unified structure ensures that the document's content, history, and identity remain tamper-proof, trustworthy, and machine-readable, enabling seamless integration with computational systems and applications. Additionally, the document functions as infrastructure by embedding intelligence in the form of executable code, enabling it to be responsive and interactive. This embedded code enables the document to autonomously enforce access permissions, respond to queries, and execute workflows, transforming it from a static file into a dynamic, self-governing entity. By combining immutability, machine-readability, and embedded intelligence, the self-tracking document provides a robust solution to the challenges of document security, traceability, and operational efficiency in modern digital ecosystems.

[0160] A self-tracking document can solve the problems of data security, inefficient use of device hardware, and inefficient use of network systems associated with traditional PDFs by leveraging its immutable structure, embedded intelligence, and machinereadable design. In terms of data security, the document's cryptographic commitments ensure that its content, audit trail, and global identifier remain tamper-proof and trustworthy, eliminating vulnerabilities inherent in PDFs, which often rely on external systems for encryption and access control. The embedded intelligence within the self-tracking document can autonomously enforce granular access permissions, dynamically adapting to user roles and security protocols, reducing the risk of unauthorized access and ensuring compliance with stringent security requirements.

[0161] Regarding device hardware, traditional PDFs require significant computational resources for rendering, extracting data, and managing versions, often leading to inefficiencies and hardware strain. A self-tracking document, with its machine-readable format and embedded intelligence, can eliminate the need for complex text extraction algorithms and redundant processing, optimizing the use of device hardware and enabling faster, more efficient operations. Similarly, network systems that handle PDFs often experience bandwidth inefficiencies due to the need to transmit large, static files and duplicate versions. A self-tracking document can address this by maintaining a single source of truth that is universally accessible via its global identifier, reducing the need to transmit entire files and instead enabling lightweight, API-driven interactions. This approach canreduce network bandwidth usage, streamlines workflows, and ensures that documents are securely and efficiently managed across devices and systems, making them ideal for modern digitai ecosystems.

[0162] In conclusion, the aspects described herein represent a significant advancement in document management technology, transforming traditional documents into self-tracking entities capable of autonomous operation. As organizations continue to navigate the complexities of digital information exchange, the adoption of self-tracking documents promises to streamline processes, safeguard sensitive data, and empower users with unprecedented control over their digital assets. This transformative approach not only enhances document security and management but also supports compliance with regulatory requirements, ensuring that all document-related activities are transparent, traceable, and verifiable.

[0163] Clause 1. A method comprising: identifying, by a self-tracking document, an event associated with the self-tracking document; storing, by the self-tracking document, information about the event with the self-tracking document; receiving, at the seif-tracking document, a request to access the information about the event; and providing, by the selftracking document and in response to the request, the information about the self-tracking document in response to the request.

[0164] Clause 2. The method of clause 1, wherein storing the information about the event comprises storing the information about the event as metadata of the self-tracking document.

[0165] Clause 3. The method of clauses 1-2, wherein storing the information about the event comprises protecting the information about the event from ever being modified.

[0166] Clause 4. The method of clauses 1-3, wherein: the event comprises a legal event; and storing information about the event comprises storing information about the legal event.

[0167] Clause 5. The method of clauses l-4;wherein: the information about the event comprises a compliance event; and storing the information about the event comprises storing information about the compliance event.

[0168] Clause 6. The method of clauses 1-5, wherein providing the information about the self-tracking document in response to the request comprises providing an audit trail of the self-tracking document.

[0169] Clause 7. The method of clauses 1-6, wherein: identifying the event associated with the self-tracking document comprises identifying that a new version of the self-tracking document has been created; and storing the information about the event with the self-tracking document comprises tracking each version of the self-tracking document.

[0170] Clause 8. The method of clauses 1-7, wherein: identifying the event associated with the self-tracking document comprises identifying a geo-location of the event; and storing the information about the event with the self-tracking document comprises storing the geolocation of the event.

[0171] Clause 9. The method of clauses 1-8. wherein: receiving, at the self-tracking document, the request to access the information about the event comprises receiving a request to access information about a plurality of events associated with the self-tracking document; and providing, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request comprises providing, in response to the request, a timeline of the plurality of events.

[0172] Clause 10. The method of clauses 1-9, wherein receiving, at the selftracking document, the request to access the information about the event comprises receiving a request to access information about a plurality of events associated with the selftracking document; and providing, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request comprises providing, in response to the request a non-chronological representation of the plurality of events that is organized in response to a context of the request instead of being organized chronologically.

[0173] Clause 11. The method of clauses 1-10, wherein: identifying the event associated with the self-tracking document comprises identifying a marketing event associated with the self-tracking document; and storing the information about the event with the self-tracking document comprises storing information about the marketing event.

[0174] Clause 12. The method of clauses 1-11, wherein: providing the information about the self-tracking document in response to the request comprises providing at least one of: information about a lead associated with the self-tracking document; an engagement metric associated with the self-tracking document; an interaction receipt associated with the self-tracking document; and a marketing test result associated with the self-tracking document.

[0175] Clause 13. A system comprising: one or more physical processors; physical memory comprising computer-executable instructions that, when executed by the one or more physical processors, cause at least one of the one or more physical processors to: identify, by a self-tracking document, an event associated with the self-tracking document; store, by the self-tracking document, information about the event with the self-trackingdocument; receive, at the self-tracking document, a request to access the information about the event; and provide, by the seif-tracking document and in response to the request, the information about the seif-tracking document in response to the request.

[0176] Clause 14. The system of clause 13, wherein the computer-executable instructions cause the one or more physical processors to store the information about the event by storing the information about the event as metadata of the self -tracking document.

[0177] Clause 15. The system of clauses 13-14, wherein the computer-executable instructions cause the one or more physical processors to store the information about the event by protecting the information about the event from being modified.

[0178] Clause 16. The system of clauses 13-15, wherein the event comprises at least one of: a legal event; a compliance event; a geo-location event; and a marketing event.

[0179] Clause 17. The system of clauses 13-16, wherein the computer-executable instructions cause the one or more physical processors to provide the information about the self-tracking document in response to the request by providing an audit trail of the self- tracking document.

[0180] Clause 18. The system of clauses 13-17, wherein: the computer-executable instructions cause the one or more physical processors to identify the event associated with the self-tracking document by identifying that a new version of the self-tracking document has been created; and the computer-executable instructions cause the one or more physical processors to store the information about the event with the self-tracking document and comprise tracking each version of the self-tracking document.

[0181] Clause 19. The system of clauses 13-18, wherein: the computer-executable instructions cause the one or more physical processors to receive, at the self-trackingdocument, the request to access the information about the event by receiving a request to access information about a plurality of events associated with the self-tracking document; and the computer-executable instructions cause the one or more physical processors to provide, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request by providing, in response to the request, a timeline of the plurality of events.

[0182] Clause 20. The system of clauses 13-19, wherein: the computer-executable instructions cause the one or more physical processors to receive, at the self-tracking document, the request to access the information about the event by receiving a request to access information about a plurality of events associated with the document; and the computer-executable instructions cause the one or more physical processors to provide, by the self-tracking document and in response to the request, the information about the selftracking document in response to the request by providing, in response to the request a nonchronological representation of the plurality of events that is organized in response to a context of the request instead of being organized chronologically.

[0183] Clause 21. A non-transitory computer-readable medium comprising computer-executable instructions that, when executed by at least one of one or more physical processors of a computing device, cause the computing device to: identify, by a self-tracking document, an event associated with the self-tracking document, store, by the self-tracking document, information about the event with the self-tracking document, receive, at the selftracking document, a request to access the information about the event, and provide, by the self-tracking document and in response to the request, the information about the selftracking document in response to the request.

[0184] Clause 22. The non-transitory computer-readable medium of clause 21, wherein the computer-executable instructions cause the one or more physical processors to store the information about the event by storing the information about the event as metadata of the self-tracking document.

[0185] Clause 23. The non-transitory computer-readable medium of clauses 21-22, wherein the computer-executable instructions cause the one or more physical processors to store the information about the event by protecting the information about the event from being modified.

[0186] Clause 24. The non-transitory computer-readable medium of clauses 21-23, wherein the event comprises at least one of: a legal event; a compliance event; a geo- location event; and a marketing event.

[0187] Clause 2b. The non-transitory computer-readable medium of clauses 21-24, wherein the computer-executable instructions cause the one or more physical processors to provide the information about the self-tracking document in response to the request by providing an audit trail of the self-tracking document.

[0188] Clause 26. The non-transitory computer-readable medium of clauses 21-25, wherein: the computer -executable instructions cause the one or more physical processors to identify the event associated with the self-tracking document by identifying that a new version of the self-tracking document has been created; and the computer-executable instructions cause the one or more physical processors to store the information about the event with the self-tracking document by tracking each version of the self-tracking document.

[0189] Clause 27. The non-transitory computer-readable medium of clauses 21-26, wherein: the computer-executable instructions cause the one or more physical processorsto receive, at the seif-tracking document, the request to access the information about the event by receiving a request to access information about a plurality of events associated with the document; and the computer-executable instructions cause the one or more physical processors to provide, by the seif-tracking document and in response to the request, the information about the self-tracking document in response to the request by providing, in response to the request, a timeline of the plurality of events.

[0190] Clause 28. The non-transitory computer-readable medium of clauses 21-27, wherein: the computer-executable instructions cause the one or more physical processors to receive, at the self-tracking document, the request to access the information about the event by receiving a request to access information about a plurality of events associated with the document; and the computer-executable instructions cause the one or more physical processors to provide, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request by providing, in response to the request a non-chronological representation of the plurality of events that is organized in response to a context of the request instead of being organized chronologically.

[0191] The features and clauses discussed herein may provide one or more of the advantages and / or solutions described, such as enhancing security, improving operational efficiency, or enabling dynamic access control. Additionally, these features and clauses may offer further or alternative benefits or address further or alternative challenges beyond those explicitly mentioned. The disclosed features and clauses are not limited to the specific advantages or solutions described and may be implemented in various ways to achieve additional or alternative benefits and / or solutions.

[0192] In some examples, the term "memory device" generally refers to any type or form of volatile or non-volatile storage device or medium capable of storing data and / or computer-readable instructions. In one example, a memory device may store, load, and / or maintain one or more of the modules described herein. Examples of memory devices include, without limitation, Random Access Memory (RAM), Read Only Memory (ROM), flash memory,Hard Disk Drives (HDDs), Solid-State Drives (SSDs), optical disk drives, caches, variations or combinations of one or more of the same, or any other suitable storage memory.

[0193] In some examples, the term "physical processor" generally refers to any type or form of hardware-implemented processing unit capable of interpreting and / or executing computer-readable instructions. In one example, a physical processor may access and / or modify one or more modules stored in the above-described memory device. Examples of physical processors include, without limitation, microprocessors, microcontrollers, CentralProcessing Units (CPUs), Field-Programmable Gate Arrays (FPGAs) that implement softcore processors, Application-Specific Integrated Circuits (ASICs), portions of one or more of the same, variations or combinations of one or more of the same, or any other suitable physical processor.

[0194] Although illustrated as separate elements, the modules described and / or illustrated herein may represent portions of a single module or application. In addition, in certain embodiments one or more of these modules may represent one or more software applications or programs that, when executed by a computing device, may cause the computing device to perform one or more tasks. For example, one or more of the modules described and / or illustrated herein may represent modules stored and configured to run on one or more of the computing devices or systems described and / or illustrated herein. One ormore of these modules may also represent all or portions of one or more special-purpose computers configured to perform one or more tasks.

[0195] In addition, one or more of the modules described herein may transform data, physical devices, and / or representations of physical devices from one form to another.Additionally or alternatively, one or more of the modules recited herein may transform a processor, volatile memory, non-volatile memory, and / or any other portion of a physical computing device from one form to another by executing on the computing device, storing data on the computing device, and / or otherwise interacting with the computing device.

[0196] In some embodiments, the term "computer-readable medium" generally refers to any form of device, carrier, or medium capable of storing or carrying computer- readable instructions. Examples of computer-readable media include, without limitation, transmission-type media, such as carrier waves, and non-transitory-type media, such as magnetic-storage media (e.g., hard disk drives, tape drives, and floppy disks), optical-storage media (e.g., Compact Disks (CDs), Digital Video Disks (DVDs), and BLU-RAY disks), electronic- storage media (e.g., solid-state drives and flash media), and other distribution systems.

[0197] The process parameters and sequence of the steps described and / or illustrated herein are given by way of example only and can be varied as desired. For example, while the steps illustrated and / or described herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order illustrated or discussed. The various exemplary methods described and / or illustrated herein may also omit one or more of the steps described or illustrated herein or include additional steps in addition to those disclosed.

[0198] The preceding description has been provided to enabie others skilled in the art to best utilize various aspects of the exemplary embodiments disclosed herein. This exemplary description is not intended to be exhaustive or to be limited to any precise form disclosed. Many modifications and variations are possible without departing from the spirit and scope of the present disclosure. The embodiments disclosed herein should be considered in all respects illustrative and not restrictive. Reference should be made to the appended claims and their equivalents in determining the scope of the present disclosure.

[0199] Unless otherwise noted, the terms "connected to" and "coupled to" (and their derivatives), as used in the specification and claims, are to be construed as permitting both direct and indirect (i.e., via other elements or components) connection. In addition, the terms "a" or "an," as used in the specification and claims, are to be construed as meaning "at least one of." Finally, for ease of use, the terms "including" and having" (and their derivatives), as used in the specification and claims, are interchangeable with and have the same meaning as the word "comprising.”

Claims

AMENDED CLAIMS received by the International Bureau on 20 Oct 2025(20.10.2025)1. A method comprising: identifying, by a self-tracking document, an event associated with the self-tracking document; storing, by the self-tracking document, information about the event with the selftracking document; receiving, at the self-tracking document, a request to access the information about the event; and providing, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request.

2. The method of claim 1, wherein storing the information about the event comprises storing the information about the event as metadata of the self-tracking document.

3. The method of claim 1, wherein storing the information about the event comprises protecting the information about the event from being modified.

4. The method of claim 1, wherein: the event comprising a legal event; and storing information about the event comprises storing information about the legal event.

5. The method of claim 1, wherein the identifying, storing, receiving, and providing steps are performed by intelligence embedded within the self-tracking document that acts as a brain of the document.

6. The method of claim 1, wherein providing the information about the self- tracking document in response to the request comprises providing an audit trail of the self- tracking document.

7. The method of claim 1, wherein: identifying the event associated with the self-tracking document comprises identifying that a new version of the self-tracking document has been created; and storing the information about the event with the self-tracking document comprises tracking each version of the self-tracking document.

8. The method of claim 1, wherein: identifying the event associated with the self-tracking document comprises identifying a geo-location of the event; and storing the information about the event with the self-tracking document comprises storing the geo-location of the event.

9. The method of claim 1, wherein: receiving, at the self-tracking document, the request to access the information about the event comprises receiving a request to access information about a plurality of events associated with the self-tracking document; andproviding, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request comprises providing, in response to the request, a timeline of the plurality of events.

10. The method of claim 1, wherein: receiving, at the self-tracking document, the request to access the information about the event comprises receiving a request to access information about a plurality of events associated with the self-tracking document; and providing, by the self-tracking document and in response to the request, the information about the self-tracking document in response to request by providing, in response to the request a non-chronological representation of the plurality of events that is organized in response to a context of the request instead of being organized chronologically.

11. The method of claim 1, wherein: identifying the event associated with the self-tracking document comprises identifying a marketing event associated with the self-tracking document; and storing the information about the event with the self-tracking document comprises storing information about the marketing event.

12. The method of claim 1, wherein: providing the information about the self-tracking document in response to request comprising providing at least one of: information about a lead associated with the self-tracking document; an engagement metric associated with the self-tracking document;an interaction receipt associated with the self-tracking document; and a marketing test result associated with the self-tracking document.

13. The method of claim 1, wherein providing the information about the self- tracking document comprises displaying different levels of detail according to a permission of a user.

14. The method of claim 1, further comprising: leveraging, by the self-tracking document, a machine learning algorithm to analyze an audit trail of the self-tracking document; and flagging an anomaly in the audit trail for review.

15. The method of claim 1, further comprising: identifying, via a machine learning capability of the self-tracking document, a pattern in user interactions with the self-tracking document; and suggesting, via the machine learning capability, additional documents relevant to a current task.

16. The method of claim 1, further comprising providing, by the self-tracking document, standardized data to an artificial intelligence system for analysis in a manner that ensures that systems interacting with the self-tracking document are aligned with a true state of the self-tracking document.

17. The method of claim 1, further comprising leveraging, by the self-tracking document, a machine learning algorithm to predict a need of a user.

18. The method of claim 5, wherein the embedded intelligence is configured to autonomously manage interactions of the self-tracking document with users and systems such that the self-tracking document independently receives, evaluates, and responds to access requests without reliance on an external system.

19. The method of claim 1, wherein the self-tracking document is configured to process a request from an artificial intelligence agent using embedded intelligence of the self-tracking document in a manner that provides a response tailored to a context of the request.

20. The method of claim 1, wherein the self-tracking document is configured to maintain an audit trail for interactions between artificial intelligence agents and the selftracking document by recording which agents accessed which portions of the self-tracking document and for what purpose.

21. The method of claim 1, wherein the self-tracking document enables artificial intelligence analysis of engagement with the self-tracking document.

22. The method of claim 1, wherein: the self-tracking document is configured to distinguish between an interaction with a human user and an interaction with an automated system; andthe self-tracking document is configured to control access to the self-tracking document based on distinguishing between the interaction with the human user and the interaction with the automated system.

23. A system comprising: one or more physical processors; and physical memory comprising computer-executable instructions that, when executed by the one or more physical processors, cause at least one of the one or more physical processors to: identify, by a self-tracking document, an event associated with the selftracking document; store, by the self-tracking document, information about the event with the self-tracking document; receive, at the self-tracking document, a request to access the information about the event; and provide, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request.

24. The system of claim 23, wherein the computer-executable instructions cause the one or more physical processors to store the information about the event by storing the information about the event as metadata of the self-tracking document.

25. The system of claim 23, wherein the computer-executable instructions cause the one or more physical processors to store the information about the event by protecting the information about the event from being modified.

26. The system of claim 23, wherein the event comprises at least one of: a legal event; a compliance event; a geo-location event; and a marketing event.'Ll. The system of claim 23, wherein the computer-executable instructions cause the one or more physical processors to provide the information about the self-tracking document in response to the request by providing an audit trail of the self-tracking document.

28. The system of claim 23, wherein: the computer-executable instructions cause the one or more physical processors to identify the event associated with the self-tracking document by identifying that a new version of the self-tracking document has been created; and the computer-executable instructions cause the one or more physical processors to store the information about the event with the self-tracking document by tracking each version of the self-tracking document.

29. The system of claim 23, wherein:the computer-executable instructions cause the one or more physical processors to receive, at the self-tracking document, the request to access the information about the event by receiving a request to access information about a plurality of events associated with the self-tracking document; and the computer-executable instructions cause the one or more physical processors to provide, by the self-tracking document and in response to the request, the information about the self-tracking document as a timeline of the plurality of events.

30. The system of claim 23, wherein: the computer-executable instructions cause the one or more physical processors to receive, at the self-tracking document, the request to access the information about the event by receiving a request to access information about a plurality of events associated with the self-tracking document; and the computer-executable instructions cause the one or more physical processors to provide, by the self-tracking document and in response to the request, the information about the self-tracking document as a non-chronological representation of the plurality of events that is organized in response to a context of the request instead of being organized chronologically.

31. A non-transitory computer-readable medium comprising computer- executable instructions that, when executed by at least one of one or more physical processors of a computing device, cause the computing device to: identify, by a self-tracking document, an event associated with the self-tracking document;store, by the self-tracking document, information about the event with the selftracking document; receive, at the self-tracking document, a request to access the information about the event; and provide, by the self-tracking document and in response to the request, the information about the self-tracking document in response to the request.

32. The non-transitory computer-readable medium of claim 31, wherein the computer-executable instructions cause the one or more physical processors to store the information about the event by storing the information about the event as metadata of the self-tracking document.

33. The non-transitory computer-readable medium of claim 31, wherein the computer-executable instructions cause the one or more physical processors to store the information about the event by protecting the information about the event from being modified.

34. The non-transitory computer-readable medium of claim 31, wherein the event comprises at least one of: a legal event; a compliance event; a geo-location event; and a marketing event.

35. The non-transitory computer-readable medium of claim 31, wherein the computer-executable instructions cause the one or more physical processors to provide the information about the self-tracking document in response to the request by providing an audit trail of the self-tracking document.

36. The non-transitory computer-readable medium of claim 31, wherein: the computer-executable instructions cause the one or more physical processors to identify the event associated with the self-tracking document by identifying that a new version of the self-tracking document has been created; and the computer-executable instructions cause the one or more physical processors to store the information about the event with the self-tracking document by tracking each version of the self-tracking document.

37. The non-transitory computer-readable medium of claim 31, wherein: the computer-executable instructions cause the one or more physical processors to receive, at the self-tracking document, the request to access the information about the event by receiving a request to access information about a plurality of events associated with the self-tracking document; and the computer-executable instructions cause the one or more physical processors to provide, by the self-tracking document and in response to the request, a timeline of the plurality of events.

38. The non-transitory computer-readable medium of claim 31, wherein:the computer-executable instructions cause the one or more physical processors to receive, at the self-tracking document, the request to access the information about the event by receiving a request to access information about a plurality of events associated with the self-tracking document; and the computer-executable instructions cause the one or more physical processors to provide, by the self-tracking document and in response to the request, the information about the self-tracking document in response to request by providing, in response to the request a non-chronological representation of the plurality of events that is organized in response to a context of the request instead of being organized chronologically.ConclusionApplicant expressly disclaims all arguments, representations, and / or amendments presented or contained in any other patent or patent application, including any patents or patent applications claimed for priority purposes by the present application or any patents or patent applications that claim priority to this patent application. Moreover, all arguments, representations, and / or amendments presented or contained in the present patent application are only applicable to the present patent application and should not be considered when evaluating any other patent or patent application.Respectfully submitted,Dated: 10 / 20 / 2025 / Bryan Hanks / Bryan HanksRegistration No. 52,991AMENDED CLAIMS STATEMENT UNDER ARTICLE 19(1)Applicant submits that, since support for the proposed Article 19 amendments contained herein can be found variously throughout the specification and original claims, these amendments do not exceed the scope of the original application or otherwise impact the description or drawings.

Images