{
  "tool_id": "art-658-publish-index-head",
  "kernel_id": "art-658-publish-index-head",
  "display_name": "Publish Index Head",
  "tool_version": "1.0.0",
  "mandate_type": "attestation_mandate",
  "purpose": "Publishes one SPEC.md §HEAD-1 head-commit publication event for an index or benchmark's per-stream publication history, so an index administrator's published history (art-646-compile-rebalance-evidence-pack results, or art-647-record-index-correction events) becomes a sequence-numbered, signer-continuous chain instead of a series of unlinked artifacts a reviewer must independently discover and order, mirroring NAV-LINEAGE-BUILD-SPEC.md §3 and art-649-publish-model-risk-head, applied to an index/benchmark administrator's stream (INDEX-LINEAGE-BUILD-SPEC.md §5). HARD FENCE: this node never accepts or handles private key material, the caller signs the head-commit off-node via chaingraph/kernels/_head.mjs's own buildHead/signHead and separately runs its own Ed25519 verification (again via _head.mjs's verifyHeadProof/verifyChain) before calling this node. signature_valid and chain_valid are the caller's own verification claim, asserted and digested into this receipt, exactly like art-562's stage-reference citations, never independently re-derived by this node (the real zkVM guest has no WebCrypto at all, so an in-kernel Ed25519 verify result would not be reproducible across this repo's required execution environments). The one field this node DOES independently recompute is head_hash (pure SHA-256/JCS over the caller-supplied head, never trusted as a caller-asserted value, per SO #34). Backed by ocg-head-file@1 only at first, matching the NAV/model-risk lineage rows; a head-file tip proves the signer's claimed tip, it does not itself detect equivocation (needs ocg-head-tlog@1, a later WU) and is not itself a rebalance-cadence enforcement mechanism. Written for administrators in the post-Regulation-(EU)-2025/914 BMR scope (critical/significant benchmarks) and for SEBI-regulated benchmark administrators; this node makes no BMR/SEBI in-scope determination of its own and makes no claim of BMR or SEBI compliance itself.",
  "control_description": "Publishes one SPEC.md §HEAD-1 head-commit publication event for an index or benchmark's per-stream publication history, so an index administrator's published history (art-646-compile-rebalance-evidence-pack results, or art-647-record-index-correction events) becomes a sequence-numbered, signer-continuous chain instead of a series of unlinked artifacts a reviewer must independently discover and order, mirroring NAV-LINEAGE-BUILD-SPEC.md §3 and art-649-publish-model-risk-head, applied to an index/benchmark administrator's stream (INDEX-LINEAGE-BUILD-SPEC.md §5). HARD FENCE: this node never accepts or handles private key material, the caller signs the head-commit off-node via chaingraph/kernels/_head.mjs's own buildHead/signHead and separately runs its own Ed25519 verification (again via _head.mjs's verifyHeadProof/verifyChain) before calling this node. signature_valid and chain_valid are the caller's own verification claim, asserted and digested into this receipt, exactly like art-562's stage-reference citations, never independently re-derived by this node (the real zkVM guest has no WebCrypto at all, so an in-kernel Ed25519 verify result would not be reproducible across this repo's required execution environments). The one field this node DOES independently recompute is head_hash (pure SHA-256/JCS over the caller-supplied head, never trusted as a caller-asserted value, per SO #34). Backed by ocg-head-file@1 only at first, matching the NAV/model-risk lineage rows; a head-file tip proves the signer's claimed tip, it does not itself detect equivocation (needs ocg-head-tlog@1, a later WU) and is not itself a rebalance-cadence enforcement mechanism. Written for administrators in the post-Regulation-(EU)-2025/914 BMR scope (critical/significant benchmarks) and for SEBI-regulated benchmark administrators; this node makes no BMR/SEBI in-scope determination of its own and makes no claim of BMR or SEBI compliance itself.",
  "declared_inputs": [
    "art-646-compile-rebalance-evidence-pack",
    "art-647-record-index-correction"
  ],
  "declared_outputs": [],
  "kernel_digest": "sha256:193c856ed0239a7110d9d91b252f23f001a5cf0e2297162478ef4dcfe48b1b2c",
  "trust_label": "independently verified: zkVM execution proof (risc0/groth16-bn254)",
  "data_vintage": "2026-09-04",
  "last_validated": "2026-09-04",
  "conformance_fixtures_vendored": true,
  "compute_proof_ready": "ready",
  "wave": 111,
  "source_url": "https://ainumbers.co/chaingraph/art-658-publish-index-head.html",
  "generated_at": "2026-09-05T02:26:40.419Z"
}