nexart.iodocs

    Governed Execution Verification Semantics

    Which Node routes attest, verify statelessly or publish keys, what each one persists or signs, and how receipt and envelope signatures set the trust boundary.

    Route matrix

    SurfaceAuthenticationPersistsSignsIntended use
    POST /api/attestYesYes, default hiddenYesAuthenticated attestation; body is the sealed CER
    POST /v1/cer/verifyNoNoNo (checks a supplied envelope only)Stateless verification; body { bundle }
    GET /.well-known/nexart-node.jsonNoNoNoNode identity and key discovery
    GET /healthNoNoNoOperational health
    GET /versionNoNoNoNode and SDK version discovery
    POST /api/proofs/:certificateHash/unhideYes, ownerUpdates visibilityNoLocal hidden to public; certificate hash unchanged

    Unsupported routes

    /certifyDecision, /verify/{hash} and /v1/attestation/cage-governance are not registered Node routes. Do not confuse an SDK helper named certifyDecision, a Node HTTP route, a portal route on verify.nexart.io, an authenticated attestation and a stateless verification call.

    Version discovery

    GET /version (governed fields)
    {
      "serviceVersion": "0.30.1",
      "governedExecutionSdkVersion": "0.4.2"
    }

    Deployment build metadata such as serviceBuild may also be present.

    Transport status versus verdict

    HTTP 200 from /v1/cer/verify means verification completed. The body's status (verified or failed), reasonCode and per-layer checks determine whether the CER passed.

    Receipt and envelope trust boundaries

    What each signature covers. The receipt signature authenticates the Node's attestation, not the producer. Integrity and authenticity are independent properties.

    See also Verification Semantics and Independent Verification.