Massachusetts Transaction Protocol — Part Three

This document constitutes Part Three of MTP-SPEC-001 — the Licensing and Certification Framework of the Massachusetts Transaction Protocol. It defines the commercial structure through which entities engage with the protocol, the conformance testing regime through which implementations are validated, the certification process through which conforming implementations are authorized for production deployment, and the enforcement mechanisms through which compliance is maintained and violations are remediated.

Every provision in this document carries the institutional authority of LeMay Inc. and derives from the governing instruments of this Corporation: the Certificate of Incorporation, the Technology Constitution, the Declaration of Commonwealth Capitalism, the National Security Compact, and the Curtis License. Where this document references obligations, restrictions, penalties, or enforcement mechanisms, those references carry the full weight of the Curtis License and every federal and state statute enumerated therein — including but not limited to the Economic Espionage Act of 1996, the Defend Trade Secrets Act of 2016, the Computer Fraud and Abuse Act, and the applicable provisions of the United States International Traffic in Arms Regulations and Export Administration Regulations.

The Chief Executive Architect of LeMay Inc. holds final and exclusive authority over every aspect of the licensing, certification, and enforcement framework defined herein. No external entity — no licensee, no implementer, no government, no standards body, no court of arbitration — holds governance authority over the protocol, its specification, its certification regime, or any derivative instrument. Disputes arising under this framework are subject to the exclusive jurisdiction and dispute resolution provisions specified in the Curtis License.

The Massachusetts Transaction Protocol, its specification documents (MTP-SPEC-001 Parts One through Three), the MTP Technical Binding (MTP-BIND-001), the reference implementation, all conformance test suites, all certification materials, and all derivative documentation are the exclusive intellectual property of LeMay Inc., protected under the Curtis License. The Curtis License is the sole instrument through which any rights whatsoever are granted with respect to MTP. No rights exist except those explicitly specified in an executed Order Form or Statement of Work between LeMay Inc. and the licensee.

The Curtis License reserves all rights not explicitly granted. This reservation is absolute and unconditional. No right to use, execute, copy, modify, distribute, sublicense, publicly display, publicly perform, create derivative works from, reverse engineer, decompile, or disassemble any MTP-related intellectual property exists unless that specific right is enumerated in the licensee’s Order Form. The absence of an explicit prohibition does not create an implicit permission. Any act not explicitly authorized is prohibited.

The Curtis License incorporates the national security provisions of the Technology Constitution and the National Security Compact. No MTP license of any tier may be granted to, and no MTP-certified implementation may be deployed by or on behalf of: any foreign person, foreign government, or foreign entity designated as an adversary under applicable United States law; any entity appearing on the Bureau of Industry and Security Entity List, the Office of Foreign Assets Control Specially Designated Nationals List, or any successor designation; any entity domiciled in, controlled by, or operating primarily for the benefit of a nation designated as a foreign adversary under Executive Order or statute; or any entity that LeMay Inc., in its sole and unreviewable discretion, determines poses a risk to the national security interests of the United States.

These restrictions are not subject to waiver, exception, or appeal. They are constitutional provisions of this Corporation that supersede commercial interest in every instance. A prospective licensee that falls within any prohibited category will be denied a license regardless of the commercial value of the engagement. A certified licensee that subsequently falls within a prohibited category — through acquisition, reorganization, change of domicile, or designation by a government authority — will have its certification revoked immediately and its license terminated without cure period.

The MTP specification, the reference implementation, the conformance test suites, the certification criteria, and all associated documentation constitute trade secrets of LeMay Inc. under the Defend Trade Secrets Act and applicable state trade secret statutes. Every licensee, at every tier, is bound by confidentiality obligations that prohibit disclosure of trade secret material to any third party except as required for the licensee’s own conforming implementation and as expressly permitted in the Order Form. Misappropriation of MTP trade secrets is subject to the full range of civil and criminal remedies available under federal and state law, including injunctive relief, actual damages, exemplary damages up to twice the amount of actual damages, and reasonable attorney’s fees.

