Documents as infrastructure

Abstract

The described technology pertains to a system and method for managing electronic documents as digital infrastructure, addressing the challenge of maintaining control and security over shared documents. The solution involves embedding an application programming interface (API) within the document, transforming the document into a smart digital object. This API enables remote management, allowing the document's owner to control access, monitor interactions, and enforce security protocols dynamically. The system includes a physical processor and memory to execute these functions, ensuring secure document handling across various platforms. The method includes storing data within the document, receiving access requests, determining authorization, and controlling access, all executed by the document itself. This approach enhances document security and control, providing a robust solution for modern digital environments.

Description

IN THE UNITED STATES PATENT AND TRADEMARK OFFICE APPLICATION FOR LETTERS PATENT DOCUMENTS AS INFRASTRUCTURE INVENTORS: Matan Gavish Gil Asher Prepared By: GREENBERG TRAURIG, LLP Attorney Docket No.: 226148.012001 / PCTDOCUMENTS AS INFRASTRUCTURE PRIORITY 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. Provisional Patent Application 63 / 680,061 filed August 6, 2024, U.S. Provisional Patent Application 63 / 685,234 filed August 20, 2024, U.S. Provisional Patent Application 63 / 693,173 filed September 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 Patent Application 63 / 714,009 filed October 30, 2024, U.S. Provisional Patent Application 63 / 723,471 filed November 21, 2024, U.S. Provisional Patent Application 63 / 736,568, filed December 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 Patent Application 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 today’s digital landscape, electronic documents are prevalent, serving as the main medium for storing and sharing information across various platforms. These documents, often in formats such as PDF, Word, or Excel, are typically stored on local, shared, or cloud-based systems. However, once shared, the control over these documents is Attorney Docket No.: 226148.012001 / PCTsignificantly diminished, leading to potential security risks and unauthorized dissemination. This loss of control presents a significant issue for individuals and organizations alike, as it can result in the exposure of sensitive information and a reliance on legal systems to enforce compliance with document handling policies.

[0003] Current methods for managing electronic documents often rely on a combination of policies, procedures, and legal agreements to maintain a semblance of control. However, these approaches have inherent limitations, as they depend on the goodwill and ethical behavior of individuals, which cannot be guaranteed at all times. Furthermore, the proliferation of electronic documents across various devices and platforms exacerbates the challenge of maintaining control, as traditional systems lack the capability to effectively track and manage document access and distribution. This creates a pressing need for a more robust and reliable solution that ensures document security and control, even after documents have been shared beyond the original digital perimeter. SUMMARY

[0004] As will be described in greater detail below, the present disclosure describes a system, method, and computer-readable medium for managing electronic documents as smart digital objects, utilizing an embedded API to enable remote control, secure access, and dynamic interaction across various platforms.

[0005] In some aspects, the techniques described herein relate to a computer- implemented method performed by an electronic document provisioned as digital infrastructure, the computer-implemented method including: receiving, at the electronic document, a request from an entity to access data associated with the electronic document; determining, via execution of the electronic document, whether the entity is allowed to Attorney Docket No.: 226148.012001 / PCTaccess the data; and controlling, via execution of the electronic document, an ability of the entity to access the data.

[0006] In some aspects, the techniques described herein relate to a system including: at least one physical processor; physical memory including computer-executable instructions that, when executed by the physical processor, cause the physical processor to: store, via execution of an electronic document on a computing device, data of the electronic document; receive, at the electronic document, a request from an entity to access the electronic document; determine, via execution of the electronic document, whether the entity is allowed to access the data of the electronic document; and control, via execution of the electronic document, access to the data within of the electronic document.

[0007] In some aspects, the techniques described herein relate to a non-transitory computer-readable medium including one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to: store, via execution of an electronic document on a computing device, data within the electronic document; receive, at the electronic document, a request from an entity to access the electronic document; determine, via execution of the electronic document, whether the entity is allowed to access the electronic document; and control, via execution of the electronic document, access to the data within the electronic document.

[0008] In some aspects, the techniques described herein relate to a computer- implemented method performed by an electronic document provisioned as digital infrastructure, the computer-implemented method including: receiving, at the electronic document, a request from an entity to interact with the electronic document. determining, via execution of the electronic document, interaction permissions of the entity; and Attorney Docket No.: 226148.012001 / PCTcontrolling, via execution of the electronic document, the interaction based on the interaction permissions.

[0009] These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims. Features from any of the embodiments described herein may be used in combination with one another in accordance with the general principles described herein. These and other embodiments, features, and advantages will be more fully understood upon reading the following detailed description in conjunction with the accompanying drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings illustrate a 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 disclosure.

[0011] FIG. 1 is a block diagram illustrating the architecture of a document provisioned as digital infrastructure.

[0012] FIG. 2 is a system diagram illustrating the architecture for managing electronic documents across a network.

[0013] FIG.3 illustrates a flow chart diagram of a method for managing access to an electronic document provisioned as digital infrastructure.

[0014] FIG.4 illustrates a flow chart diagram of a method for managing access to an electronic document.

[0015] 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 Attorney Docket No.: 226148.012001 / PCTembodiments 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

[0016] The Portable Digital Format (PDF) was originally designed to address the problem of uniform document appearance across different screens and printers. While this innovation solved a significant issue at the time, it fundamentally lacks the features necessary for a connected, digital-first world. The PDF predates the internet and was created for human consumption rather than machine interaction. It does not support essential functionalities such as document confidentiality, access control, tracking, versioning, interactivity, or integration with broader systems of record. Additionally, the PDF is incapable of representing document context, such as identities, workflows, or relationships between documents. As a result, it functions as a static, human-centric file format that proliferates disconnected copies, making it unsuitable for modern digital ecosystems, impeding the efficiency and effectiveness of computer device hardware and networking systems.

[0017] The limitations of the PDF extend to its inability to support dynamic user experiences or machine-readable interactions. Unlike modern software interfaces, PDF readers lack interactivity and responsiveness, offering no buttons or APIs for users or machines to engage with the document beyond its visual representation. This static nature prevents users from performing tasks such as auditing, signing, or securely sharing documents. Furthermore, the PDF's reliance on local file storage leads to fragmentation, as Attorney Docket No.: 226148.012001 / PCTmultiple independent copies of the same document are created during exchanges, eroding the concept of a single, authoritative version of the document.

[0018] To address these shortcomings, the design of digital documents can be reimagined from first principles, focusing on interactivity, machine-readability, and integration into connected systems. A modern digital document should be uniquely addressable, immutable, and capable of supporting dynamic workflows and applications. It should enable seamless interaction between users and machines, while maintaining trustworthiness, discrete versions, and ownership. By leveraging advancements in artificial intelligence and interconnected systems, digital documents can evolve into permanent, machine-readable knowledge assets that align with the original vision of the web as an interconnected and reliable repository of information.

[0019] This disclosure presents methods and systems for maintaining security, control, and ownership of electronic documents. For example, one approach provides a computer-implemented method of controlling an electronic document through an embedded software chip, which allows the document’s controller, such as the author or owner, to remotely manage the document and any copies. By employing this remote-control capability, the controller can enable or disable another party’s ability to interact with the electronic document, thereby maintaining control even when the document is no longer in direct custody. This approach ensures that document security and control are preserved, regardless of the document's location or the number of copies that exist.

[0020] The embedded software chip can function as an API (Application Programming Interface) or other computer-executable code that is integrated directly into the document, transforming it into a smart digital object. This API serves as a conduit for Attorney Docket No.: 226148.012001 / PCTinteraction between the document and external systems or users, enabling a range of functionalities that extend beyond traditional document capabilities.

[0021] As one example, the embedded software chip provides a standardized interface through which users and systems can interact with the document. This interface allows for controlled access, modification, and management of the document's content, ensuring that interactions are governed by predefined rules and permissions.

[0022] Furthermore, as an API, the embedded software chip facilitates remote management of the document. The document’s owner or controller can use the API to monitor access, track changes, and enforce security protocols, even when the document is distributed across different platforms or devices.

[0023] The API also enables dynamic content rendering and real-time updates within the document. This means that the document can display the most current information and adapt its content based on user interactions or external data inputs, all managed through the API.

[0024] The API also allows the document to integrate seamlessly with other software systems, such as cloud services or enterprise applications. This integration supports enhanced functionalities like automated workflows, data synchronization, and collaborative features, all orchestrated through the API.

[0025] The API embedded within the document provides robust security features, such as encryption and access control, ensuring that only authorized users can interact with the document. This level of control is maintained through the API, which acts as a gatekeeper for all document interactions. Attorney Docket No.: 226148.012001 / PCT

[0026] By embedding the software chip as an API within the document, the embodiments of this disclosure transform the document into an active, controllable entity that can interact with its environment in a secure and managed manner. This approach significantly enhances the document’s utility and security, providing a comprehensive solution for modern document management challenges by providing a document as infrastructure.

[0027] When a document is described as infrastructure, it signifies a fundamental shift in how documents are perceived and utilized within digital ecosystems. Unlike traditional documents, which are static files stored and accessed in isolation, a document as infrastructure is integrated into a broader digital framework, functioning as a dynamic and interactive entity. This transformation is achieved through the embedding of an API or other computer-executable code within the document, enabling it to interact seamlessly with other systems, applications, and users. As infrastructure, the document becomes a central component of a digital ecosystem, supporting automated workflows, data synchronization, and collaborative features. It is no longer confined to a single location or device but can be accessed and managed across various platforms, ensuring consistency and reliability.

[0028] This approach enhances the document’s utility by enabling real-time updates, secure access control, and remote management, making it an active participant in digital processes rather than a passive repository of information. By serving as infrastructure, the document supports the development of new products and services that leverage its capabilities, ultimately providing a robust foundation for modern digital environments.

[0029] As noted, the present disclosure is directed to electronic documents. In general, the term “electronic document” refers to any form of document that is created, Attorney Docket No.: 226148.012001 / PCTstored, accessed, or transmitted in a digital format using computing devices or digital systems. Unlike physical documents, which exist in tangible form and are typically composed of paper or other physical materials, electronic documents are intangible and exist as digital files represented by binary data. These files can be stored on local drives, shared networks, cloud- based systems, or other digital storage mediums. Common formats for electronic documents include PDF, Word, Excel, HTML, and XML, among others.

[0030] The following will provide, with reference to FIGS. 1-4, detailed descriptions of systems and methods for managing electronic documents as digital infrastructure. FIG. 1 illustrates the architecture of a document provisioned as digital infrastructure, highlighting the integration of various interfaces and components. FIG. 2 presents the system architecture for managing electronic documents across a network, showcasing the interaction between servers, networks, and computing devices. FIG.3 depicts a flowchart of a method for managing access to an electronic document, detailing the steps involved in storing, accessing, and controlling data within the document. FIG. 4 further elaborates on the method for managing access, illustrating the decision-making process for authorizing user access and ensuring document security.

[0031] Turning to FIG. 1, the document 100 serves as the central element of the described system, acting as a digital infrastructure that integrates various interfaces and components to manage electronic documents effectively. The document 100 is provisioned to store data, control access, and maintain ownership and trust through embedded interfaces and components. The document 100 is designed to function as a smart digital object, capable of interacting with the surrounding environment and providing a secure and controlled document management system. Attorney Docket No.: 226148.012001 / PCT

[0032] The instructions 102 within the document 100 play a significant role in the operation of the document 100, providing the necessary connections between the document 100 and its various functionalities. These instructions 102 include the storage instructions 104, access control instructions 106, ownership instructions 108, and trust instructions 110. Each set of instructions 102 are responsible for a specific aspect of the document 100’s functionality, ensuring that data is stored securely, access is controlled, ownership is maintained, and trust is established.

[0033] The storage instructions 104 are responsible for managing the storage of data within the document 100. The storage instructions 104 interact with the data storage 120 to ensure that data 122 is stored efficiently and securely. The storage instructions 104 facilitate the retrieval and updating of data 122, allowing the document 100 to maintain a single true copy and ensuring consistency across all accessed versions. This storage instructions 104 plays an important role in the document’s ability to provide dynamic content rendering and real-time updates.

[0034] The access control instructions 106 manage who can access the data within the document 100. These instructions determine whether an entity is allowed to access the document 100 and controls access based on predefined rules and permissions. By ensuring that only authorized users can interact with the document 100, the instructions 106 provide a secure environment for document management. The access control instructions 106 are essential for the document's 100 capability to enable secure sharing and collaboration among multiple users with varying access levels.

