Protocol Compliance

What Is Protocol Compliance

A protocol-compliant application correctly implements the NexArt Protocol specification. This means:

• Code Mode systems execute identically to the reference implementation
• Determinism guarantees are preserved
• Output can be independently verified
• Systems created in one compliant app work in all others

Compliance is not about branding or affiliation. It is a technical standard that any application can meet by implementing the protocol correctly.

Compliance Levels

There are two levels of protocol compliance, depending on which components an application integrates.

Why Canonical Certification Matters

Level 1 compliance is sufficient for creation and exploration, but Level 2 is required for certification because:

• Determinism verification, Only the Canonical Renderer produces outputs that can be independently verified
• Hash permanence, The output hash becomes the permanent proof of authenticity
• Independent verifiability, Any party can verify that the output matches the original system
• Long-term archival, Canonical outputs are the authoritative record

A preview rendered in the browser may look identical, but it lacks the cryptographic proof that makes verification possible.

On-chain anchoring is one application of certification; the same guarantees apply to simulations, audits, and verification workflows.

Protocol-Compliant Applications

The following applications independently implement the NexArt Protocol at different compliance levels. Inclusion reflects technical compliance, not ownership or endorsement.

Becoming Compliant

If you are building an application that creates or displays NexArt systems, you can achieve compliance by:

1. Integrating the Code Mode SDK for system creation and preview
2. Optionally integrating the Canonical Renderer for on-chain anchoring capabilities
3. Following the protocol specification for system structure and metadata
4. Preserving determinism guarantees in your implementation

There is no certification process. Compliance is self-declared and verifiable, if your outputs match the Canonical Renderer's outputs, you are compliant.

Acceptance Checklist

The canonical renderer adheres to the following behavior guarantees. Compliant clients and integrations should expect these behaviors.

C10 confirms that protocolVersion is lenient (optional) but always resolved and recorded. The canonical renderer defaults to its current version when omitted. C5 and C7 both return 429; quota enforcement (C5) is account-level and distinct from rate limiting (C7).