Access to the Massachusetts Transaction Protocol is structured in three tiers, each granting a defined scope of rights and imposing a defined scope of obligations. The tiers are cumulative: a Production License includes all rights granted by the Development License, which includes all rights granted by the Evaluation License. No licensee may hold rights at a higher tier without first satisfying the obligations of all lower tiers.

1. Scope of Rights

The Evaluation License grants the licensee the right to read and inspect the MTP-SPEC-001 specification documents, the MTP Technical Binding, and the reference implementation source code, solely for the purpose of evaluating whether to pursue a Development License and subsequent implementation. The Evaluation License grants no right to execute the reference implementation in any environment — neither production, staging, development, nor testing. It grants no right to copy, excerpt, or reproduce any portion of the specification or source code except as reasonably necessary for internal evaluation memoranda that remain subject to the confidentiality obligations of the Curtis License. It grants no right to create derivative works, incorporate any portion of the specification into the licensee’s own documentation, or publicly reference specific technical details of the protocol beyond what LeMay has published in its own public materials.

2. Duration and Termination

The Evaluation License is granted for a fixed evaluation period of ninety days from the date of execution. The evaluation period may be extended once, for an additional ninety days, at LeMay’s discretion upon written request by the licensee. Upon expiration or termination of the Evaluation License, the licensee must destroy or return all copies of the specification and reference implementation source code in its possession, and must certify such destruction or return in writing within thirty days.

3. Fees

The Evaluation License fee is specified in the Order Form and is non-refundable. The fee reflects the value of the intellectual property made available for inspection and the administrative cost of onboarding, access provisioning, and compliance monitoring during the evaluation period. The Evaluation License fee is credited against the Development License fee if the licensee proceeds to the Development tier within thirty days of the Evaluation License’s expiration.

1. Scope of Rights

The Development License grants the licensee all rights of the Evaluation License plus the following: the right to execute the reference implementation in non-production development and testing environments operated by the licensee; the right to build a Conforming Implementation using the specification and reference implementation as authoritative guides; the right to execute the conformance test suite against the licensee’s implementation in development and testing environments; and the right to submit the implementation to LeMay for certification.

The Development License does not grant the right to deploy any implementation in a production environment, the right to process live transactions, the right to represent any implementation as MTP-certified before certification has been granted, the right to modify the specification or the reference implementation, the right to extend the protocol without LeMay’s approval through the Extension Specification process, or the right to distribute any portion of the specification, reference implementation, or test suite to any third party.

2. Development Environment Restrictions

Development and testing environments operated under the Development License must be isolated from production systems. No live transaction data — data involving real principals, real payment instruments, or real value exchange — may be processed in a development environment. The licensee must maintain network and access controls that prevent any development environment from communicating with the MTP production network or with any Certified Implementation’s production endpoints. Violation of this restriction constitutes a material breach of the Curtis License and results in immediate termination of the Development License with no cure period.

3. Duration and Fees

The Development License is granted for a fixed development period specified in the Order Form, typically twelve months. Extensions may be negotiated. The Development License fee is specified in the Order Form and is structured as an annual fee payable in advance. The fee reflects the value of the intellectual property and tooling made available, the cost of LeMay’s technical support during the development period, and the administrative cost of conformance test suite access and certification preparation support.

1. Scope of Rights

The Production License grants the licensee all rights of the Development License plus the following: the right to deploy a Certified Implementation in production environments; the right to process live MTP transactions involving real principals, real payment instruments, and real value exchange; the right to represent the implementation as MTP-certified and to use the MTP Certification Mark in connection with the implementation; and the right to register the implementation’s Capability Manifests with the LeMay authoritative index and any federated discovery indexes.

The Production License is contingent on active certification status. If certification is revoked for any reason, the Production License is automatically suspended and the licensee must cease all live transaction processing within the timeframe specified in the revocation notice. The Production License is reinstated only upon successful recertification.

2. Transaction Reporting

Production licensees must provide LeMay with periodic transaction reports as specified in the Order Form. Transaction reports include aggregate transaction volume, aggregate value exchanged, error rates by error classification, verification outcomes by outcome type, and any conformance deviations detected by the implementation’s self-monitoring systems. Transaction reports do not include personally identifiable information of principals or the substantive content of transactions. LeMay uses transaction reports for conformance monitoring, protocol health assessment, and fee calculation. The reporting frequency and format are specified in the Order Form.