[0035] The ownership instructions 108 are designed to maintain control over the document 100, even when shared with third parties. These instructions enable the Attorney Docket No.: 226148.012001 / PCTdocument’s owner to manage ownership rights and control the distribution of the document 100. This feature is important for ensuring that the document’s ownership is preserved and that the document 100 can be linked to a specific context in which the document 100 was shared. The ownership instructions 108 provide the document’s owner with the ability to revoke access or grant temporary access as needed.

[0036] The trust instructions 110 are responsible for establishing and maintaining trust in the document 100. The trust instructions 110 provide mechanisms for verifying the authenticity and integrity of the document 100, ensuring that users can rely on the document’s content. This interface may include features such as encryption and access control, which help to prevent unauthorized access and ensure that the document 100 is handled securely. The trust instructions 110 plays a significant role in providing users with confidence in the document’s authenticity and in enhancing information security.

[0037] The data storage 120 supports document 100, offering a secure location for storing data 122. The data storage 120 operates in conjunction with the storage instructions 104 to ensure that data is stored in an efficient and secure manner. The design of the data storage 120 maintains a single true copy of the document 100, ensuring consistency across all accessed versions. Data storage for self-determinative documents can be implemented in various configurations, including a single cloud-based server, distributed across multiple servers or devices, or within an on-premises system, each offering distinct advantages based on scalability, security, accessibility, and compliance needs. In a single cloud-based server setup, the data storage is hosted on centralized platforms like Amazon Web Services (AWS) or Microsoft Azure, ensuring that the document and its associated data are stored securely and accessible globally. This configuration is ideal for organizations prioritizing scalability and Attorney Docket No.: 226148.012001 / PCTdisaster recovery, as it allows employees across regions to access the most up-to-date version of the document without duplicating or fragmenting the data.

[0038] Alternatively, a distributed storage model spans multiple servers or devices, creating a decentralized system that ensures redundancy, fault tolerance, and localized access. For example, financial institutions may store documents across geographically dispersed servers to minimize latency and ensure high availability, often leveraging technologies like blockchain to maintain tamper-proof authenticity and traceability. On-premises systems, where data storage is hosted entirely within an organization’s local infrastructure, can provide maximum control and security, making them ideal for handling sensitive or regulated data, such as patient medical records or classified government documents. This setup ensures compliance with privacy regulations and eliminates reliance on external internet connectivity, allowing uninterrupted access even in environments with limited network availability.

[0039] A hybrid storage model combines cloud-based and on-premises systems, enabling organizations to store sensitive data locally while leveraging cloud platforms for less critical data or global access. For instance, a government agency might store classified documents on-premises while using cloud storage for public-facing reports, balancing scalability with compliance. Regardless of the configuration, the design of the data storage ensures that the document maintains a single true copy, preventing duplication or fragmentation of data. Synchronization protocols, cryptographic techniques, and metadata tracking ensure consistency across all accessed versions, while security measures like encryption and access controls protect the data from unauthorized access or tampering. By leveraging these flexible storage options, organizations can confidently manage their self- Attorney Docket No.: 226148.012001 / PCTdeterminative documents in a manner that aligns with their operational, security, and compliance requirements.

[0040] The data 122 stored within the data storage 120 represents the content of the document 100. The data 122 is managed by the storage instructions 104 and is subject to the access control instructions 106, ownership instructions 108, and trust instructions 110. The data 122 serves as a central component of the document’s functionality, providing the information that users and other entities interact with and manage through the document’s application programming interface 140.

[0041] The data of a self-determinative document can include two distinct components: content 124 and metadata 126, each serving a unique purpose in the 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.

[0042] 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 Attorney Docket No.: 226148.012001 / PCTlifecycle 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.

[0043] 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 serving a 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.

[0044] 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 can 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.

[0045] Consider a scenario involving a contract document. The process metadata for this document might include a log of when the contract was drafted, when it was sent to Attorney Docket No.: 226148.012001 / PCTa client for review, and when it was signed by both parties. It might also record any amendments made to the contract, along with the identities of the individuals who made those changes. This metadata provides a transparent and unambiguous record of the document’s lifecycle, which is invaluable for compliance, auditing, and dispute resolution.

[0046] Another example is a receipt document. The process metadata for a receipt might include information about when the receipt was issued, when it was submitted for reimbursement, and when it was approved by the finance department. This metadata ensures that the document’s history is traceable and verifiable, reducing the risk of errors or fraud.

[0047] 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.

[0048] 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 "Finance Documents" 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.

[0049] An example provided in the discussion involves an NDA document. The semantic metadata for this document might include fields specifying the parties involved, the Attorney Docket No.: 226148.012001 / PCTdate the agreement was signed, and the expiration date of the confidentiality obligations. This metadata not only categorizes the document but also enriches it with contextual information that is directly related to its purpose and use.

[0050] 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.

[0051] For example, a marketing presentation might include content-related metadata that identifies the title slide, the key points in each section, and the images used to illustrate the presentation. This metadata allows the document to be rendered dynamically based on the user’s device or context. On a mobile phone, the presentation might be displayed as a series of concise bullet points, while on a desktop, it might be shown in its full layout with detailed graphics.

[0052] Another example is a financial report. The content-related metadata for this document might include tags for each section, such as "Executive Summary," "Revenue Analysis," and "Expense Breakdown." These tags enable users to navigate the document efficiently and allow the system to extract specific sections for use in other workflows or applications.

[0053] One aspect of metadata in documents that are digital infrastructure is its bidirectional relationship with the document itself. Changes to the metadata can directly modify the document, and updates to the document can automatically update the metadata. Attorney Docket No.: 226148.012001 / PCTThis dynamic interaction ensures that the document and its metadata remain consistent and synchronized.

[0054] For example, if the due date for a receipt is updated in the metadata, the document itself might display a notification or highlight the updated due date. Conversely, if a user adds a comment to a document, the metadata might be updated to include information about the comment, such as the timestamp and the identity of the commenter. This bidirectional relationship enhances the document’s utility and ensures that all changes are accurately reflected across its metadata and content.

[0055] The discussion provided several compelling examples of how metadata can be used to enrich and enhance documents. Metadata can specify fields that need to be filled within a document, such as names, dates, and signatures. For example, an NDA document might include metadata fields for the names of the parties involved and the date of signing. These fields can be dynamically updated based on user input, ensuring that the document remains accurate and complete. Metadata can record actions that need to be performed with a document, such as submitting it for approval or attaching supporting documents. For instance, a receipt might include metadata specifying that it needs to be submitted to the finance department by a certain date.

[0056] Metadata enables documents to be fully queryable, allowing users to retrieve information efficiently. For example, a user might query the system to find all receipts above $10 or all contracts signed in the last year. This capability transforms documents into active, searchable entities. Metadata from multiple documents can be aggregated into a centralized database, enabling cross-document queries and analysis. For example, an Attorney Docket No.: 226148.012001 / PCTenterprise might use this data layer to analyze spending patterns across all receipts or identify trends in contract negotiations.

[0057] Metadata can be the backbone of smart documents, providing the structure and intelligence needed to transform them from static files into dynamic, interactive entities. By capturing process history, semantic characteristics, and content structure, metadata enables advanced computational interactions, efficient organization, and seamless workflows. The examples provided illustrate the versatility and power of metadata, highlighting its role in creating a new paradigm for digital documents.

[0058] The physical processor 130 is responsible for executing the instructions necessary for the operation of the document 100. The physical processor 130 is used by application programming interface 140 to execute the document's operations and manage the interactions of the document 100 with users and external systems.

[0059] The physical processor 130 in a self-determinative document system can take various forms, depending on the specific requirements of the deployment environment and the complexity of the operations performed by the document. In its simplest configuration, the physical processor 130 can be a single processor, such as a standard Central Processing Unit (CPU), capable of executing the embedded instructions within the document to perform tasks like tracking authenticity, responding to validation requests, and managing access control. Alternatively, the physical processor 130 can consist of multiple processors working in parallel to handle more demanding workloads, such as processing large volumes of data or supporting simultaneous interactions with multiple users. In modern computing systems, the processor may also feature multiple cores within a single chip, enabling efficient multitasking and parallel execution of the document’s embedded instructions. Attorney Docket No.: 226148.012001 / PCT

[0060] For distributed computing environments, the physical processor 130 can represent a network of interconnected processors across multiple devices or servers, collectively executing the document’s operations. For example, in a cloud-based deployment, the processor may leverage virtualized computing resources across a distributed infrastructure to ensure scalability and high availability. Other examples of processing hardware include Field-Programmable Gate Arrays (FPGAs), which can be configured to execute specific tasks related to document authentication, and Graphics Processing Units (GPUs), which are optimized for parallel processing and can be used for computationally intensive operations, such as cryptographic validation or real-time analytics. Additionally, Application-Specific Integrated Circuits (ASICs) can be employed for specialized tasks, such as encryption or blockchain integration, providing high efficiency and performance for specific use cases. By leveraging these diverse processing hardware configurations, the physical processor 130 ensures that the self-determinative document system can operate effectively across a wide range of environments, from local devices to distributed cloud networks.

[0061] The application programming interface (API) 140 provides a standardized interface for interaction between the document 100 and external systems or users. The API 140 enables a range of functionalities, including controlled access, modification, and management of the document's 100 content. It serves as a conduit for interaction, allowing the document 100 to integrate seamlessly with other software systems and support enhanced functionalities like automated workflows and data synchronization. The integration of API 140 transforms the document 100 into an active, controllable entity that can interact with its environment in a secure and managed manner. Attorney Docket No.: 226148.012001 / PCT

[0062] In the context of embodiments of this disclosure, the API embedded within the document serves as a component that transforms the document into a smart digital object. This API is not merely a set of protocols for building and interacting with software applications; it is an integral part of the document itself, enabling a wide array of functionalities that enhance the document’s utility, security, and control.

[0063] The API provides a standardized interface that enables the document to interact seamlessly with external systems, applications, and users. This integration enables the document to function as part of a larger digital ecosystem, where it can communicate and exchange data with other software systems, such as cloud services, enterprise applications, and third-party tools. Through the API, the document’s owner or controller can remotely manage the document's access and usage. This includes monitoring who accesses the document, tracking changes, and enforcing security protocols. The API allows for real-time updates and modifications, ensuring that the document remains current and relevant, regardless of its location or the number of copies in existence.

[0064] The API can equipped with robust security features, such as encryption and access control mechanisms, to protect the document from unauthorized access and tampering. It acts as a gatekeeper, ensuring that only authorized users can interact with the document. This level of security is essential for maintaining the integrity and confidentiality of the document's content. Additionally, the API enables dynamic content rendering, allowing the document to display the most current information and adapt its content based on user interactions or external data inputs. This capability is particularly useful for documents that require real-time updates, such as financial reports, legal documents, or collaborative projects. Attorney Docket No.: 226148.012001 / PCT

[0065] By embedding the API within the document, embodiments of this disclosure support enhanced functionalities like automated workflows, data synchronization, and collaborative features. The API allows the document to function as an interactive and responsive entity that can interact with and respond to its environment, users, and other systems in a secure and managed manner. Furthermore, the API ensures that the document is device and platform agnostic, meaning it can be accessed and interacted with from various types of devices and operating systems without compatibility issues. This flexibility helps ensure that the document can be used effectively in diverse digital environments.

[0066] In some examples, the API serves as an immutable interface, providing a consistent and reliable framework for accessing and interacting with the document. This immutability ensures that the document’s structure and access protocols remain stable over time, enhancing trust and reliability for users and applications interacting with the document. In summary, the API embedded within the document is a transformative component that elevates the document from a static file to a dynamic, interactive digital object. It provides the necessary infrastructure for secure, controlled, and flexible document management, addressing the challenges of traditional document handling and offering a comprehensive solution for modern digital environments. In other examples, some aspects of the API may be updated or revised over time without impacting accessibility of the document or the immutability of the content of the document.

[0067] The system 200 can represent an architecture designed to facilitate the secure and controlled management of electronic documents. At the center of this system is the document 100, which is stored on a server 206. The server 206 can act as a centralized repository, ensuring that the document 100 is accessible to authorized users while Attorney Docket No.: 226148.012001 / PCTmaintaining the document's integrity and security. The server 206 is connected to a network 204, which serves as the communication backbone, enabling data exchange between the server 206 and various computing devices 202. This network 204 can be implemented using various technologies, such as the internet, intranet, or other suitable communication protocols, to ensure reliable and secure data transmission.

[0068] The computing device 202 provides the interface through which users interact with the document 100. The computing device 202 is equipped with a physical processor 220, which executes the necessary instructions to perform various operations on the document 100. The physical processor 220 is responsible for processing data, executing applications, and managing system resources to ensure smooth and efficient operation. The computing device 202 also includes memory 240, which stores the applications, data, and instructions required for the operation of the system 200. The memory 240 can be implemented using various types of storage media, such as RAM, ROM, flash memory, or other suitable technologies, to provide fast and reliable data access.

