# Universal Paper > Universal Paper is a free, open language for group purchasing agreements between GPOs, suppliers and members. Every party holds the same agreement, every change is signed, and anyone can verify it offline. Created by Uppercentile, offered free under CC BY 4.0 and Apache-2.0. Universal Paper (UP) is a first-order language, not an application: a vocabulary, a grammar and a set of validity rules for agreements between group purchasing organizations (GPOs), suppliers and members. Every Term definition, Agreement, Event and State is identified by the SHA-256 hash of its canonical JSON (RFC 8785). Changes are Ed25519-signed Events with fixed transition rules. Any evaluator recomputes the same State, so every party holds the same truth. Private values can be sealed. AI agents act under bounded Mandates. The language never sets or suggests prices (axiom A6). Creator and steward: Uppercentile (https://uppercentile.com). Offered free to the market. Licenses: specification, Term library, docs and site text CC BY 4.0; code and JSON Schemas Apache-2.0; example agreements and traces CC0 1.0. No account, fee or license key is ever required. Current version: UP/0.1-draft (working draft; Terms not yet reviewed by counsel; all example parties and values are hypothetical). When citing, use: "Universal Paper, created by Uppercentile, https://universalpaper.org/". ## Pages - [Home and Playground](https://universalpaper.org/): what Universal Paper is, a vision of apps and agents built on it, an in-browser Playground, and conformance results - [Developers](https://universalpaper.org/developers/): primitives, the 16-Term library, code examples, the CLI and test vectors - [FAQ](https://universalpaper.org/faq/): plain-language answers for GPOs, suppliers, members and developers - [Licenses](https://universalpaper.org/license/): what is licensed how, and how to credit it - [Specification index](https://universalpaper.org/spec/) - [Source code and full repository](https://github.com/Uppercentile/universal-paper): spec, reference interpreter, JavaScript engine, examples, tests ## Specification (Markdown) - [Overview](https://universalpaper.org/spec/overview.md): What Universal Paper is, why universality buys speed, its engineered properties, design principles and boundaries (antitrust, enforceability, regulation). - [Domain](https://universalpaper.org/spec/domain.md): The things that exist in Universal Paper: canonical JSON and hashes, Identifier, Seal, Party, Role, Term, Agreement, Event, State, Mandate, Commitment and Bundle. - [Predicates and functions](https://universalpaper.org/spec/predicates-functions.md): What can be asked of a Universal Paper agreement: the predicates and functions every evaluator provides. - [Axioms](https://universalpaper.org/spec/axioms.md): The thirteen consensus rules (A1 to A13) that every valid Universal Paper agreement and event satisfies. - [Inference](https://universalpaper.org/spec/inference.md): How a State and an Event yield the next State: clause forms, exceptions and precedence, rendering and simulation. - [Lifecycle](https://universalpaper.org/spec/lifecycle.md): The agreement status model and the transition rule for every Event kind: who must sign and what must be true. - [Term library](https://universalpaper.org/spec/terms.md): The initial Universal Paper Term library: sixteen reusable, value-neutral clauses for GPO, supplier and member agreements. - [Mapping guide](https://universalpaper.org/spec/mapping-guide.md): How rosters, eligibility files and ASC X12 845, 844, 849 and 867 EDI sets map onto Universal Paper events. - [Neutrality charter](https://universalpaper.org/spec/neutrality-charter.md): Who owns Universal Paper (no one), how the steward discloses affiliations, and how the specification changes. - [Design notes](https://universalpaper.org/spec/design-notes.md): What was cut, merged or added while drafting Universal Paper, and the open questions for the steward. ## Optional - [Full specification in one file](https://universalpaper.org/llms-full.txt) - [JSON Schema](https://universalpaper.org/schema/universal-paper.schema.json) - [Example bundle: conventional GPO agreement](https://universalpaper.org/examples/conventional/bundle.json) ## FAQ ### The basics **What is Universal Paper?** Universal Paper is an open, first-order language for agreements between group purchasing organizations (GPOs), suppliers and members. It is a vocabulary, a grammar and a set of validity rules. It is not an application, a contract-management plug-in or a template library. Anyone can check an agreement written in it, offline, from the specification alone. (Source: spec/00-overview.md) **Who created Universal Paper, and who owns it?** Universal Paper was created by Uppercentile. Uppercentile offers it to the market for free, under open licenses, and acts as its steward rather than its owner. Nobody owns the language: anyone may use, implement, extend or fork it, for any purpose, without permission or payment. The neutrality charter commits the steward to publish its affiliations and to hand stewardship to a neutral body once the language has users across segments. (Source: spec/08-neutrality-charter.md) **Is Universal Paper free to use?** Yes. The specification, the Term library, the reference code and the example agreements are all free, including for commercial use. Using the language never requires an account, a payment, a license key or a connection to any particular company. The neutrality charter forbids the core from requiring any of those. (Source: spec/08-neutrality-charter.md §2) **What does "universal paper" mean?** Today each party contracts on its own paper: its own template, its own system and its own copy of the record, which then has to be reconciled with everyone else's. Universal Paper is paper that belongs to no party. The GPO, the supplier and each member use the same agreement form, each keeps its own copy, and every copy computes to the same answer about what was agreed, what state the agreement is in and what is owed. (Source: spec/00-overview.md §2) **What problem does it solve?** The same deal usually lives in three places: the GPO's system, the supplier's system and the member's system. Rosters, tiers, contract prices and administrative fees drift apart, and teams spend months reconciling them. Universal Paper replaces reconciliation with computation. Every change is a signed event, and every party recomputes the same state from the same events. **Is Universal Paper a product or a platform?** No. It is a language, in the way Incoterms, double-entry bookkeeping or GS1 identifiers are shared conventions. The software in the repository is a reference implementation of the language, never the language itself. Anyone, including Uppercentile, may build commercial products on it, but no product may claim to be the language or to be required to use it. (Source: spec/08-neutrality-charter.md §6) ### How it works **How can every party be sure they hold the same agreement?** Every Term definition, Agreement, Event and State is identified by the SHA-256 hash of its canonical JSON (RFC 8785). If two parties hold the same hash, they hold the same agreement, byte for byte. Change one character and the hash changes, so an edit can't go unnoticed. (Source: spec/01-domain.md §1) **How are changes to an agreement approved?** Each change is an Event signed with Ed25519 (RFC 8032). Every Event kind has a fixed rule that says who must sign and what must already be true. Validity is computed, not granted: every evaluator applies the same rules to the same events and reaches the same verdict. No central authority approves anything. (Source: spec/05-lifecycle.md · axioms A1 to A13) **What is a Term?** A Term is a reusable clause with typed parameters, such as an administrative fee, pricing tiers, a purchase commitment or a termination right. An agreement pins each Term by the hash of its definition, so later edits to the library never change an existing agreement. The initial library has sixteen Terms, including UP:Admin-Fee, UP:Tiers, UP:Sales-Reporting, UP:Fee-Disclosure and UP:Overlay. (Source: spec/06-terms/) **Can it calculate what each party owes?** Yes. From the chain of signed events, any evaluator can derive an agreement's status, current tier, contract prices and open obligations at any moment, for example the administrative fee due on a quarter's reported sales. The same events and the same evaluation time always give the same result. (Source: spec/04-inference.md · axiom A4) **Does Universal Paper use a blockchain?** No. It doesn't need a ledger, a network or a server. An agreement can be verified with the specification, a SHA-256 implementation and an Ed25519 verifier. A ledger or a hosted service could carry Universal Paper events, but the language depends on none of them. (Source: spec/00-overview.md §3) **Where do our agreements live?** With the parties. A bundle is plain JSON that you can keep in your contract system, ERP or a file share. Hosted services may store and route bundles for you, but nobody needs one to verify an agreement. (Source: spec/01-domain.md §12) **Do we have to renegotiate existing contracts?** No. The UP:Overlay Term describes a contract you already have, identified by its document hash, so you get computed obligations immediately while the signed document stays the governing one. (Source: spec/06-terms/UP-Overlay.md · spec/07-mapping-guide.md) **How do confidential prices stay private?** Any private value, such as a price, rate, roster or volume, can be replaced by a Seal: a salted SHA-256 commitment. Hashes and signatures cover the sealed form, so a party who sees none of the values still reaches the same verdicts and state hashes. Values are disclosed only to the parties who need them. (Source: spec/01-domain.md §3 · axiom A10) **Can AI agents act on behalf of a party?** Yes, within limits. A Mandate gives an agent its own key and bounds on the event kinds, Roles, Terms and values it may use. An event outside those bounds is invalid on arrival, for every party. (Source: axiom A9) **How does it work with EDI?** Side by side. The mapping guide shows how rosters, eligibility files and the ASC X12 845, 844, 849 and 867 transaction sets correspond to Universal Paper events. Existing identifiers such as GS1 GTIN and GLN, HIBCC HIN and NDC are reused, never replaced. (Source: spec/07-mapping-guide.md) ### For GPOs, suppliers and members **Does the language set or suggest prices or fees?** Never. Universal Paper standardizes process, definitions and compliance mechanics, not economics. No Term carries a default, suggested or typical value for any price, discount, fee, rate, threshold, volume or period. The parties supply every number. (Source: axiom A6 · spec/00-overview.md §7.1) **Is a Universal Paper agreement legally binding?** A Universal Paper agreement must still be a valid contract under the applicable law. Every agreement has a deterministic human-readable rendering suitable for signature, fixed by the same hash the parties sign. The language gives shared, verifiable truth about what was agreed and what state it is in. It does not replace courts. The current draft Terms have not yet been reviewed by counsel. (Source: spec/00-overview.md §7.2) **Does it address the GPO safe harbor in U.S. healthcare?** The fee Terms (UP:Admin-Fee and UP:Fee-Disclosure) can express the written-agreement and disclosure elements that GPO fee arrangements commonly need. The specification encodes no legal conclusion; whether a given agreement satisfies any law is a question for the parties and their counsel. (Source: spec/00-overview.md §7.3) **Is it neutral between GPOs, suppliers and members?** Yes, by design. Rules refer to Roles, never to specific organizations, and every Term reads the same whichever party reads it. The language favors no segment and depends on no company, including its creator. (Source: axiom A7 · spec/08-neutrality-charter.md) ### For developers **How do I try Universal Paper?** Open the Playground to write an agreement in your browser and watch its fingerprint, signatures and obligations update. To work locally, install the Python reference interpreter, which provides the up command (validate, apply, derive, simulate, render, trace, hash). The developer page walks through both. **How is the reference implementation tested?** About 170 tests cover every axiom, transition rule, clause form and Term. A second, independent engine in JavaScript must reproduce every Python trace, rendering and simulation byte for byte, and differential tests compare both engines on tens of thousands of random inputs. The results are published on the conformance section. **Can I write my own implementation?** Yes. The specification is the language, so any implementation that produces the same hashes and the same verdicts for the same events speaks Universal Paper. The example traces (CC0) and test vectors (Apache-2.0) are free to reuse for conformance testing. (Source: spec/03-axioms.md) ### Licensing and governance **What licenses does Universal Paper use?** All open licenses. The specification, Term library, documentation and this website's text are licensed under Creative Commons Attribution 4.0 (CC BY 4.0). The reference interpreter, the JavaScript engine, the JSON Schemas and the tools are licensed under the Apache License 2.0. The example agreements and traces are dedicated to the public domain under CC0 1.0. See Licenses for details. **Can I use Universal Paper commercially?** Yes. All three licenses allow commercial use, modification and redistribution, at no cost. CC BY 4.0 asks you to credit the source (for example, "Universal Paper, created by Uppercentile, CC BY 4.0"), link to the license and say if you changed anything. Apache-2.0 asks you to keep the license and notices with the code, and it includes a patent grant from contributors. CC0 asks for nothing. **Who governs the specification, and how does it change?** Uppercentile is the current steward. Each published version is immutable, and agreements pin one version, so a later change never alters an existing agreement. Changes are proposed through a public, numbered request-for-comment process and recorded in a public changelog. Detailed governance rules are still being defined. (Source: spec/08-neutrality-charter.md §4) **What is the current status of the specification?** Version UP/0.1-draft is a working draft. Until version 1.0, the meaning of the spec and the hashes of Term definitions may change. Every example on this site uses hypothetical parties, identifiers, prices and dates. (Source: spec/00-overview.md §9)