3. Fees

The Production License fee structure consists of two components. The annual base fee, payable in advance, grants the right to operate a Certified Implementation in production. The transaction fee, calculated as a percentage of the value exchanged through the licensee’s Certified Implementation, is payable in arrears on the schedule specified in the Order Form. The transaction fee percentage, the minimum annual transaction fee, and the fee calculation methodology are specified in the Order Form and may vary by licensee based on projected volume, strategic significance, and negotiated terms. LeMay reserves the right to audit the licensee’s transaction records to verify fee calculations, subject to the audit provisions of the Curtis License.

4. Duration and Renewal

The Production License is granted for an initial term specified in the Order Form, typically thirty-six months. Renewal is subject to successful recertification, payment of all outstanding fees, and the absence of any unresolved compliance violations. LeMay reserves the right to modify the fee structure at renewal, subject to the notice provisions specified in the Order Form. The licensee may terminate the Production License at any time upon written notice, subject to the payment of all fees accrued through the termination date and the wind-down obligations specified in Section IX.

Certification is the process by which LeMay verifies that an implementation conforms to the normative requirements of MTP-SPEC-001 Part Two and is authorized for production deployment. Certification is mandatory: no implementation may process live MTP transactions without active certification. Certification is granted at LeMay’s sole discretion — satisfaction of the conformance test suite is necessary but not sufficient. LeMay evaluates the implementation’s overall fitness for production deployment, including factors beyond automated test results.

Before submitting an implementation for certification, the licensee must hold an active Development License; must have executed the complete conformance test suite against the implementation with all mandatory tests passing; must have resolved all conformance deviations identified during development; must have documented all SHOULD recommendation deviations and their rationales; must have completed an internal security review of the implementation’s cryptographic configuration; and must have prepared the certification submission package as defined in Section IV-C.

The MTP Certification Test Suite is the authoritative instrument through which conformance is verified. The test suite is maintained by LeMay and updated with each protocol version. The test suite is provided to Development License holders as part of their license entitlement. The test suite source code is protected under the Curtis License and may not be disclosed, distributed, or modified.

1. Test Categories

The test suite is organized into seven categories corresponding to the seven protocol layers, plus three cross-cutting categories that verify system-level properties. The Identity Layer test category verifies Agent identity creation, Principal-to-Agent delegation, credential issuance, credential verification, credential revocation, selective disclosure, zero-knowledge proof generation and verification, and delegation chain validation. The Discovery Layer test category verifies Capability Manifest publication, indexing, querying, Offer revocation propagation, federated discovery across multiple indexes, and Request-to-Offer matching. The Negotiation Layer test category verifies single-round negotiation, multi-round negotiation, conditional negotiation, multi-party negotiation, negotiation timeout handling, round exhaustion handling, and proposal signature verification. The Commitment Layer test category verifies Transaction Mandate generation, multi-party signature collection, conditional mandate activation, precondition monitoring, mandate expiration, and mandate immutability enforcement. The Settlement Layer test category verifies settlement initiation, settlement confirmation, settlement reversal, settlement atomicity, payment rail adapter interface compliance, and multi-rail fallback. The Verification Layer test category verifies attestation-based verification, evidence-based verification, computation-based verification, third-party verification, dispute initiation, partial fulfillment handling, and Receipt generation. The Attribution Layer test category verifies Shapley value calculation for transactions involving two through ten parties, approximate Shapley computation for transactions exceeding ten parties, attribution record generation, and attribution record verification.

The three cross-cutting test categories are as follows. The Interoperability category verifies that the implementation can execute a complete transaction — from Discovery through Attribution — with the reference implementation, without any prior coordination, custom configuration, or out-of-band agreements. The State Machine category verifies that the implementation’s transaction state machine matches the normative state machine defined in Part Two Section IV, including all state transitions, error-triggered transitions, and terminal state handling. The Cryptographic Compliance category verifies that the implementation uses only the mandatory cryptographic families and algorithms specified in Part Two Section VIII, that key generation meets the entropy requirements, that signature generation and verification produce correct results across all protocol objects, and that the Algorithm Negotiation mechanism functions correctly.