[0069] The viewer 260 is an important component of the computing device 202, providing a user interface for accessing and interacting with the document 100. The viewer 260 is designed to render the document 100 in a user-friendly format, allowing users to view, edit, and manage the document's content. The viewer 260 can be implemented as a standalone application or as part of a web-based interface, providing flexibility in how users access the document 100. The viewer 260 also supports various functionalities, such as zooming, scrolling, and searching, to enhance the user experience and facilitate efficient document management. Attorney Docket No.: 226148.012001 / PCT

[0070] The network 204 enables seamless communication between the server 206 and the computing device 202. The network 204 ensures that data is transmitted securely and efficiently, using encryption and other security measures to protect the integrity and confidentiality of the document 100. The network 204 also supports various communication protocols, such as TCP / IP, HTTP, and HTTPS, to ensure compatibility with different devices and platforms. By facilitating reliable and secure data exchange, the network 204 enables users to access the document 100 from any location, at any time, while maintaining the necessary security and control measures.

[0071] In some examples, the viewer 260 serves as the primary user interface for accessing and interacting with the document 100. It is designed to render the document in a user-friendly format, allowing users to view, edit, and manage the document's content seamlessly. As noted, the viewer 260 can be implemented as a standalone application or integrated into a web-based interface, providing flexibility in how users access the document. This adaptability ensures that the viewer can function effectively across various platforms and devices, maintaining a consistent user experience. The viewer is equipped to handle dynamic content rendering, allowing real-time updates and modifications to be displayed as they occur. This feature is particularly beneficial for collaborative environments where multiple users may be interacting with the document simultaneously. The viewer 260 also incorporates security measures, such as authentication protocols, to ensure that only authorized users can access and modify the document. By providing a comprehensive and secure interface, the viewer 260 enables users to engage with the document in a controlled and efficient manner.

[0072] In some examples, the viewer is designed to provide an experience beyond a fixed layout, allowing for dynamic interaction with the document's content. A document as Attorney Docket No.: 226148.012001 / PCTinfrastructure enables dynamic layout of content and data through several features. It can integrate real-time data from external sources, such as databases or APIs, allowing the document to update its content dynamically. For example, a financial report document can automatically refresh stock prices or currency exchange rates, ensuring users always have access to the most current information. Additionally, the document can adjust its layout and content based on the user's role or preferences, providing a personalized experience. For instance, a project management document might display different sections or levels of detail depending on whether the viewer is a project manager, team member, or stakeholder. Interactive elements, such as forms, charts, or graphs, can be included, and can allow users to manipulate data directly within the document. This feature enables users to explore data visually and interactively, such as adjusting parameters in a sales forecast to see potential outcomes. The document can also show or hide content based on specific conditions or triggers, such as revealing additional clauses in a legal document only when certain criteria are met.

[0073] Furthermore, the document supports real-time collaboration, allowing multiple users to access and interact with the document simultaneously, with changes to metadata made by one user immediately reflected for all other users. Adaptive layouts ensure the document adjusts automatically to fit different screen sizes and orientations, providing optimal readability and usability on various devices. Additionally, the document can host embedded applications or widgets, such as calculators or data analysis tools, enabling users to perform complex tasks without leaving the document. By leveraging these capabilities, a document as infrastructure transforms from a static file into a dynamic, interactive platform that enhances user engagement and productivity. Attorney Docket No.: 226148.012001 / PCT

[0074] In some aspects, the viewer has the ability to run applications within the document itself, providing additional functionality and user interaction. This capability allows the viewer to support AI features, enhancing document interaction and analysis. The viewer ensures visual trustworthiness, giving users confidence in the document's authenticity and integrity.

[0075] The viewer can also play a role in information security by making it more difficult to scrape or perform OCR (Optical Character Recognition) on the document's content. This security feature helps protect sensitive information from unauthorized access or extraction. Additionally, the viewer can be embedded in other systems, such as within a frame or user interface component, to provide seamless integration with existing workflows and applications.

[0076] Furthermore, the viewer can enable previews of document content, allowing users to quickly assess information before full access. This feature is particularly useful in environments where users need to evaluate multiple documents efficiently. Overall, the viewer is a strategic component that differentiates the system by providing a comprehensive, secure, and interactive document management experience.

[0077] FIG.3 illustrates a flow diagram of an exemplary method 300 for managing access to an electronic document provisioned as digital infrastructure. This method outlines the steps involved in securely storing, accessing, and controlling data within the document. The process begins with step 310, where the electronic document receives a request from an entity seeking access to data associated with the document. The method then proceeds to step 320, where the electronic document determines, via execution of the document, whether the requesting entity is authorized to access the document. Finally, step 340 involves Attorney Docket No.: 226148.012001 / PCTcontrolling access to the data associated with the document, ensuring that only authorized entities can interact with the document's content.

[0078] As an initial point, data may be associated with an electronic document in a variety of ways. Data can be associated with an electronic document in various ways to enhance its functionality, accessibility, and / or security. For example, data can be stored directly within the document, such as embedded metadata, semantic tags, or encrypted content. This data may be stored on the same device of set of devices as the document. Additionally or alternatively, data can be accessible by the document through various sources, such as linked databases or cloud storage systems, allowing the document to dynamically retrieve and update information in real-time, such as stock prices or user interactions. Additionally, data can be associated with the document in other suitable ways, such as through audit trails, access logs, or related documents stored in a centralized system, providing a comprehensive view of the document’s history and interactions. Indeed, in some examples, the term “electronic document” refers to any data, metadata, audit information, or intelligence that pertain to the electronic document. In other words, an electronic document may be made up of its data, metadata, intelligence, and / or other information. The data, metadata, intelligence, and / or other information of a document may be stored in any suitable manner (e.g., each of these items may be stored in a single database or device, distributed across multiple database or devices, distributed across networked devices, etc.).

[0079] Data may be store within or otherwise associated with an electronic document through execution of the electronic document on a computing device, a process that enables the document’s function as a smart digital object. In some aspects, this process is not merely about saving data in a conventional sense but involves a sophisticated Attorney Docket No.: 226148.012001 / PCTmechanism that ensures the document acts as a dynamic and interactive entity. As explained above, in some examples, the document is provisioned to maintain a single true copy, which facilitates ensuring consistency and integrity across all accessed versions. This single true copy can be stored in a secure environment, leveraging cloud-based infrastructure to facilitate accessibility and scalability.

[0080] Storing data within a document through execution of the document refers to the process where the document itself, as an active digital entity, manages and updates its own data content dynamically. This concept transforms the document from a static file into an interactive and intelligent object capable of executing operations to modify its content. In some examples this involves including executable code or an API as part of the document, which allows it to perform actions such as data retrieval, processing, and storage autonomously. For example, a document can be programmed to fetch the latest data from a remote server or database whenever it is opened, updating it with real-time information such as current stock prices or weather forecasts. Another example is a collaborative document that tracks interactions of different users, storing them within the document itself to maintain a comprehensive version audit trail. This capability is particularly useful in environments where documents need to reflect the most current data or where user interactions need to be logged and managed directly within the document. By executing these operations internally, the document can ensure data consistency and integrity.

[0081] Returning to FIG.3, step 310 involves receiving a request from an entity to access the document, which is a phase in a document’s lifecycle that ensures secure and controlled interaction with its content. This step may be programmed to handle access requests in a manner that prioritizes security, flexibility, and user experience. Various types Attorney Docket No.: 226148.012001 / PCTof entities may initiate such requests. These entities can include individual users, such as employees, contractors, or collaborators, who need to access the document for work-related purposes. They may request access to view, edit, or comment on the document based on their roles and permissions. Automated systems, such as software applications or services, may also require access to the document for processing or integration purposes. For example, a data analysis tool can request access to extract information from the document for reporting or analytics.

[0082] External partners, including business partners, clients, or vendors, may need access to the document as part of a collaborative project or transaction, with limited or conditional access based on agreements or contracts. Regulatory bodies, such as government agencies or compliance auditors, may request access to the document for verification or auditing purposes, typically governed by legal or regulatory requirements. Third-party applications that integrate with the document’s API to provide additional functionality, such as document signing, workflow automation, or content management, may request access to perform specific tasks or operations. Additionally, cloud services that host or manage the document as part of a broader digital ecosystem may request access to synchronize data, perform backups, or facilitate collaboration across different users and devices. Each of these entities may have different levels of access and permissions, which are managed and controlled through the document’s API to ensure security and compliance with organizational policies.

[0083] The process of receiving a request can involve one or more of several layers of security and verification. For example, the electronic document can employ multi-factor authentication to verify the identity of the requesting entity, ensuring that only authorized Attorney Docket No.: 226148.012001 / PCTusers can proceed. This authentication process may include password verification, biometric checks, or other security measures tailored to the document's context and the user's role.

[0084] Additionally, the document’s API can support role-based access control, allowing different levels of access based on the entity’s permissions. This means that the document can provide personalized access experiences, where users with different roles or security clearances see only the parts of the document they are authorized to view. This capability is particularly important in environments where sensitive information must be protected from unauthorized access.

[0085] The document can also maintain a real-time access control list, dynamically updated based on user activity and permissions. This list ensures that access decisions are made with the most current information, enhancing the document’s security and control capabilities. By managing access requests in this detailed and secure manner, step 320 plays a significant role in maintaining the integrity and confidentiality of the document’s content, aligning with the overall goal of providing a robust and reliable document management solution.

[0086] Step 320 involves determining, via execution of the document, whether the requesting entity is authorized to access the document. This step ensures that only authorized users can interact with the document’s content, thereby maintaining the document's security and integrity. The document, functioning as a smart digital object, utilizes its embedded software chip to execute this determination. In one example, a software chip of the document may facilitate seamless interaction with external systems and databases to verify the credentials and permissions of the requesting entity. This verification process may Attorney Docket No.: 226148.012001 / PCTinvolve cross-referencing the entity’s credentials with a centralized authentication server or database, ensuring that the entity’s identity and access rights are valid and up-to-date.

[0087] In some examples, determining whether an entity (such as a user or system) is authorized to interact with an electronic document is performed by evaluating the entity’s permissions against predefined access criteria embedded within the document itself. The electronic document can contain criteria that are embedded rules or conditions that define who can access specific sections, features, or functionalities based on factors such as user roles, security clearances, or contextual requirements. For example, the document may include criteria specifying that only users with a certain clearance level can view sensitive sections, or that access is contingent upon signing a non-disclosure agreement (NDA). When an entity attempts to interact with the document, the embedded intelligence within the document evaluates the entity's credentials, role, or other attributes against these predefined criteria to determine whether access should be granted, restricted, or denied. This ensures that the document autonomously enforces access control, maintaining security and compliance while providing a tailored user experience.

[0088] Step 330 involves controlling access to the data within the document, ensuring that only authorized entities can interact with the document’s content. This step maintains the document’s security and integrity, as well as for providing a controlled and managed environment for document interaction. Based on the discussion with the inventor, this step is designed to leverage advanced security features and real-time management capabilities to enforce access control effectively.

[0089] Once the determination in step 320 confirms that an entity is authorized to access the document, step 330 ensures that the interaction with the document is Attorney Docket No.: 226148.012001 / PCTconducted within the predefined security and access parameters. The embedded software chip and / or document API enable this process by acting as a gatekeeper that manages and monitors all interactions with the document. This includes enforcing access permissions, tracking user activities, and logging interactions for audit and compliance purposes.

[0090] A document’s API support dynamic access control, allowing the document owner or controller to modify access permissions in real-time. This flexibility enables adapting to changing security requirements or organizational policies. For instance, access can be temporarily granted or revoked based on specific conditions, such as the completion of a project or the expiration of a contract. This capability ensures that access is always aligned with the current context and needs of the organization.

[0091] Additionally, the document’s API or integrated chip facilitates secure sharing and collaboration by enabling controlled access to different sections of the document based on user roles and permissions. This means that users can collaborate on the document without compromising sensitive information, as access is restricted to only the relevant parts of the document. The API also supports encryption and other security measures to protect the document's content from unauthorized access or tampering.

[0092] When a request to access a document is denied, the document handles the situation by implementing several measures to ensure security and provide guidance to the requesting entity. For example, the API can display a notification or entry page to the user, indicating that access has been denied. This notification may include a message explaining that the user does not have the necessary permissions to view the document, along with instructions on how to request access or contact the document owner or administrator for further assistance. Additionally, the API can log the denied access attempt, recording details Attorney Docket No.: 226148.012001 / PCTsuch as the time of the request, the identity of the requesting entity, and the reason for the denial. This logging can maintain an audit trail and can be used for security analysis or compliance purposes. The API may also trigger an alert to the document owner or administrator, notifying them of the denied access attempt. This alert can help in identifying potential security threats or unauthorized access attempts, allowing for timely intervention.

