nexart.io

    DRAFT v0

    Status: DraftEnforcement: NoneRuntime Impact: None

    NexArt Builder Manifest

    A declarative specification for app identity and SDK usage attribution.

    Overview

    The Builder Manifest is:

    • • A small public JSON file
    • • Used to declare app identity and SDK usage
    • • Optional
    • • Non-invasive
    • • Static

    Important:

    • • It does NOT enable rewards
    • • It does NOT grant approval
    • • It does NOT modify runtime behavior

    Location & Discovery

    Builders should expose one manifest at:

    /.well-known/nexart.json

    or

    /nexart.json

    Only one manifest per app.

    What Changed in SDK v1.12.0

    SDK v1.12.0 continues optional, passive support for Builder Manifest registration:

    • • SDK now allows optional registration of a Builder Manifest
    • • Manifest is write-only
    • • SDK does not read, expose, validate, or transmit the manifest
    • • Execution, determinism, and outputs are identical with or without a manifest

    Safety Note:

    Registering a Builder Manifest does not enable rewards, tracking, approval, or attribution. It is a declaration of intent only.

    Design Principles

    • • Static
    • • Human-readable
    • • Dependency-free
    • • No secrets
    • • No runtime hooks
    • • No network calls

    JSON Schema (Draft v0)

    {
  "protocol": "nexart",
  "manifestVersion": "0.1",

  "app": {
    "name": "Example Builder App",
    "url": "https://example.app",
    "description": "An AI agent with a verifiable execution trail, built on the NexArt protocol",
    "contact": "hello@example.app"
  },

  "sdk": {
    "package": "@nexart/codemode-sdk",
    "version": "^1.12.0",
    "execution": "deterministic"
  },

  "renderer": {
    "package": "@nexart/ui-renderer",
    "version": "^0.9.1",
    "mode": "preview",
    "optional": true
  },

  "features": {
    "codeMode": true,
    "soundArt": false,
    "staticOnly": false,
    "loopMode": true,
    "experimental": []
  },

  "declaration": {
    "usesOfficialSdk": true,
    "noRuntimeModification": true,
    "noProtocolBypass": true
  },

  "timestamp": "2026-01-01T00:00:00Z"
}

    Field Explanations

    protocol

    Must be "nexart". Identifies the protocol family.

    manifestVersion

    Schema version. Currently "0.1".

    app

    Application metadata: name, URL, description, and contact.

    sdk

    Declares which canonical SDK package and version is used.

    renderer

    Optional. Declares UI renderer package if used for previews.

    features

    Declares which protocol features the app supports. Includes experimental array for future extensibility.

    declaration

    Self-attested compliance statements. Declarative only.

    timestamp

    ISO 8601 timestamp of manifest creation or last update.

    Syntactic Validation Rules (Draft)

    A manifest is considered syntactically valid if:

    • • JSON parses correctly
    • • protocol === "nexart"
    • • Required fields exist
    • • No signatures
    • • No authentication
    • • No enforcement

    What This Enables (Future)

    May be used in the future for:

    • • Builder attribution
    • • Ecosystem discovery
    • • Foundation grants
    • • SDK diagnostics (opt-in)

    Manifests may be discovered by NexArt tools, third-party platforms, or the NexArt Foundation, but discovery implies no endorsement or approval.

    What This Does NOT Do

    • • No rewards
    • • No approvals
    • • No whitelisting
    • • No tracking
    • • No SDK behavior changes

    The NexArt Builder Manifest is a declaration of intent, not a promise.