2. Test Result Classification

Test results are classified into four outcomes. Pass indicates that the implementation’s behavior matches the expected behavior for the test case. Fail indicates that the implementation’s behavior deviates from the expected behavior on a MUST or SHALL requirement. A single Fail result on any mandatory test renders the implementation non-conforming. Advisory Fail indicates that the implementation’s behavior deviates from the expected behavior on a SHOULD recommendation. Advisory Fail results do not automatically render the implementation non-conforming but are evaluated during LeMay’s discretionary review. Skip indicates that a test case was not executed, which is permitted only for tests in the MAY-permission category; skipping a mandatory or recommended test is itself a Fail.

3. Minimum Conformance Threshold

The minimum conformance threshold for certification is: one hundred percent pass rate on all mandatory tests (those verifying MUST and SHALL requirements); ninety percent pass rate on recommended tests (those verifying SHOULD recommendations), with all Advisory Fail results documented and justified; and successful completion of the Interoperability category’s full transaction demonstration with the reference implementation. Implementations that meet the minimum threshold proceed to LeMay’s discretionary review. Implementations that do not meet the minimum threshold are rejected and must remediate before resubmission.

The certification submission package must contain: the complete test suite execution report, including pass, fail, advisory fail, and skip counts for every test category; the implementation’s architectural documentation, describing how each of the seven protocol layers is implemented; the implementation’s cryptographic configuration documentation, identifying the specific algorithms, parameter sets, key sizes, and random number generator sources used; the SHOULD deviation report, documenting every SHOULD recommendation deviation with its rationale; the security review report from the licensee’s internal security review; and the deployment architecture documentation, describing the production environment in which the implementation will operate, including network topology, access controls, key management infrastructure, and audit trail storage.

Upon receipt of a conformance-threshold-passing submission package, LeMay conducts a discretionary review that evaluates factors beyond automated test results. The discretionary review considers: the quality and completeness of the architectural documentation; the robustness of the implementation’s cryptographic configuration relative to current threat intelligence; the adequacy of the deployment architecture’s security controls; the persuasiveness of the SHOULD deviation rationales; the licensee’s organizational capacity to maintain the implementation through future protocol versions; and any strategic or national security considerations relevant to the licensee’s deployment context.

The discretionary review is conducted by LeMay’s certification team and the outcome is communicated to the licensee in writing. Possible outcomes are: Certified, indicating that the implementation is approved for production deployment and a Production License may be executed; Certified with Conditions, indicating that the implementation is approved subject to the licensee’s completion of specified remediation actions within a defined timeframe; and Denied, indicating that the implementation is not approved for production deployment, with a written explanation of the deficiencies and guidance for remediation and resubmission.

The discretionary review is not an appeal of the automated test results. It is an additional evaluation layer that considers factors the test suite cannot measure. LeMay’s discretionary review decision is final. There is no appeal process. A licensee that receives a Denied outcome may remediate the identified deficiencies and resubmit, subject to the terms and timeline specified in the denial communication.

Certification is not permanent. Production licensees must undergo periodic recertification to maintain their authorization to process live transactions. Recertification ensures that implementations remain conforming as the protocol evolves, as the threat landscape changes, and as the implementation itself is modified through maintenance and feature development.

Recertification is required at the following intervals and trigger events. Annual recertification is mandatory for all Production License holders, conducted on the anniversary of the initial certification grant. Version recertification is required within the migration window of any Major protocol version release, as specified in Part Two Section XII. Event-triggered recertification is required when the licensee makes material changes to the implementation’s architecture, cryptographic configuration, or deployment environment. The licensee must notify LeMay of material changes within thirty days and must complete event-triggered recertification within ninety days of the change.

The recertification process mirrors the initial certification process with the following modifications. The test suite execution must use the current version of the certification test suite, which may include new tests added since the previous certification. The submission package must include a change log documenting all modifications to the implementation since the previous certification. The discretionary review is expedited for implementations with a clean compliance history; implementations that have received compliance notices or enforcement actions during the certification period undergo full discretionary review.