[0093] In some cases, the API may offer alternative actions to the user, such as providing access to a limited version of the document or redirecting the user to related resources that they are authorized to access. This approach ensures that the user experience is not entirely disrupted while maintaining the security and integrity of the document. Overall, the API’s handling of denied access requests is designed to balance security with user guidance, ensuring that unauthorized access is prevented while providing clear communication and options to the requesting entity.

[0094] FIG.4 illustrates a detailed flowchart of a method 400 for managing access to an electronic document provisioned as digital infrastructure. This method outlines the steps involved in securely storing, accessing, and controlling data within the document, ensuring that only authorized users can interact with its content.

[0095] The process begins with step 410, where a user attempts to access the document. This step is crucial as it initiates the interaction between the user and the document, triggering the subsequent security and access control measures. The document, provisioned as a smart digital object, utilizes its embedded software chip (i.e., API) to process this access request, ensuring that the request is handled securely and efficiently.

[0096] Following the access attempt, the method proceeds to step 420, where the system determines whether the user is authorized to access the document. This Attorney Docket No.: 226148.012001 / PCTdetermination is made via execution of the document, via the API, to verify the user’s credentials and permissions. The process may involve cross-referencing the user’s credentials with a centralized authentication server or database, as described above.

[0097] If the user is authorized, the method advances to step 430, where the data of the document is displayed to the user. This step involves rendering the document’s content in a user-friendly format, allowing the authorized user to view, edit, and manage the document’s content as permitted by their access rights. The document facilitates dynamic content rendering and real-time updates, ensuring that the user interacts with the most current and relevant information.

[0098] Conversely, if the user is not authorized, the method moves to step 440, where an entry page is displayed to the user. This entry page serves as a notification that the user does not have the necessary permissions to access the document, providing instructions or contact information for obtaining access if appropriate.

[0099] Overall, FIG. 4 shows a method for managing access to electronic documents, addressing the challenges of unauthorized access and ensuring data integrity through a robust framework of security and control measures.

[0100] Access to an electronic document can involve access to the data of a document as well as access to interact with a document. For example, a self-determining document may perform computer-implemented method where the document, provisioned as digital infrastructure, autonomously determines and controls how an entity interacts with it. This includes not only granting or denying access to the document’s data (e.g., viewing or retrieving content), but also managing sharing and other lifecycle events of a document. Attorney Docket No.: 226148.012001 / PCT

[0101] The ability to control interactions based on permissions allows an electronic document to dynamically tailor its content by selectively rendering sections according to the specific access rights or roles of the user. This ensures that different users can view personalized versions of the same document without being aware of hidden sections or content they are not authorized to access. For example, in a corporate setting, a document containing sensitive information about a merger might display only general updates to junior employees, while executives with higher security clearance can view detailed financial data and strategic plans.

[0102] Similarly, in a subscription-based service, a basic subscriber might only see a summary of a report, while a premium subscriber can access detailed analytics and proprietary insights. In legal contexts, a client might see only the terms relevant to their obligations in a contract, while their attorney can view additional sections containing legal clauses and annotations. Compliance requirements can also be addressed, such as a document shared under an NDA that hides confidential sections until the user electronically signs the agreement, at which point the hidden sections are rendered visible. In educational settings, a student might see only the lessons they are enrolled in, while an instructor can view the full curriculum, including answer keys and grading rubrics. This selective rendering enhances security, compliance, and user experience by ensuring that users only access the information they are authorized to see, while maintaining the integrity of the document as a single authoritative version.

[0103] In some examples, an electronic document includes semantic tags associated with distinct content sections, and determining the interaction permissions further comprises comparing a clearance level of the entity with access requirements linked to the Attorney Docket No.: 226148.012001 / PCTsemantic tag. In such examples, an electronic document may use semantic tags to define and organize distinct content sections, enabling granular control over access permissions. Semantic tags may be metadata embedded within the document that identify and categorize specific sections, such as “Executive Summary,” “Confidential Financial Data,” or “Appendix,” and link them to predefined access requirements based on user roles, security clearances, or contextual conditions.

[0104] When an entity attempts to interact with the document, the system compares the entity’s clearance level or credentials with the access requirements associated with the semantic tags to determine whether the entity is authorized to view or interact with specific sections. For example, in a corporate report, the “Confidential Financial Data” section may be tagged to require executive-level clearance, allowing junior employees to see only general updates while executives access sensitive financial data. Similarly, in a subscription- based market analysis report, basic subscribers might only see a summary, while premium subscribers access the “Detailed Analytics” section tagged for higher-tier access. In legal contexts, a contract can tag “Proprietary Clauses” for attorney-level clearance, ensuring clients see only relevant terms while their attorneys access proprietary clauses. In educational settings, “Instructor Notes” can be tagged for instructor-level access, allowing students to view lessons while instructors access notes and grading rubrics. For classified government documents, sections like “Weapon Specifications” can require top-secret clearance, restricting lower-clearance users to general information. By leveraging semantic tags, the electronic document autonomously enforces access control at a granular level, ensuring users interact only with sections they are authorized to access. This approach enhances security, Attorney Docket No.: 226148.012001 / PCTcompliance, and user experience while maintaining the integrity of the document as a single authoritative version.

[0105] In some examples, a document can manage synchronizing real-time interaction across multiple users based on interaction permissions. This can involve an electronic document dynamically synchronizing real-time interactions made by multiple users to ensure that all authorized users see the most current version of the document based on their interaction permissions. Thus, when a user interacts with the document—a log of the interactions is immediately propagated to all other users who have access to the document, while respecting their individual permissions.

[0106] In some examples, every interaction with an electronic document is logged by the document and recorded in real time, creating a continuously updated audit trail. Each interaction event—such as viewing, editing, sharing, or attempting unauthorized access—is captured and stored as metadata associated with the document. This real-time logging ensures that the document owner or controller has a comprehensive record of all activities related to the document, including details such as the identity of the user, the nature of the interaction, the time and date of the event, and any changes made to the document. For example, in a legal setting, the audit trail can track when a contract was accessed, who made specific edits, and whether any unauthorized access attempts occurred. Similarly, in a corporate environment, the audit trail can provide insights into how sensitive documents are being used, ensuring compliance with internal policies and regulatory requirements. By maintaining a detailed and real-time audit trail, this method enhances transparency, accountability, and security, enabling document owners to monitor usage, detect anomalies, and address potential breaches effectively. Attorney Docket No.: 226148.012001 / PCT

[0107] Some examples involve methods for dynamically altering interactive elements of an electronic document based on the interaction permissions of the entity. For example, an electronic document may control an interaction by enabling or disabling specific in-document applications and features, ensuring that users only access functionalities aligned with their permissions. A user with editing rights might be able to access annotation tools and collaborative features, while a viewer with read-only access would be restricted from making changes. In some examples, dynamic alteration of interactive elements includes enabling or disabling embedded applications within the document itself. For instance, a financial report can include a built-in calculator that is accessible only to users with analytical privileges, while other users might see a simplified version of the report without interactive tools.

[0108] Some examples involve a method where the electronic document autonomously displays a notification to an entity in response to specific events, such as a change in interaction permissions or the detection of an unauthorized access attempt. For instance, if the document owner modifies the entity’s access rights—such as granting additional permissions or revoking existing ones—the document can notify the entity in real- time, ensuring transparency and keeping the user informed of their updated access status. Similarly, if the entity attempts to perform an action outside their authorized permissions, such as accessing a restricted section or sharing the document with an unauthorized party, the document can display a notification alerting the entity that the action is not permitted. This notification may also include guidance, such as instructions to contact the document owner or administrator for further assistance. By providing real-time feedback, this method enhances security, compliance, and user experience, ensuring that entities are aware of their permissions and that unauthorized activities are promptly addressed. Attorney Docket No.: 226148.012001 / PCT

[0109] Some examples involve a method for controlling the interaction with an electronic document where the electronic document limits the number of times it can be shared by an authorized entity or a set of authorized entities. The electronic document can be to enforce a predefined sharing limit, such that once the maximum number of allowed shares is reached, any additional sharing attempts are automatically denied. For example, a document owner may set a limit allowing a user to share the document with three other individuals. Once the user shares the document with three authorized recipients, any further attempts to share the document will result in a notification or denial of access. This mechanism ensures that the document owner retains control over its distribution, preventing unauthorized proliferation or excessive sharing. By embedding this functionality within the document itself, the method enhances security, compliance, and accountability, while enabling controlled and intentional sharing of sensitive information.

[0110] Some examples involve an electronic document enabling ownership transition of itself by transferring its interaction permissions to a designated successor entity upon the occurrence of a predefined condition. The electronic document is provisioned to autonomously manage the transfer of control, ensuring that ownership rights, access permissions, and associated metadata are securely passed to the successor entity. For example, predefined conditions can include the expiration of the original owner’s access rights, a legal transfer of ownership, or the death of the original owner. In such scenarios, the document dynamically updates its permissions and audit logs to reflect the new ownership, ensuring continuity and compliance with the original owner’s intent. This capability is particularly useful in contexts such as estate planning, corporate transitions, or legal agreements, where ownership changes must be handled securely and transparently. By Attorney Docket No.: 226148.012001 / PCTembedding this functionality within the document, the method provides a robust framework for managing ownership transitions while maintaining the integrity and security of the document throughout its lifecycle.

[0111] In some examples, an electronic document may enforce ownership rights over itself by enabling an owner to define, modify, and revoke access permissions at any time, ensuring that the document remains under the exclusive control of its owner regardless of its distribution or storage location. This functionality allows the owner to maintain comprehensive control over the document’s lifecycle, even after it has been shared with third parties or stored on external systems. For example, the owner can grant temporary access to a collaborator, revoke access from a former employee, or modify permissions to restrict certain sections of the document based on changing circumstances. This capability eliminates reliance on external systems or the goodwill of recipients to maintain document security and compliance. By embedding this control directly within the document, the method ensures that ownership rights are preserved, enabling the owner to adapt to evolving security needs and organizational policies while maintaining the integrity and confidentiality of the document.

[0112] Some examples involve an electronic document programmed to control interactions with itself by decrypting encrypted data only after verifying that an entity’s interaction permissions allow access to the encrypted content. The electronic document may be provisioned with encryption to safeguard sensitive information, ensuring that unauthorized entities cannot access or interact with the data. When an entity attempts to access the encrypted data, the system evaluates the entity’s credentials and permissions against predefined access criteria embedded within the document. If the entity is authorized, Attorney Docket No.: 226148.012001 / PCTthe system decrypts the data and renders it accessible, while maintaining the integrity and security of the document. For example, a user with appropriate clearance can be granted access to confidential financial data within a document, while users without the required permissions would be denied access to the encrypted sections. This approach ensures that sensitive information remains protected, even when the document is distributed across various platforms or devices, while providing authorized users with seamless and secure access to the encrypted content.

[0113] Access management to data is facilitated by a self-determinative document, and in some examples is support by an infrastructure (i.e., data) layer. By providing data storage and management, this layer can ensure that all applications within the ecosystem operate from a single, authoritative source of truth. This unified approach not only enhances data consistency and integrity but also streamlines workflows by allowing applications to access and interact with the same dataset in real-time.

[0114] A multi-document data layer aggregates metadata from multiple documents into a centralized and structured database, enabling efficient querying and data retrieval without the need to open individual documents. This approach ensures that all applications within the ecosystem operate from a single, authoritative source of truth, enhancing data consistency and integrity. For example, in an enterprise setting, the multi- document data layer can aggregate metadata from receipts stored within the system, allowing users to query the system with requests such as "What is the total sum of receipts above $10?" or "How many receipts are from Supplier X?" The system can process these queries and retrieve relevant information directly from the aggregated metadata, eliminating the need for exhaustive searches through individual documents. Attorney Docket No.: 226148.012001 / PCT

[0115] Beyond simple queries, this data layer can support advanced analytics and AI-driven insights by analyzing aggregated metadata to identify patterns, detect anomalies, or generate reports. Additionally, it enables cross-document workflows, such as identifying all contracts containing a specific clause and flagging them for review. By providing a unified and centralized approach to data storage and management, the multi-document data layer streamlines workflows, enhances operational efficiency, and ensures real-time access to consistent and reliable information across the ecosystem.

