Reddit Programming

example. At Decombine, we want to provide our users assurances of how their data will be handled during a sales process. We can take the contents of our policy for the sales process, package it into OCI, and then sign it. This is an overly simple scenario, but it illustrates the key points: our policy becomes a commitment that can be easily distributed, reproduced, and verified. Here is how we might do it with conventional tools today: Start with a simple document. # Sales Engagement Agreement ## Data Handling ### 1. Data Collection You agree to provide us with the following data to facilitate the sales engagement process: Stakeholders: - Name ... Push the document to a registry. oras push --artifact-type "application/vnd.decombine.text.v1+markdown" docker.io/decombine/texts:sales-v0.0.1 Contracts being packaged, stored, and transmitted via OCI involves services and tooling interacting with registries, but most software distributed cloud-natively already do that, so organizations should already have a base level of familiarity. The tangle benefits are clear, across the following major value proposition categories: Improved security supply chain using cryptographic digital signatures OCI artifacts can be validated and signed out of the box. Artifacts are typically verified at multiple levels and layers to ensure that what you’re getting when you retrieve one is exactly what you expected. This is relied on heavily for things like Software Bill of Materials (SBOM). Contracts can take advantage of these same principles to validate that a specific template is unchanged, comes from a specific party, and can prove all of this using the same industry standards relied on for financial services, federal government, and other regulated industries. This establishes a base level of attestation and verification that simply doesn't exist today. Organizations may independently digitally sign their documents, but that process isn't baked in. It also isn't cost-effective, simple, or easily verifiable, whereas OCI artifacts of all kinds have this potential out of the box with relatively little configuration. Smart organizations have been shifting security left for years now, including building in supply chain attestation and verification into their software development lifecycles. Adopting these practices would effectively achieve the same thing for business procedures that can be automated for use in more complex environments such as regulated industries or by automated systems such as AI agents. OCI for contracts would enable the adopting organization to effectively standardize published contracts as indisputably validated in their respective business processes / value chains. Sustainability and efficiency using protocol basics Conventional document storage and distribution is effectively the copying of thousands, millions, or even billions of independent files. Some storage systems may support highly complex deduplication techniques to reduce storage requirements, but this may not be at all possible with many types of contracts. Producing contracts programmatically using templates that are intelligently layered would drastically change the economics. OCI can be used to chunk contracts into template layers. If 90% of the end product is standardized, that means 90% of the contract could be in a single layer. Even if there are a billion independent versions of that file, as long as they share a common ancestor template, we're only concerned with storing the changes of that last 10%. The same goes for uploading, downloading, and transferring in general - we're just moving the changes. Let's put this into a practical example where we have 10 million contract file records. Each contract file is a PDF of about 6 MB. 90% of these files is exactly the same with the remaining 10% being customized. The storage benefits are clear, but this also means that the user experience around working with these documents is significantly improved. We're not

2 views17:00