If a Production licensee’s recertification deadline arrives and the recertification process has not been completed, a grace period of thirty days is granted during which the licensee may continue to process live transactions while completing recertification. If recertification is not completed within the grace period, the certification is suspended and the licensee must cease live transaction processing until recertification is successfully completed. Transactions initiated before the suspension that have not yet reached a terminal state must be allowed to complete, but no new transactions may be initiated.

The MTP Certification Mark is a registered trademark of LeMay Inc. that identifies implementations that have been certified through the process defined in Section IV. The Certification Mark may be used only by Production License holders with active, non-suspended certification. Use of the Certification Mark by any other party, or use by a certified party in a manner not authorized by the Mark Usage Guidelines, constitutes trademark infringement and a material breach of the Curtis License.

The Certification Mark must be displayed with the certification version number and certification date, in the format specified by the Mark Usage Guidelines published by LeMay. The Mark must not be displayed in any context that implies endorsement of the licensee’s products or services beyond the specific assertion that the identified implementation conforms to MTP. The Mark must be removed from all materials within forty-eight hours of certification suspension or revocation.

The Extension Specification process is the sole mechanism by which the MTP protocol may be extended. Extensions are governed exclusively by LeMay. No licensee, implementer, or external party holds the authority to extend the protocol unilaterally. An implementation that incorporates an unapproved extension is non-conforming, and the deployment of a non-conforming implementation in production constitutes a material breach of the Production License.

Any Development or Production licensee may submit an Extension Request to LeMay’s protocol governance team. The Extension Request must contain: a description of the proposed extension and the problem it addresses; the proposed schema changes, including new fields, new Value Taxonomy subcategories, new negotiable dimensions, new verification methods, or new payment rail adapters; an impact analysis describing how the extension interacts with the core specification and with previously approved extensions; a backward compatibility analysis demonstrating that the extension does not break existing Conforming Implementations that do not support the extension; and a security analysis demonstrating that the extension does not weaken the protocol’s cryptographic guarantees or introduce new attack surfaces.

LeMay evaluates each Extension Request against four criteria. Architectural consistency: the extension must be coherent with the protocol’s design principles, must respect the separation of layers, and must not circumvent or undermine the normative requirements of the core specification. Security integrity: the extension must not introduce vulnerabilities, must not weaken cryptographic guarantees, and must not create new vectors for unauthorized access, data leakage, or transaction manipulation. Strategic alignment: the extension must serve the protocol’s long-term strategic purpose as defined by LeMay’s architectural vision. Implementability: the extension must be specified with sufficient precision that it can be implemented without ambiguity and tested through additions to the conformance test suite.

LeMay’s evaluation decision is final. Approved extensions are published as LeMay Extension Specifications, assigned an Extension Identifier and a compatibility version, and incorporated into the conformance test suite. Denied extensions may be resubmitted with modifications addressing the deficiencies identified in the denial. LeMay is under no obligation to approve any extension, regardless of the number of licensees requesting it, the commercial demand for it, or the technical merit of the proposal.

The enforcement framework exists to ensure that the MTP protocol operates with the integrity, security, and trustworthiness that its architecture demands. Enforcement is not punitive. It is protective — it protects the protocol’s users, the protocol’s reputation, and the protocol’s strategic value from implementations that fail to meet the standard the protocol requires.

LeMay monitors compliance through three mechanisms. Transaction reporting, as specified in Section III-C-2, provides aggregate operational data that LeMay analyzes for patterns indicative of conformance deviations. Certification test suite self-monitoring, which Production licensees are required to execute on a periodic schedule specified in the Order Form, produces conformance reports that are submitted to LeMay. Field reports from counterparty Agents that encounter unexpected behavior when transacting with a Certified Implementation are submitted to LeMay through the protocol’s error reporting channel.