[0116] As noted, self-determinative documents empower document owners or controllers to maintain comprehensive control and visibility over electronic documents throughout their lifecycle, addressing the limitations of traditional document management systems. By embedding intelligence within the document itself, such as an integrated application programming interface (API), these documents transform into active, controllable entities capable of enforcing access permissions, tracking interactions, and maintaining ownership rights. This embedded intelligence enables document owners to remotely manage access, revoke permissions, and monitor usage in real-time, regardless of the document's location or the number of copies distributed. For instance, a document shared under a non- disclosure agreement (NDA) can autonomously enforce compliance by restricting access to authorized users and logging all interactions for audit purposes. Additionally, self- determinative documents provide visibility into their usage by maintaining detailed records of access attempts, modifications, and transfers, ensuring that document owners can trace the document's journey and identify potential security breaches or unauthorized activities. This level of control and visibility eliminates reliance on goodwill or external safeguards, Attorney Docket No.: 226148.012001 / PCTallowing document owners to confidently manage sensitive information while ensuring compliance with organizational policies and legal requirements.

[0117] Self-determinative documents provide virtual custody and remote control by embedding intelligence directly within the document, enabling the sender to maintain control even when the document is no longer in their physical possession. This can be achieved through an integrated application programming interface (API) or embedded software chip that transforms the document into a smart digital object. With this capability, the document owner can remotely manage access permissions, revoke or grant access in real- time, and monitor interactions, regardless of where the document is stored or how many copies exist. For example, if a document is shared with a third party under specific conditions, such as a non-disclosure agreement (NDA), the document can autonomously enforce those conditions by restricting access to authorized users and logging all interactions. Even if the recipient downloads or duplicates the document (if these actions are allowed for the recipient), the embedded intelligence ensures that access remains governed by the original owner’s permissions. This virtual custody eliminates the need to rely on the recipient’s goodwill or external legal enforcement to ensure compliance. Furthermore, the document can dynamically adapt to changing circumstances, such as revoking access if the recipient’s permissions expire or if a security breach is detected. By maintaining control over the document’s lifecycle, self-determinative documents provide a robust solution for managing sensitive information in a secure and reliable manner.

[0118] In one aspect, the concept of “Lose Access" refers to a counterintuitive yet effective implementation where access to a document is universally restricted or terminated, including for the document’s owner, by severing all connections to the secure cloud location Attorney Docket No.: 226148.012001 / PCTwhere the document is stored. This approach ensures that the document’s content becomes permanently inaccessible to any party, preventing retrieval, viewing, or interaction under any circumstances. The embedded intelligence within the document or the managing system initiates this disconnection, severing all links, portals, or identifiers that would otherwise allow access. While the document's metadata, access permissions, and interaction logs may remain intact for audit or compliance purposes, the content itself is irretrievable.

[0119] The Lose Access mechanism can be particularly useful in scenarios involving highly sensitive or classified information, where the risk of unauthorized access must be completely eliminated. For example, a government agency might use this approach to protect national security documents that are no longer needed but cannot risk being accessed by any party. Similarly, organizations may employ Lose Access as part of end-of-lifecycle management for documents that have reached the end of their useful life and must be permanently retired. This ensures that the document cannot be accidentally or maliciously accessed in the future. In certain legal or regulatory contexts, Lose Access may also be required to comply with data destruction mandates, such as ensuring that customer data is permanently inaccessible after a specific retention period. Additionally, in crisis situations, such as a security breach or suspected compromise, Lose Access can act as an emergency measure to immediately terminate all access to a document, preventing further exposure of sensitive information.

[0120] The implications of Lose Access can be significant, as it is an irreversible action that permanently restricts access to the document’s content. This makes it a high- stakes decision that should only be executed with careful consideration and appropriate authorization. While the document’s content becomes inaccessible, the system may retain Attorney Docket No.: 226148.012001 / PCTmetadata and logs to provide a record of the document’s existence and the actions taken to restrict access, ensuring transparency and accountability for compliance purposes. By severing all connections to the secure cloud location, Lose Access can provide the highest level of security, ensuring that the document cannot be retrieved by any means.

[0121] For example, consider a scenario where a company is winding down a highly sensitive project involving proprietary technology. To ensure that no remnants of the project can be accessed or leaked, the company initiates Lose Access for all related documents. The embedded intelligence within the documents severs their connections to the secure cloud location, rendering them permanently inaccessible. The company retains metadata and audit logs to demonstrate compliance with internal policies and regulatory requirements. In summary, Lose Access is a powerful mechanism for ensuring the absolute inaccessibility of a document. By severing all connections to the secure cloud location, this approach provides a robust solution for managing highly sensitive or obsolete documents, offering unparalleled security and compliance capabilities.

[0122] In other examples, self-determinative documents can be particularly valuable in targeted scenarios, such as sharing confidential documents during acquisitions, where maintaining control and security is paramount. For example, when a company shares sensitive information with a potential acquirer, such as trade secrets or financial records, the embedded intelligence within self-determinative documents ensures that access is strictly limited to authorized parties and governed by predefined conditions, such as compliance with a non-disclosure agreement (NDA). Even if the deal does not proceed, the document owner can revoke access in real-time, ensuring that the shared information remains secure and inaccessible to the other party. Attorney Docket No.: 226148.012001 / PCT

[0123] Additionally, self-determinative documents can autonomously enforce document handling policies, such as prohibiting downloads, restricting printing, or logging all interactions for audit purposes. This capability eliminates the need to rely on the goodwill of the recipient or legal enforcement to ensure compliance. Furthermore, these documents can provide detailed visibility into their usage, allowing the owner to track who accessed the document, when, and for how long, as well as identify any unauthorized attempts to interact with the content. By offering granular control and robust security features, self-determinative documents enable organizations to confidently share sensitive information in high-stakes scenarios, such as mergers and acquisitions, while mitigating risks and ensuring compliance with confidentiality agreements.

[0124] Self-determinative documents can be stored in a centralized, searchable cloud database, enabling efficient and secure access to critical information. Unlike traditional document management systems, where files are scattered across local drives or multiple platforms, self-determinative documents are maintained as a single authoritative version. In some examples, each document is uniquely identified and indexed, allowing for precise and comprehensive searches based on metadata, content, or contextual attributes. For example, users can query the database to locate documents associated with specific legal contexts, such as "NDAs signed with Company X in 2025," or search for documents containing particular keywords or phrases. The embedded intelligence within these documents can ensure that search results are accurate and reflect the most current version of the document, eliminating the risk of retrieving outdated or duplicate files. Furthermore, the database supports advanced filtering and categorization, enabling users to refine searches by criteria such as creation date, access history, or user interactions. This streamlined approach not only Attorney Docket No.: 226148.012001 / PCTenhances document retrieval but also facilitates compliance audits, legal discovery, and organizational knowledge management. By leveraging a searchable cloud database, self- determinative documents transform document storage into a dynamic and accessible resource, ensuring that critical information is always available while maintaining robust security and control.

[0125] Self-determinative documents may be securely stored in encrypted form within a centralized system (or distributed system), ensuring protection against unauthorized access and data breaches. Each document can be encrypted using advanced cryptographic algorithms, safeguarding its content both during transmission and while at rest. This encryption ensures that only authorized users with the appropriate decryption credentials can access the document, preserving its confidentiality and integrity. The system also incorporates granular access controls, allowing document owners to define specific permissions for users, such as viewing, editing, or sharing, without compromising the document’s security. Thus, even if a document is intercepted or duplicated, its encrypted state ensures that it remains inaccessible to unauthorized parties. Furthermore, the encryption process is seamlessly integrated into the document’s lifecycle, ensuring that security measures are consistently applied without disrupting user workflows. By combining robust encryption with centralized storage, self-determinative documents provide a secure and reliable solution for managing sensitive information, enabling organizations to maintain control, compliance, and trust in digital environments.

[0126] As noted, self-determinative documents ensure that interactions remain secure and visible only to authorized users by embedding advanced access control mechanisms and encryption directly within the document. These documents autonomously Attorney Docket No.: 226148.012001 / PCTenforce permissions, allowing only users with verified credentials to access, view, or interact with the content. For example, sensitive communications shared under a non-disclosure agreement (NDA) can be restricted to specific parties, with the document logging all interactions for audit purposes. Unauthorized users attempting to access the document are denied entry, and their attempts are recorded for security analysis. Additionally, self- determinative documents can dynamically adjust access based on user roles, ensuring that confidential sections are visible only to those with the appropriate clearance while other users see a tailored version of the document. This granular control significantly reduces or eliminates the risk of accidental exposure or unauthorized sharing. Furthermore, all interactions, such as edits, comments, or transfers, can be tracked and stored as part of the document’s metadata, providing a transparent record of activity. By combining encryption, role-based access, and detailed interaction logs, self-determinative documents create a secure environment for confidential communications, ensuring that sensitive information remains protected and accessible only to those who are authorized.

[0127] The analogy of city infrastructure provides a compelling way to understand the transformative role of dynamic, intelligent documents as foundational elements in digital ecosystems. Just as a city relies on essential infrastructure like electricity, water, roads, and telecommunications to support its operations and enable the development of services and businesses, these advanced documents serve as the foundational infrastructure for modern information management, enabling a wide range of applications and services to be built on top of them. Imagine a bustling city. At its core, the city operates on a network of infrastructure systems that are invisible to most residents but are critical to its functioning. Electricity powers homes, businesses, and public spaces, while water systems ensure clean Attorney Docket No.: 226148.012001 / PCTdrinking water and sanitation. Roads and transportation networks connect neighborhoods, allowing people and goods to move efficiently. Telecommunications infrastructure enables communication, commerce, and access to information. These systems are not the end goal themselves; rather, they are the foundation upon which the city’s economy, culture, and daily life thrive. Similarly, intelligent documents act as the infrastructure for digital ecosystems. They are not merely static files or isolated records; they are dynamic, interactive entities that provide the foundational capabilities needed for modern workflows, compliance, and collaboration. Just as a city’s infrastructure supports diverse activities like commerce, education, and healthcare, these documents enable a wide range of services, including verification, authentication, workflow automation, auditing, and data analysis.

[0128] In a city, the presence of reliable infrastructure allows businesses and services to flourish. For example, a restaurant relies on electricity to power its kitchen appliances, water for cooking and cleaning, roads for food deliveries, and telecommunications for online orders and customer communication. Without this infrastructure, the restaurant would struggle to operate efficiently or scale its services. In the digital world, intelligent documents provide similar foundational support. Consider a legal firm managing contracts. These documents enable the firm to automate workflows, such as tracking contract revisions, managing access permissions, and ensuring compliance with regulatory requirements.

[0129] The firm can build services like automated contract review, real-time collaboration, and secure sharing on top of the document infrastructure. These services are analogous to the restaurant’s reliance on city infrastructure—they are made possible by the foundational capabilities of these advanced documents. Attorney Docket No.: 226148.012001 / PCT

[0130] Cities often expand their infrastructure to accommodate growth and new opportunities. For instance, a city might build a new subway line to connect previously inaccessible neighborhoods, enabling economic development and improving residents’ quality of life. This expansion creates new possibilities for businesses, housing, and cultural activities. Intelligent documents similarly enable expansion in digital ecosystems. For example, an enterprise might integrate these documents into its customer relationship management (CRM) system. This integration allows the CRM to access real-time data from contracts, invoices, and other records, enabling advanced analytics and personalized customer interactions. Just as a new subway line connects neighborhoods, these documents connect disparate systems, breaking down silos and enabling seamless communication and collaboration.

[0131] City infrastructure is designed to be resilient and adaptable, ensuring that it can withstand challenges like natural disasters or population growth. For example, a city might upgrade its water system to handle increased demand or reinforce its electrical grid to prevent outages during storms. Intelligent documents offer similar resilience and adaptability in digital ecosystems. They are designed to be immutable, ensuring the integrity and trustworthiness of their content. At the same time, they are dynamic, allowing for real-time updates, granular access control, and integration with emerging technologies like artificial intelligence. This adaptability ensures that these documents can evolve alongside the needs of organizations, just as city infrastructure evolves to meet the needs of its residents.

[0132] The city infrastructure analogy illustrates the foundational role of intelligent documents in digital ecosystems. Just as a city’s infrastructure supports the development of services, businesses, and communities, these documents provide the Attorney Docket No.: 226148.012001 / PCTcapabilities needed for modern workflows, compliance, and collaboration. They enable organizations to build services, expand their capabilities, and adapt to changing needs, creating a robust and interconnected digital environment. This analogy underscores the transformative potential of these documents as the infrastructure for the future of information management.

[0133] Documents as infrastructure enable a wide range of new services and workflows that transform traditional document management into dynamic, interactive, and automated processes. For instance, automated contract review becomes possible as documents as infrastructure autonomously analyze clauses, flag discrepancies, and suggest edits based on predefined rules or past agreements, streamlining legal workflows. Real-time collaboration is enhanced as multiple users can simultaneously edit, comment, and interact with a single authoritative version of a document, with all changes tracked and logged. Dynamic access control ensures sensitive information is protected by enforcing granular permissions based on user roles, security clearances, or contextual conditions. Audit trail generation is seamlessly integrated, as documents as infrastructure automatically record all interactions, including edits, views, and shares, creating a comprehensive log for compliance and regulatory purposes.

