Non-Goals

Not a Prompt Generator

NexArt systems are authored, not prompted. The protocol does not include natural language interfaces, text-to-image generation, or AI-driven creation as core primitives.

Systems are crafted through deliberate parameter selection, code authorship, or structured input composition. The creative act is explicit, not delegated to a model. Implementations may choose to offer assistive tools, but these are outside the protocol's scope.

Not a Style Marketplace

NexArt does not aim to catalogue, trade, or license visual styles. The protocol defines systems, not aesthetic taxonomies.

Systems may produce outputs that share visual characteristics, but the protocol does not model "style" as a first-class concept. Commerce, licensing, or style transfer mechanisms are outside the protocol's concern.

Not a Single Rendering Engine

The protocol does not mandate or provide a single renderer. Multiple renderers are expected and encouraged.

Different implementations may render the same system using different technologies, optimizations, or output formats. The protocol specifies what a system means, not how it must be drawn. Renderer diversity strengthens the ecosystem by preventing dependency on any single codebase.

Not a Platform Lock-In Mechanism

The protocol is designed to outlive any single application, including the current NexArt app at nexart.xyz.

Systems authored today should remain interpretable and renderable by future tools, regardless of which applications exist. The canonical unit format, specification, and reference implementations will be publicly available to ensure that no single vendor controls access to authored work.

Not a DAO or Governance Token System

Protocol governance is not driven by token voting, staking, or decentralized autonomous organization mechanics.

Governance will mature over time through structured stewardship, not financialized decision-making. Contributors and builders influence the protocol through participation, proposals, and demonstrated commitment, not through token holdings.

Not a Blockchain Requirement

NexArt systems are protocol objects regardless of whether they are stored on-chain. The protocol does not require blockchain usage for validity, ownership, or authenticity.

Systems may be stored on-chain, off-chain, or in hybrid arrangements. The protocol is agnostic to storage medium. On-chain representation is one possible use case, not a protocol requirement.

Not Guaranteed Pixel-Perfect Replay in All Contexts

The protocol values honesty about reproducibility. Pixel-perfect determinism is achievable for conforming implementations under specified rendering rules, but it is not universally guaranteed.

Floating-point behavior, hardware differences, audio analysis variations, and unpinned dependencies may cause outputs to differ. The protocol distinguishes between deterministic and best-effort systems precisely because absolute guarantees are not always possible.

Not a Finished Specification

The protocol is a specification-in-progress. Definitions, mode semantics, and rendering rules are evolving.

Early adopters should expect changes. The protocol will stabilize through real-world implementation, feedback, and deliberate iteration. Stability is a goal, not a starting condition.

Not a Standalone Service

The NexArt Protocol is not currently intended to operate as a standalone service or replace the NexArt application.