When LeMay identifies a potential conformance deviation through any monitoring mechanism, LeMay issues a Compliance Notice to the licensee. The Compliance Notice identifies the suspected deviation, cites the normative requirement believed to be violated, and specifies a remediation deadline. Compliance Notices are classified into three severity levels. A Critical Compliance Notice addresses deviations that pose an immediate risk to transaction integrity, security, or principal safety — such as cryptographic failures, unauthorized extensions in production, or settlement processing errors. The remediation deadline for Critical notices is seventy-two hours. A Standard Compliance Notice addresses deviations that affect conformance but do not pose immediate risk — such as audit trail gaps, reporting irregularities, or SHOULD recommendation regressions. The remediation deadline for Standard notices is thirty days. An Advisory Compliance Notice addresses observations that are not yet deviations but indicate drift toward non-conformance — such as increasing Advisory Fail counts in self-monitoring reports. Advisory notices carry no mandatory remediation deadline but are considered in recertification evaluations.

Certification suspension is the temporary withdrawal of the licensee’s authorization to process live transactions. Suspension is triggered by: failure to remediate a Critical Compliance Notice within the seventy-two-hour deadline; failure to remediate a Standard Compliance Notice within the thirty-day deadline after one extension has been granted and exhausted; failure to complete recertification within the grace period specified in Section V-C; or discovery of a security vulnerability in the implementation that LeMay determines poses immediate risk to the MTP network.

During suspension, the licensee must cease initiating new transactions. Transactions already in progress must be allowed to reach a terminal state. The licensee’s Capability Manifests must be withdrawn from all discovery indexes. The Certification Mark must be removed from all materials. Suspension is lifted upon successful remediation of the triggering condition and, at LeMay’s discretion, successful completion of an expedited recertification.

Certification revocation is the permanent withdrawal of the licensee’s certification. Revocation terminates the Production License. Revocation is triggered by: a pattern of repeated compliance failures demonstrating systemic inability or unwillingness to maintain conformance; deployment of the implementation to a prohibited entity or territory as defined in Section II-B; material breach of the Curtis License, including unauthorized distribution, modification, or disclosure of protected materials; incorporation of unapproved extensions in a production deployment; fraud in the certification or recertification process, including falsification of test results or misrepresentation of the implementation’s architecture; or any action that LeMay determines poses an unacceptable risk to the integrity of the MTP protocol or the safety of its users.

Revocation is communicated in writing with a detailed statement of the grounds. Revocation is effective immediately upon delivery of the notice. There is no cure period for revocation. The licensee must cease all live transaction processing within twenty-four hours of receiving the revocation notice, must withdraw all Capability Manifests from all discovery indexes, must remove the Certification Mark from all materials, and must destroy or return all copies of the specification, reference implementation, and test suite. The licensee’s revocation is recorded in the MTP Certification Registry, which is publicly queryable, and the revocation record is permanent.

A revoked licensee may apply for a new Evaluation License after a cooling-off period of not less than twelve months from the date of revocation. The new application is evaluated on its own merits, and the prior revocation is considered as a factor in the discretionary review. A second revocation of the same entity results in a permanent bar from MTP licensing.

When a Production License terminates — whether through voluntary termination, expiration without renewal, certification suspension that is not cured, or certification revocation — the licensee must execute the following wind-down obligations in sequence.

The licensee must cease initiating new transactions immediately upon the effective date of termination. Transactions already in progress at the time of termination must be allowed to reach a terminal state, with the licensee maintaining conforming behavior throughout the wind-down period. The wind-down period for in-progress transactions is sixty days from the effective date of termination; any transaction that has not reached a terminal state within sixty days is transitioned to the Failed state with an appropriate error record.

The licensee must withdraw all Capability Manifests from all discovery indexes within forty-eight hours of the effective date of termination. The licensee must remove the Certification Mark from all materials, marketing collateral, technical documentation, and public-facing interfaces within forty-eight hours. The licensee must submit a final transaction report covering all transactions processed between the last regular reporting period and the effective date of termination.

The licensee must destroy or return all copies of the MTP specification documents, the reference implementation source code, the conformance test suite, and all certification materials within thirty days of the effective date of termination. The licensee must certify such destruction or return in writing. Audit trail records generated during the Production License period must be retained for the duration specified in the Order Form, notwithstanding the termination of the license, because audit trail records may be required for dispute resolution of transactions processed before termination.