[0134] Version management is simplified, as documents as infrastructure maintain a timeline of changes, allowing users to access previous versions or compare differences without duplicating files. Embedded applications hosted within these documents enable users to perform complex tasks, such as calculations, data visualizations, or form- filling, directly within the document itself. Workflow automation is another key capability, as documents as infrastructure can trigger actions like sending notifications, initiating approvals, Attorney Docket No.: 226148.012001 / PCTor updating related systems based on predefined rules or user interactions. Secure sharing is facilitated by enforcing restrictions, such as requiring recipients to sign an NDA or authenticate their identity before accessing the content. Data synchronization ensures that documents as infrastructure integrate seamlessly with external databases or systems, keeping their content up-to-date and consistent across platforms.

[0135] Dynamic rendering enables documents as infrastructure to adapt their layout and content based on the user’s device, role, or preferences, providing an optimized viewing experience. Content personalization further enhances usability by tailoring the document’s content to individual users, such as displaying different sections based on user roles or preferences. Compliance verification is automated, as documents as infrastructure autonomously check their content against regulatory requirements, flagging non-compliance and suggesting corrections. Lead generation is supported by enabling documents shared externally to collect user information, such as names and emails, before granting access, creating opportunities for marketing and sales. Data analytics capabilities allow documents as infrastructure to aggregate and analyze metadata, providing insights into user behavior, engagement patterns, and workflow efficiency.

[0136] Documents as infrastructure also establish relationships with other documents, such as linking contracts to appendices or invoices to purchase orders, enabling seamless navigation and contextual understanding. Content redaction is automated, allowing sensitive information to be hidden based on access permissions or user-defined rules, ensuring confidentiality. Offline access is supported, enabling users to securely interact with documents as infrastructure even when disconnected, while maintaining synchronization with the authoritative version upon reconnection. Ownership transition is facilitated, as Attorney Docket No.: 226148.012001 / PCTdocuments as infrastructure can transfer ownership or permissions to designated successors upon predefined conditions, such as the death of the original owner. Dynamic notifications keep users informed of updates, deadlines, or required actions, ensuring timely responses and efficient workflows.

[0137] Finally, documents as infrastructure integrate seamlessly with AI systems, enabling contextual insights, automating repetitive tasks, and answering queries based on their content and metadata. These capabilities collectively transform documents from static files into dynamic infrastructure, revolutionizing workflows, enhancing collaboration, and unlocking new opportunities for automation and efficiency.

[0138] Aspects of this disclosure address the technical problem of maintaining control and security over electronic documents once they have been shared beyond the original digital perimeter. 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. This lack of control can lead to unauthorized dissemination, security breaches, and potential exposure of sensitive information.

[0139] The technical problem is further compounded by the limitations of existing methods, which often rely on static security measures, such as passwords or encryption, that do not provide dynamic control or real-time monitoring capabilities. These methods are insufficient for managing documents across diverse platforms and devices, where the risk of unauthorized access and data leakage is high.

[0140] Aspects of this disclosure may address this problem by introducing a computer-implemented method or system that provisions the document as digital infrastructure, embedding an API within the document itself. This API enables the document Attorney Docket No.: 226148.012001 / PCTto function as a smart digital object, allowing for remote management and control. The method includes storing data within the document, receiving access requests, determining authorization, and controlling access—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 embodiments disclosed herein provides a robust solution to the challenges of document security and control in modern digital environments.

[0141] These aspects of the disclosure enhance the function of computing devices by transforming the way electronic documents are managed, accessed, and controlled, thereby significantly improving the device’s capabilities. By provisioning the document as digital infrastructure with an embedded API, the computing device gains the ability to manage documents as smart digital objects. This transformation allows for remote control and management of the document, enabling the device to enforce access permissions, track interactions, and maintain document integrity even after distribution. The computing device can dynamically manage access to the document, allowing for real-time updates to permissions based on user roles, security clearances, or contextual conditions. This flexibility ensures that the device can adapt to changing security requirements and organizational policies, providing a more responsive and secure document management system.

[0142] Some aspects of this disclosure address technical problems related to the secure and efficient access of electronic documents across different computing devices, focusing on the interaction between the document and the hardware components involved. In traditional document management systems, accessing documents from remote devices Attorney Docket No.: 226148.012001 / PCToften involves significant security risks and compatibility issues. When a document is accessed from a remote viewer, there is a challenge in ensuring that the document’s content remains secure and that the interaction is seamless across different hardware platforms. Additionally, providing users with an indication of the document’s trustworthiness is difficult, especially when documents are accessed from various devices with differing capabilities.

[0143] Some aspects introduce a technical solution to these technical difficulties via a method or system where the request to access the document is received from a remote viewer that is programmed to interact with the document's embedded API. This interaction is executed as part of the document, allowing the document to be accessed securely from any remote computing device. The embedded API ensures that the document’s content is rendered correctly and securely, regardless of the hardware specifications of the remote device. This approach mitigates compatibility issues and enhances security by ensuring that the document’s access protocols are consistently applied across different devices.

[0144] Other aspects build on such solutions by ensuring that the viewer provides a user accessing the data with an indication of the document’s trustworthiness. This is achieved through the embedded API, which communicates with the hardware components of the remote device to display security indicators, such as encryption status or access permissions. By leveraging the hardware’s capabilities, such as display and processing power, the system can provide real-time feedback on the document’s security status, enhancing user confidence and ensuring that the document’s integrity is maintained during access.

[0145] Together, these aspects provide a comprehensive solution to the technical problems of secure and reliable document access across diverse hardware platforms, Attorney Docket No.: 226148.012001 / PCTensuring that users can interact with documents confidently and securely, regardless of the device used.

[0146] Some aspects address the technical challenge of ensuring that a document’s interface remains stable and reliable, regardless of the hardware used to access it. Inconsistencies can lead to security vulnerabilities, unauthorized access, and difficulties in integrating with other systems, as different devices may interpret document structures and access protocols differently.

[0147] Some aspects provide a technical solution to this problem by introducing a computer-implemented method or system where a document is structured as an immutable API that provides an immutable interface for accessing and interacting with the data. This immutable API, being embedded within or otherwise an integral part of the document itself, ensures that the document’s structure and access protocols remain consistent and reliable across all hardware platforms. The API also facilitates seamless integration with other systems and applications, allowing the device to interact with a broader digital ecosystem without compatibility issues. This capability enables the device to perform more complex tasks and workflows without additional processing delays, enhancing its effectiveness in managing digital documents. Furthermore, with a standardized interface for document interaction, the likelihood of errors due to misinterpretation of document structures or access protocols is minimized. This reduction in errors leads to more reliable document processing and fewer interruptions in workflow, wasted compute cycles, and system crashes, making a physical computing device more efficient and effect.

[0148] In traditional document management systems, maintaining ownership and control over electronic documents once they have been shared is a significant challenge. As Attorney Docket No.: 226148.012001 / PCTnoted, when documents are distributed, the original owner often loses the ability to manage ownership rights and control the distribution of the document. This lack of control can lead to unauthorized sharing, modification, or misuse of the document, potentially resulting in the exposure of sensitive information and legal complications.

[0149] Some aspects address this technical problem by introducing a method or system where the document controls ownership via an immutable application programming interface (API). This API is embedded within the document, providing a stable and immutable interface for managing ownership rights. By embedding the API, the document becomes a smart digital object that can enforce ownership controls consistently across all platforms and devices.

[0150] Another technical problem addressed by aspects of this disclosure is the difficulty in maintaining control and oversight over electronic documents once they have been shared with third parties. In traditional document management systems, once a document is distributed, the original owner often loses the ability to manage and monitor the document's usage and distribution. This lack of control can lead to unauthorized sharing, modification, or misuse of the document, potentially resulting in the exposure of sensitive information and legal complications. Additionally, ensuring that the document remains linked to its original legal context and intended use becomes challenging.

[0151] Aspects of this disclosure address this problem by introducing a method that allows for the sharing of a document while maintaining control over it through the execution of the document itself. The document, provisioned as digital infrastructure with an embedded API, enables the owner to share the document with a third party while retaining the ability to manage and monitor its usage. This includes maintaining control over the Attorney Docket No.: 226148.012001 / PCTdocument's access and ensuring that it remains linked to its original legal context. By embedding an API within the document, the system can dynamically manage and monitor document usage, reducing the need for redundant data transfers and minimizing bandwidth consumption. The API allows for the enforcement of access permissions and tracking of interactions directly within the document, which means that changes in access rights or document status do not require the entire document to be re-transmitted across the network. This capability significantly reduces the network load and optimizes bandwidth usage.

[0152] A self-determining document autonomously enforces and manages non- disclosure agreement (NDA) restrictions, ensuring secure interactions between users, the document, and external systems. The document is configured to enforce NDA compliance before granting access, with embedded intelligence defining the terms of the NDA and specifying authentication methods such as email verification or biometric validation. When a user attempts to access the document, the embedded intelligence prompts the user to electronically sign the NDA, storing the signed agreement as metadata to ensure enforceable compliance throughout the document’s lifecycle.

[0153] Once shared, the document tracks interactions to confirm adherence to NDA terms, verifying that recipients have agreed to the restrictions before granting access. Unauthorized access or violations trigger immediate revocation of permissions, with the document notifying the owner and logging attempted breaches. The document also displays notices to users who have not signed the NDA, guiding them through the signing process while preventing access to the document’s content until compliance is achieved.

[0154] The document facilitates the signing process by presenting the NDA in a clear format, offering options for electronic signatures through methods such as email Attorney Docket No.: 226148.012001 / PCTverification, biometric validation, or secure token-based authentication. Upon signing, the document updates its metadata to reflect the agreement, dynamically adjusting access permissions based on the user’s role and the NDA terms. The document restricts access to sensitive sections, using visual indicators like locked icons or grayed-out areas to denote inaccessible content. It also reminds users of their obligations under the NDA, such as confidentiality and time-limited access, while providing interactive features like comment fields and annotation tools tailored to the user’s permissions.

[0155] The document tracks user interactions, including sections accessed, time spent, and actions performed, such as downloading or printing. It provides the owner with detailed analytics, engagement metrics, and compliance summaries, issuing alerts for unusual activity or unauthorized sharing attempts. The document owner can manage access permissions, revoke access, grant temporary access, or export interaction logs for compliance reporting. Notifications inform users of updates or changes to the document, ensuring adherence to NDA terms.

[0156] When the document owner terminates an NDA, the embedded intelligence revokes access immediately, logging the action in the audit trail and notifying the user of their restricted status. The document interrupts ongoing sessions and prevents future access, displaying a “Notice of Unavailability” with details about the revocation. The owner’s dashboard provides a comprehensive view of updated access permissions, confirming the revocation and documenting the reason, timestamp, and initiating party.

[0157] The document enforces real-time access control, ensuring sensitive information remains secure and inaccessible to unauthorized users. Its embedded intelligence dynamically manages permissions, providing the owner with confidence in the Attorney Docket No.: 226148.012001 / PCTdocument’s security and compliance. By autonomously managing NDA restrictions, the document delivers tailored user experiences, robust security, and efficient control over sensitive information.

[0158] 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 global marker, and embedded intelligence. This innovative structure addresses longstanding challenges in document management, auditing, and compliance.

[0159] Immutable Content

[0160] 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.

[0161] Immutable Audit Trail

[0162] 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 Attorney Docket No.: 226148.012001 / PCTcryptographic 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.

[0163] Immutable Connection to a Permanent Global Marker

[0164] 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.

[0165] 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.

[0166] 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: Attorney Docket No.: 226148.012001 / PCT

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

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

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

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

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

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

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

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

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

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

[0177] Benefits of the Immutable Structure

[0178] Integrity: The immutability of the content ensures that the document remains unchanged and trustworthy throughout its lifecycle. Attorney Docket No.: 226148.012001 / PCT

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

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

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

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

[0183] 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.

[0184] 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.)

[0185] 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 Attorney Docket No.: 226148.012001 / PCTdocument 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.

[0186] Features of Embedded Intelligence

[0187] Self-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.

[0188] 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.

[0189] 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 Attorney Docket No.: 226148.012001 / PCTdocument can seamlessly integrate with diverse systems and applications, making it highly interoperable.

[0190] 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's lifecycle stage, or the specific task being performed. This dynamic adaptability enhances usability and ensures that the document serves the needs of each stakeholder effectively.

