OpenChainGraph Suite · CONTRACT A3 · arch #5

Index Rebalance Evidence Publication Check

Prove an index rebalance in five independent runs plus a session receipt: record a caller-declared constituent set as of a stated date (ART-557), compute a weight per constituent under a stated methodology from caller-supplied input rows (ART-645), compile one rebalance event into a pack diffing current against prior constituent and weight rows and citing the step 1 and step 2 receipts (ART-646), publish the pack as one sequence-numbered head-commit event for the index stream (ART-658), closing with a session receipt aggregating the run execution hashes (CRY-05). Every constituent row, input row, methodology, and verification claim is caller-supplied and asserted, never fetched; each run is an independent recompute from its own declared inputs. This chain attests declared inputs in sequence, it does not verify them against market data, and it is not a live index feed.

OpenChainGraph · 5 Steps cryptographic mandate Hash-Anchored §4 chain_depth:5 Client-Side · Zero PII
Chain Topology: Record Index Constituents → Compute Index Weights → Compile Rebalance Evidence Pack → Publish Index Head → Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 5 Steps
1 ROOT node
Record Index Constituents art-557-record-index-constituents
Records a caller-declared constituent set as of a stated date, with its own execution_hash. Every constituent row, the eligibility-criteria description, and the selection universe size are caller-supplied and asserted, never fetched. This step attests that a declared set exists exactly as stated, never whether the criteria were applied correctly against market data.
MCP Call · record_index_constituents
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "record_index_constituents",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 STAGE 2 node
Compute Index Weights art-645-compute-index-weights
Computes a weight per constituent under a stated methodology from caller-supplied input rows, with weight_sum_check within 1e-9 of 1.0, and its own execution_hash. The step 2 run cites the step 1 receipt by execution_hash plus tool_id as a receipt citation; it does not re-derive the step 1 constituent set, and it does not verify that its input list matches any particular constituent-set attestation.
MCP Call · compute_index_weights
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_index_weights",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 STAGE 3 node
Compile Rebalance Evidence Pack art-646-compile-rebalance-evidence-pack
Compiles one rebalance event into a pack: current and prior constituent and weight rows, diffed into additions, removals and weight deltas, citing the step 1 and step 2 receipts by execution_hash plus tool_id. The step 1 to step 2 to step 3 links are receipt citations, not declared graph edges. The pack does not re-run or independently re-derive the cited arithmetic, and a reviewer must check the cited hashes against the step 1 and step 2 receipts as a manual check.
MCP Call · compile_rebalance_evidence_pack
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compile_rebalance_evidence_pack",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
4 STAGE 4 node
Publish Index Head art-658-publish-index-head
Publishes one sequence-numbered head-commit event for the index stream, with head_hash independently recomputed by SHA-256 and seq and prev_head_hash checked. signature_valid and chain_valid are the caller's own verification claim, asserted and digested into this receipt; this node never handles private key material and never itself runs an Ed25519 verify, and head_hash is not proof of signing. A head-file tip proves the signer's claimed stream tip at that seq; it does not detect a signer publishing conflicting levels elsewhere.
MCP Call · publish_index_head
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "publish_index_head",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
5 TERMINAL node
Agent-Action Audit-Trail Aggregator cry-05-agent-action-audit-trail-aggregator
Produces session_receipt_root, the Merkle root over the run execution hashes (final stage)
MCP Call · aggregate_execution_receipts
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "aggregate_execution_receipts",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: For the example index, what weights follow from the declared market caps, and what does the rebalance pack record?
Run the AINumbers MCP tool `run_chain` with {"chain":"index-rebalance-evidence-publication"} and read `art-646-compile-rebalance-evidence-pack.weight_deltas`.
Re-run with `inputs` for `art-646-compile-rebalance-evidence-pack`, reusing the values that result echoed, with `current` changed so a different current constituent set and weight set are declared. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/index-rebalance-evidence-publication.html