All fees accrued through the effective date of termination, including transaction fees for the final reporting period, are due and payable within thirty days of the final transaction report submission. Termination of the license does not relieve the licensee of any payment obligation incurred during the license term.

Disputes between LeMay and a licensee arising under this framework are subject to the dispute resolution provisions of the Curtis License. The governing law is the law of the Commonwealth of Massachusetts. The exclusive venue for litigation is the state and federal courts sitting in Middlesex County, Massachusetts. Arbitration is not available for disputes involving national security provisions, certification revocation, or alleged misappropriation of trade secrets. For all other disputes, the Curtis License specifies binding arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules, with the arbitration seated in Boston, Massachusetts.

Disputes between transacting Agents within the MTP protocol — that is, disputes arising from the execution of transactions governed by the protocol, as distinct from disputes between LeMay and its licensees — are resolved through the dispute resolution procedure specified in the Terms of the relevant Transaction Mandate, as defined in Part Two Section III-F-2. The protocol provides the framework for dispute resolution but does not itself adjudicate disputes between transacting parties. The licensee’s Production License requires the licensee to implement the dispute resolution mechanisms specified in the protocol and to honor the outcomes of those mechanisms.

LeMay maintains the MTP Certification Registry — a publicly queryable database of all Certified Implementations, their certification status, their certification version, their certification date, and their licensee identity. The Certification Registry serves two functions: it allows any Agent to verify in real time that a counterparty’s implementation is certified before initiating a transaction, and it provides the market with transparency about the certification status of every implementation in the MTP ecosystem.

The Certification Registry records the following for each Certified Implementation: the licensee’s legal name and jurisdiction; the implementation’s unique Certification Identifier; the protocol version against which the implementation was certified; the certification date; the current certification status (Active, Suspended, or Revoked); the date and reason for any status change; and the implementation’s supported extensions with their version numbers. The Registry does not record proprietary technical details of the implementation; it records only the information necessary for counterparty verification and market transparency.

The Identity Layer of the MTP protocol integrates with the Certification Registry: a Conforming Implementation SHOULD verify a counterparty’s certification status through the Registry before entering the Negotiation Layer. This verification is RECOMMENDED, not REQUIRED, because the protocol must remain operational when the Registry is temporarily unavailable. However, implementations that skip Registry verification accept the risk of transacting with a suspended or revoked counterparty, and LeMay accepts no liability for transactions conducted without Registry verification.

This document completes MTP-SPEC-001. Three parts, together constituting the founding specification of the Massachusetts Transaction Protocol. Part One declared the strategic case — the vacancy in the agent economy’s infrastructure, the indictment of existing protocols, the scope of universal value exchange, and the governance posture under which this protocol will operate for the duration of this Corporation’s existence. Part Two declared the architecture — four primitives, seven layers, a deterministic state machine, nine Value Taxonomy categories, a post-quantum cryptographic foundation, and conformance requirements sufficient to guarantee interoperability between independently developed implementations. Part Three, this document, declares the commercial and enforcement regime — three license tiers, a certification process built on a ten-category conformance test suite with discretionary review, recertification requirements, an extension governance framework, and enforcement mechanisms ranging from advisory notices to permanent revocation.

Two companion documents remain. MTP-BIND-001, the Technical Binding, targeted for the third quarter of 2026, will designate the specific technologies that implement the architectural requirements: the DID method, the Verifiable Credential format, the serialization format, the transport protocol, the cryptographic parameter sets, the wire-level message schemas, the normative JSON schemas for all four primitives, the complete MTP Error Code Registry, and the mandatory quality dimensions for each Value Taxonomy category. The MTP Reference Implementation, developed in parallel with the Technical Binding in TypeScript and Rust, will provide the canonical implementation against which all Certified Implementations are tested.

The specification is now complete. The architecture is declared. The commercial framework is defined. The enforcement regime is established. What remains is construction — the engineering that will transform this specification from a document into infrastructure, from a declaration into a protocol that governs how autonomous entities exchange value across the machine economy.

The protocol is the foundation. The specification is the blueprint. The Curtis License is the wall. The certification regime is the gate. LeMay is the gatekeeper. And the construction begins now.

End of Part Three

End of MTP-SPEC-001