[0191] 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.

[0192] How Intelligence is Embedded

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

[0194] 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.

[0195] 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 Attorney Docket No.: 226148.012001 / PCTits integrity. The document's intelligence uses this metadata to make decisions and respond to queries.

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

[0197] APIs for Interaction: Smart documents expose APIs (Application Programming 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.

[0198] 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.

[0199] 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.

[0200] Examples of Embedded Intelligence in Action Attorney Docket No.: 226148.012001 / PCT

[0201] 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.

[0202] 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.

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

[0204] 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.

[0205] 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.

[0206] 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.

[0207] 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 Attorney Docket No.: 226148.012001 / PCTaddress longstanding challenges in document security, compliance, and usability, while enabling dynamic interactions and personalized experiences.

[0208] The Synergy of Immutability and Embedded Intelligence

[0209] 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 document to interact dynamically with its environment, adapt to its context, and provide personalized experiences.

[0210] 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.

[0211] 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.

[0212] 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. Attorney Docket No.: 226148.012001 / PCT

[0213] 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.

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

[0215] Real-World Applications

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

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

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

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

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

[0221] 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 Attorney Docket No.: 226148.012001 / PCTpersonalized experiences, this synergy addresses longstanding challenges and unlocks new possibilities for innovation and efficiency.

[0222] Alternative Terminology

[0223] The term “smart document” or “smart electronic document” can also be referred to as a self-determinative document, an active 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.

[0224] The self-determining document solves the technical problem of traditional document systems by autonomously managing access requests, determining authorization, and controlling access to its data. The document can achieve this through its immutable structure, embedded intelligence, and integration of a permanent global marker, and / or because of any of the other features and characteristics of smart documents.

[0225] The immutable content ensures that the document’s data remains unaltered and trustworthy throughout its lifecycle. Cryptographic techniques, such as hashing and digital signatures, secure the content, allowing the document to verify its integrity and authenticity. Any attempt to modify the content results in a mismatch between the original cryptographic fingerprint and the altered data, signaling tampering. This immutability guarantees that the document can reliably assess whether the data being accessed is consistent with its original state. Attorney Docket No.: 226148.012001 / PCT

[0226] The immutable audit trail records every interaction with the document, including access requests, modifications, and approvals. Each event is cryptographically secured and timestamped, ensuring that the sequence of events remains unaltered. The audit trail provides the document with a complete history of interactions, enabling it to analyze past events and determine whether an entity requesting access has the necessary permissions. This ensures that the document can make informed decisions about granting or denying access.

[0227] The permanent global marker serves as a unique and unchanging identifier for the document, linking its content and audit trail. This marker is embedded in the document’s metadata and cryptographically secured, ensuring that the document can always be referenced and retrieved in its original form. The global marker allows the document to maintain a single source of truth, eliminating ambiguity and enabling seamless integration with external systems. By leveraging this marker, the document ensures that access requests are evaluated against a consistent and authoritative record.

[0228] Embedded intelligence enables the document to process access requests dynamically. The document uses its executable code to evaluate the entity’s credentials, analyze its metadata and audit trail, and determine whether the entity is authorized to access the data. This intelligence allows the document to autonomously enforce access permissions, track interactions, and adapt its behavior based on the context of the request. For example, the document can recognize the identity of the entity, the device being used, and the stage of the document’s lifecycle, tailoring its response accordingly.

[0229] The document’s ability to control access is further enhanced by its integration of APIs for interaction. These APIs enable the document to communicate with Attorney Docket No.: 226148.012001 / PCTexternal systems, process access requests, and return responses in a structured format. The APIs ensure that the document can enforce access permissions consistently across diverse platforms and devices, maintaining security and usability.

[0230] By combining immutability, embedded intelligence, and a permanent global marker, the self-determining document can address the limitations of traditional systems, which rely on static files and external mechanisms for access control. The document can autonomously manage access requests, determine authorization, and control access to its data, ensuring security, integrity, and traceability in modern digital environments. This approach transforms the document into an active and reliable entity capable of solving the technical problem of maintaining control and security over shared data.

[0231] A document as infrastructure addresses the technical problem of fragmented, insecure, and static document systems by transforming the document into a dynamic, self-contained entity with immutable content, an immutable audit trail, and an immutable global identifier, all of which are machine-readable and cryptographically secured. Traditional document systems struggle with maintaining consistency, authenticity, and traceability, often relying on external mechanisms to manage interactions and ensure security. The document as infrastructure solves this problem by embedding intelligence in the form of executable code, enabling the document to be responsive and reactive to its environment. The immutable content ensures that the document remains unchanged and trustworthy, while the immutable audit trail records every interaction, providing a tamper- proof history of the document’s lifecycle. The immutable global identifier links the content and audit trail, ensuring that the document can always be referenced and retrieved in its original form. Together, these features create a unified, machine-readable framework that Attorney Docket No.: 226148.012001 / PCTenables the document to autonomously enforce access controls, adapt to user needs, and integrate seamlessly with external systems, offering a robust technical solution to modern document management challenges.

[0232] A document as infrastructure solves 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 machine- readable 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 document autonomously enforces granular access permissions, reducing the risk of unauthorized access and ensuring compliance with security protocols.

[0233] Regarding device hardware, traditional PDFs require significant computational resources for rendering, extracting data, and managing versions, often leading to inefficiencies and hardware strain. A document as infrastructure, with its machine- readable format, eliminates 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 document as infrastructure addresses 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 minimizes network bandwidth Attorney Docket No.: 226148.012001 / PCTusage, streamlines workflows, and ensures that documents are securely and efficiently managed across devices and systems.

[0234] The following clauses exemplify how documents provisioned as digital infrastructure provide solutions to technical problems:

[0235] Clause 1. A computer-implemented method performed by an electronic document provisioned as digital infrastructure, the computer-implemented method comprising: receiving, at the electronic document, a request from an entity to access data associated with the electronic document; determining, via execution of the electronic document, whether the entity is allowed to access the data; and controlling, via execution of the electronic document, an ability of the entity to access the data.

[0236] Traditional document systems lack the ability to dynamically and autonomously manage access control, leading to inefficiencies, security risks, and reliance on external systems for enforcing permissions. Clause 1 introduces an electronic document provisioned as digital infrastructure that autonomously evaluates access requests, determines authorization, and enforces access control directly within the document, which can ensure secure, efficient, and real-time management of data access.

[0237] Clause 2. The computer-implemented method of clause 1, wherein the electronic document comprises an application programming interface that provides an immutable interface for accessing and interacting with the data.

[0238] A problem that can be solved by this clause is the inconsistency and vulnerability of traditional electronic document interfaces, which can be altered or misinterpreted across different systems, leading to security and usability issues. By embedding an application programming interface (API) that provides an immutable interface, Attorney Docket No.: 226148.012001 / PCTthe clause ensures that the document’s structure and access protocols remain stable and reliable, enabling secure and consistent interaction across diverse platforms and devices.

[0239] Clause 3. The computer-implemented method of one or more of clauses 1- 2, wherein the electronic document controls ownership of the electronic document via the application programming interface.

[0240] A problem that can be solved by this clause is the difficulty in maintaining ownership and control over electronic documents once they have been shared, which can lead to unauthorized modifications, misuse, or loss of ownership rights of electronic documents. By enabling the electronic document to control ownership through an embedded application programming interface (API), the clause can ensure that ownership rights are consistently enforced, allowing the document’s owner to define, modify, and revoke permissions dynamically across all platforms and devices.

[0241] Clause 4. The computer-implemented method of one or more of clauses 1- 3, further comprising: sharing, via executing the electronic document, the electronic document with a third party; and maintaining control of the electronic document, via executing the electronic document, after sharing the electronic document with the third party.

[0242] A problem that can be solved by this clause is that traditional document systems can lose control over electronic documents once they are shared with third parties, leading to unauthorized access or misuse. By enabling the electronic document to execute sharing while maintaining control, the clause ensures that the document’s owner can dynamically manage permissions, revoke access, and monitor interactions even after the document has been distributed. Attorney Docket No.: 226148.012001 / PCT

[0243] Clause 5. The computer-implemented method of one or more of clauses 1- 4, wherein the request is received from a remote viewer that is programmed to provide access to the data within the electronic document by interacting with the application programming interface that is executing as part of the electronic document.

[0244] A problem that can be solved by this clause is the challenge of securely accessing electronic documents from remote devices, which can be prone to compatibility issues and unauthorized access. By allowing the request to be received from a remote viewer programmed to interact with the application programming interface embedded within the electronic document, the clause can ensure that access can be securely provided while maintaining consistent functionality across diverse platforms and devices.

[0245] Clause 6. The computer-implemented method of one or more of clauses 1- 5, wherein the remote viewer provides a user accessing the data with an indication of trustworthiness of the data.

[0246] A problem that can be solved by this clause is the difficulty users face in determining the authenticity and reliability of data accessed through electronic documents, which can lead to mistrust or misuse. By enabling the remote viewer to provide an indication of the trustworthiness of the data, the clause can ensure that users can be informed of the document’s integrity and security, enhancing confidence and reducing the risk of unauthorized or erroneous interactions.

[0247] Clause 7. The computer-implemented method of one or more of clauses 1- 6, wherein providing the user with access to the data does not change a location of the electronic document. Attorney Docket No.: 226148.012001 / PCT

[0248] A problem that can be solved by this clause is the inefficiency and security risks associated with relocating electronic documents during access, which can lead to duplication, fragmentation, or unauthorized distribution. By ensuring that providing access to the data does not change the location of the electronic document, the clause can ensure that the document can be securely accessed while maintaining a single authoritative version, reducing redundancy and enhancing control.

[0249] Clause 8. A system comprising: at least one physical processor; physical memory comprising computer-executable instructions that, when executed by the physical processor, cause the physical processor to: store, via execution of an electronic document on a computing device, data of the electronic document; receive, at the electronic document, a request from an entity to access the electronic document; determine, via execution of the electronic document, whether the entity is allowed to access the data of the electronic document; and control, via execution of the electronic document, access to the data within of the electronic document.

[0250] Clause 9. The system of clause 8, wherein the electronic document comprises an application programming interface that provides an immutable interface for accessing and interacting with the data.

[0251] Clause 10. The system of one or more of clauses 8-9, wherein the electronic document controls ownership of the electronic document via the application programming interface.

[0252] Clause 11. The system of one or more of clauses 8-10, wherein the computer-executable instructions, when executed by the physical processor, further cause the physical processor to: share, via executing the electronic document, the electronic Attorney Docket No.: 226148.012001 / PCTdocument with a third party; and maintain control of the electronic document, via executing the electronic document, after sharing the electronic document with the third party.

[0253] Clause 12. The system of one or more of clauses 8-11, wherein the request is received from a remote viewer that is programmed to provide access to the data within the electronic document by interacting with the application programming interface that is executing as part of the electronic document.

[0254] Clause 13. The system of one or more of clauses 8-12, wherein the remote viewer provides a user accessing the data with an indication of trustworthiness of the data.

[0255] Clause 14. The system of one or more of clauses 8-13, wherein providing the user with access to the data does not change a location of the electronic document.

[0256] Clause 15. A non-transitory computer-readable medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to: store, via execution of an electronic document on a computing device, data within the electronic document; receive, at the electronic document, a request from an entity to access the electronic document; determine, via execution of the electronic document, whether the entity is allowed to access the electronic document; and control, via execution of the electronic document, access to the data within the electronic document.

[0257] Clause 16. The non-transitory computer-readable medium of clause 15, wherein the electronic document comprises an application programming interface that provides an immutable interface for accessing and interacting with the data. Attorney Docket No.: 226148.012001 / PCT

[0258] Clause 17. The non-transitory computer-readable medium of clause 16, wherein the electronic document controls ownership of the electronic document via the application programming interface.

[0259] Clause 18. The non-transitory computer-readable medium of one or more of clauses 15-16, wherein the computer-executable instructions, when executed by the at least one processor, further cause the processor to: share, via executing the electronic document, the electronic document with a third party; and maintain control of the electronic document, via executing the electronic document, after sharing the electronic document with the third party.

[0260] Clause 19. The non-transitory computer-readable medium of one or more of clauses 15-18, wherein the request is received from a remote viewer that is programmed to provide access to the data within the electronic document by interacting with the application programming interface that is executing as part of the electronic document.

[0261] Clause 20. The non-transitory computer-readable medium of one or more of clauses 15-19, wherein the viewer provides a user accessing the data with an indication of trustworthiness of the data.

[0262] Clause 21. A computer-implemented method performed by an electronic document provisioned as digital infrastructure, the computer-implemented method comprising: receiving, at the electronic document, a request from an entity to interact with the electronic document. determining, via execution of the electronic document, interaction permissions of the entity; and controlling, via execution of the electronic document, the interaction based on the interaction permissions. Attorney Docket No.: 226148.012001 / PCT

[0263] Clause 22. The computer-implemented method of clause 21, wherein determining the interaction permissions further comprises evaluating the interaction permissions of the entity against a set of predefined access criteria embedded within the electronic document.

[0264] Clause 23. The computer-implemented method of one or more of clauses 21-22, wherein controlling the interaction based on the permissions further comprises personalizing a view of the electronic document by selectively rendering document sections according to the interactions permissions of the entity.

[0265] Clause 24. The computer-implemented method of clause 21-23, wherein the electronic document includes semantic tags associated with distinct content sections, and determining the interaction permissions further comprises comparing a clearance level of the entity with access requirements linked to the semantic tags.

[0266] Clause 25. The computer-implemented method of clause 21-24, further comprising synchronizing real-time modifications of the electronic document across multiple users based on the interaction permissions.

[0267] Clause 26. The computer-implemented method of clause 21-25, further comprising logging each interaction event with the electronic document and updating an audit trail of the electronic document in real time.

[0268] Clause 27. The computer-implemented method of clause 21-26, wherein controlling the interaction based on the permissions comprises dynamically altering interactive elements of the electronic document. Attorney Docket No.: 226148.012001 / PCT

[0269] Clause 28. The method of clause 21-27, wherein dynamically altering interactive elements of the electronic document comprises enabling or disabling in-document applications and features based on the interaction permissions of the entity.

[0270] Clause 29. The computer-implemented method of clause 21-28, further comprising displaying a notification to the entity upon at least one of: a change in the interaction permissions; or detection of an unauthorized access attempt by the entity.

[0271] Clause 30. The computer-implemented method of clause 21-29, wherein controlling the interaction further comprises executing a lose access mechanism that permanently restricts access to the electronic document by severing all connections to data of the electronic document in a manner that renders the document irretrievable while maintaining metadata of the document.

[0272] Clause 31. The computer-implemented method of clause 21-30, wherein controlling the interaction further comprises limiting a number of times the electronic document can be shared by an authorized entity such that once a predefined number of shares is reached, additional sharing attempts are denied by the electronic document.

[0273] Clause 32. The computer-implemented method of clause 21-31, wherein controlling the interaction further comprises enabling ownership transition of the electronic document by transferring the interaction permissions to a designated successor entity upon an occurrence of a predefined condition.

[0274] Clause 33. The method of clause 21-32, wherein the predefined condition comprises a legal transfer of ownership of the electronic document.

[0275] Clause 34. The computer-implemented method of clause 21-33, wherein controlling the interaction further comprises enforcing ownership rights by allowing an owner Attorney Docket No.: 226148.012001 / PCTof the electronic document to define, modify, and revoke access permissions at any time such that the electronic document remains under exclusive control of an owner of the electronic document regardless of its distribution or storage location.

[0276] Clause 35. The computer-implemented method of clause 21-34, wherein controlling the interaction further comprises maintaining virtual custody of the electronic document by enabling an owner of the electronic document to remotely manage access to the document in real-time regardless of a physical location of the electronic document or a number of distributed copies of the electronic document.

[0277] Clause 36. The computer-implemented method of clause 21-35, wherein controlling the interaction further comprises enabling remote control of the electronic document by allowing an owner of the electronic document to dynamically adjust access permissions, revoke access, and track interactions through an embedded application programming interface, regardless of a storage location of the electronic document or a device used to access the electronic document.

[0278] Clause 37. The computer-implemented method of clause 21-36, wherein controlling the interaction further comprises ensuring universal accessibility by enabling authorized users to securely access the electronic document across a plurality of platforms, devices, and operating systems while maintaining consistent access control to the electronic document.

[0279] Clause 38. The computer-implemented method of clause 21-37, wherein controlling the interaction further comprises maintaining a universal frictionless system of record for the electronic document by providing a single authoritative version of the Attorney Docket No.: 226148.012001 / PCTelectronic accessible in real-time for each entity authorized to interact with the electronic document.

[0280] Clause 39. The computer-implemented method of clause 21-38, wherein controlling the interaction further comprises controlling access to a data layer associated with the document.

[0281] Clause 40. The computer-implemented method of clause 21-39, wherein controlling the interaction further comprises decrypting encrypted data upon verifying that the interaction permissions of the entity allow access to the encrypted data.

[0282] 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.

[0283] As detailed above, 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 modules 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.

[0284] 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 Attorney Docket No.: 226148.012001 / PCTmaintain 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.

[0285] 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, Central Processing 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.

[0286] 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 or more of these modules may also represent all or portions of one or more special-purpose computers configured to perform one or more tasks. Attorney Docket No.: 226148.012001 / PCT

[0287] 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.

[0288] 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.

[0289] 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.

[0290] The preceding description has been provided to enable 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 Attorney Docket No.: 226148.012001 / PCT

Claims

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. [0291] 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.” Attorney Docket No.: 226148.012001 / PCTWHAT IS CLAIMED IS:

1. A computer-implemented method performed by an electronic document provisioned as digital infrastructure, the computer-implemented method comprising: receiving, at the electronic document, a request from an entity to access data associated with the electronic document; determining, via execution of the electronic document, whether the entity is allowed to access the data; and controlling, via execution of the electronic document, an ability of the entity to access the data.

2. The computer-implemented method of claim 1, wherein the electronic document comprises an application programming interface that provides an immutable interface for accessing and interacting with the data.

3. The computer-implemented method of claim 2, wherein the electronic document controls ownership of the electronic document via the application programming interface.

4. The computer-implemented method of claim 1, further comprising: sharing, via executing the electronic document, the electronic document with a third party; and Attorney Docket No.: 226148.012001 / PCTmaintaining control of the electronic document, via executing the electronic document, after sharing the electronic document with the third party.

5. The computer-implemented method of claim 2, wherein the request is received from a remote viewer that is programmed to provide access to the data within the electronic document by interacting with the application programming interface that is executing as part of the electronic document.

6. The computer-implemented method of claim 5, wherein the remote viewer provides a user accessing the data with an indication of trustworthiness of the data.

7. The computer-implemented method of claim 6, wherein providing the user with access to the data does not change a location of the electronic document.

8. A system comprising: at least one physical processor; physical memory comprising computer-executable instructions that, when executed by the physical processor, cause the physical processor to: store, via execution of an electronic document on a computing device, data of the electronic document; receive, at the electronic document, a request from an entity to access the electronic document; Attorney Docket No.: 226148.012001 / PCTdetermine, via execution of the electronic document, whether the entity is allowed to access the data of the electronic document; and control, via execution of the electronic document, access to the data within of the electronic document.

9. The system of claim 8, wherein the electronic document comprises an application programming interface that provides an immutable interface for accessing and interacting with the data.

10. The system of claim 9, wherein the electronic document controls ownership of the electronic document via the application programming interface.

11. The system of claim 8, wherein the computer-executable instructions, when executed by the physical processor, further cause the physical processor to: share, via executing the electronic document, the electronic document with a third party; and maintain control of the electronic document, via executing the electronic document, after sharing the electronic document with the third party.

12. The system of claim 9, wherein the request is received from a remote viewer that is programmed to provide access to the data within the electronic document by interacting with the application programming interface that is executing as part of the electronic document. Attorney Docket No.: 226148.012001 / PCT13. The system of claim 12, wherein the remote viewer provides a user accessing the data with an indication of trustworthiness of the data.

14. The system of claim 13, wherein providing the user with access to the data does not change a location of the electronic document.

15. A non-transitory computer-readable medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to: store, via execution of an electronic document on a computing device, data within the electronic document; receive, at the electronic document, a request from an entity to access the electronic document; determine, via execution of the electronic document, whether the entity is allowed to access the electronic document; and control, via execution of the electronic document, access to the data within the electronic document.

16. The non-transitory computer-readable medium of claim 15, wherein the electronic document comprises an application programming interface that provides an immutable interface for accessing and interacting with the data. Attorney Docket No.: 226148.012001 / PCT17. The non-transitory computer-readable medium of claim 16, wherein the electronic document controls ownership of the electronic document via the application programming interface.

18. The non-transitory computer-readable medium of claim 15, wherein the computer-executable instructions, when executed by the at least one processor, further cause the processor to: share, via executing the electronic document, the electronic document with a third party; and maintain control of the electronic document, via executing the electronic document, after sharing the electronic document with the third party.

19. The non-transitory computer-readable medium of claim 16, wherein the request is received from a remote viewer that is programmed to provide access to the data within the electronic document by interacting with the application programming interface that is executing as part of the electronic document.

20. The non-transitory computer-readable medium of claim 19, wherein the viewer provides a user accessing the data with an indication of trustworthiness of the data.

21. A computer-implemented method performed by an electronic document provisioned as digital infrastructure, the computer-implemented method comprising: Attorney Docket No.: 226148.012001 / PCTreceiving, at the electronic document, a request from an entity to interact with the electronic document. determining, via execution of the electronic document, interaction permissions of the entity; and controlling, via execution of the electronic document, the interaction based on the interaction permissions.

22. The computer-implemented method of claim 21, wherein determining the interaction permissions further comprises evaluating the interaction permissions of the entity against a set of predefined access criteria embedded within the electronic document.

23. The computer-implemented method of claim 21, wherein controlling the interaction based on the permissions further comprises personalizing a view of the electronic document by selectively rendering document sections according to the interactions permissions of the entity.

24. The computer-implemented method of claim 21, wherein the electronic document includes semantic tags associated with distinct content sections, and determining the interaction permissions further comprises comparing a clearance level of the entity with access requirements linked to the semantic tags.

25. The computer-implemented method of claim 21, further comprising synchronizing real-time modifications of the electronic document across multiple users based on the interaction permissions. Attorney Docket No.: 226148.012001 / PCT26. The computer-implemented method of claim 21, further comprising logging each interaction event with the electronic document and updating an audit trail of the electronic document in real time.

27. The computer-implemented method of claim 21, wherein controlling the interaction based on the permissions comprises dynamically altering interactive elements of the electronic document.

28. The method of claim 27, wherein dynamically altering interactive elements of the electronic document comprises enabling or disabling in-document applications and features based on the interaction permissions of the entity.

29. The computer-implemented method of claim 21, further comprising displaying a notification to the entity upon at least one of: a change in the interaction permissions; or detection of an unauthorized access attempt by the entity.

30. The computer-implemented method of claim 21, wherein controlling the interaction further comprises executing a lose access mechanism that permanently restricts access to the electronic document by severing all connections to data of the electronic document in a manner that renders the document irretrievable while maintaining metadata of the document. Attorney Docket No.: 226148.012001 / PCT31. The computer-implemented method of claim 21, wherein controlling the interaction further comprises limiting a number of times the electronic document can be shared by an authorized entity such that once a predefined number of shares is reached, additional sharing attempts are denied by the electronic document.

32. The computer-implemented method of claim 21, wherein controlling the interaction further comprises enabling ownership transition of the electronic document by transferring the interaction permissions to a designated successor entity upon an occurrence of a predefined condition.

33. The method of claim 32, wherein the predefined condition comprises a legal transfer of ownership of the electronic document.

34. The computer-implemented method of claim 21, wherein controlling the interaction further comprises enforcing ownership rights by allowing an owner of the electronic document to define, modify, and revoke access permissions at any time such that the electronic document remains under exclusive control of an owner of the electronic document regardless of its distribution or storage location.

35. The computer-implemented method of claim 21, wherein controlling the interaction further comprises maintaining virtual custody of the electronic document by enabling an owner of the electronic document to remotely manage access to the document Attorney Docket No.: 226148.012001 / PCTin real-time regardless of a physical location of the electronic document or a number of distributed copies of the electronic document.

36. The computer-implemented method of claim 21, wherein controlling the interaction further comprises enabling remote control of the electronic document by allowing an owner of the electronic document to dynamically adjust access permissions, revoke access, and track interactions through an embedded application programming interface, regardless of a storage location of the electronic document or a device used to access the electronic document.

37. The computer-implemented method of claim 21, wherein controlling the interaction further comprises ensuring universal accessibility by enabling authorized users to securely access the electronic document across a plurality of platforms, devices, and operating systems while maintaining consistent access control to the electronic document.

38. The computer-implemented method of claim 21, wherein controlling the interaction further comprises maintaining a universal frictionless system of record for the electronic document by providing a single authoritative version of the electronic accessible in real-time for each entity authorized to interact with the electronic document.

39. The computer-implemented method of claim 21, wherein controlling the interaction further comprises controlling access to a data layer associated with the document. Attorney Docket No.: 226148.012001 / PCT

Images