nexart.iodocs

    Release Notes

    What changed at the current documented baseline across @nexart/ai-execution, @nexart/agent-kit, @nexart/cli, @nexart/policy, @nexart/governed-execution and NexArt Node.

    @nexart/governed-execution 0.4.2

    • Static workflow cycles allowed.
    • Concrete execution remains acyclic.
    • Illegal selected edges now rejected consistently.
    • Native and generic CAGE validation share the same edge resolver.
    • No canonicalisation, certificate-hash, schema or public API change.

    See Migration to SDK 0.4.2.

    NexArt Node 0.30.1

    • Pins Governed Execution SDK 0.4.2.
    • Supports valid cyclic static topology.
    • Preserves fail-closed concrete causal validation.
    • Reports the installed governed SDK version in /version.
    • Adds request-boundary security hardening.
    • Keeps production proxy trust disabled by default.
    • Does not introduce database migrations, CER schema changes, cryptographic algorithm changes or new submission routes.

    Overview

    This page summarizes the current documented baseline. For exact version numbers and how they relate to each other, see Versions.

    @nexart/ai-execution 1.4.0

    This release is additive. It introduces the V2 record schema (ai.execution.v2 snapshot type, cer.ai.execution.v2 bundle type, protocolVersion 1.3.1, jcs-v1 canonicalisation). V1 (ai.execution.v1 / cer.ai.execution.v1) is unchanged and remains fully supported.

    • New V2 API surface: createSnapshotV2, sealCerV2, certifyDecisionV2, verifyCerV2, verifyCerV2Async, verifyAiCerBundleDetailedV2, certifyDecisionFromProviderCallV2.
    • New V2 evidence and protected-set helpers: buildModelEvidenceV2, evidenceString, deriveProtectedSetV2, validateSnapshotV2Schema, decisionRefDomain.
    • New AIEF exports: verifyAief, mapToAiefReason. See AIEF.
    • New confidential V2 helpers: sealConfidentialV2, verifyConfidentialV2 and their async variants, computeCommitment, generateSalt.

    @nexart/agent-kit 0.6.0

    Adds certifyAiExecutionV2(params), returning { bundle, certificateHash, executionId, openings? }. Existing V1 surfaces (wrapTool, certifyDecision, certifyDecisionWithPolicy, createProjectSession, exportProjectBundle, importProjectBundle, verifyProjectBundleDetailed, startWorkflow) are unchanged. They stay V1 forever: wrapTool and startWorkflow step bookkeeping have no V2 counterpart.

    @nexart/cli 1.3.0

    The CLI verifies both cer.ai.execution.v1 and cer.ai.execution.v2 bundles (dual-schema verification). It adds an --aief flag on nexart ai verify, projecting the AIEF v0.2.5 Section 9 result (exit 0 = PASS, exit 1 = FAIL). See AIEF for details.

    @nexart/policy 0.1.0 (new package)

    A new, standalone producer-side package for declarative, data-only policy predicates over captured execution fields. See Policy SDK.

    NexArt Node 0.25.0 (previous baseline)

    /api/attest now dispatches by bundle schema, accepting both cer.ai.execution.v1 and cer.ai.execution.v2. Unknown AI-family schemas (for example cer.ai.execution.v999) fail closed rather than being accepted or best-effort processed.

    What Did Not Change

    Unchanged in this baseline
    • The canonicalisation protocol itself and the set of supported protocolVersion values.
    • projectHash semantics for Project Bundles.
    • certificateHash coverage rules for existing V1 records.
    • CLI exit codes for existing commands.
    • Verification of existing V1 records.

    Next

    • Versions: the four independent version axes and current baseline.
    • AIEF: verifying V1 and V2 bundles.
    • Policy SDK: the new package.