OpenChainGraph Suite · CONTRACT A3 · arch #5

NAV Error Disclosure Evidence Pack

A fund administrator recomputes a NAV per share from declared holdings, accruals, liabilities and shares, tests whether the difference against the published NAV is material under a declared policy, and bundles the two receipts into a disclosure evidence pack shaped for CSSF Circular 24/856, citing each receipt by execution_hash. Every price, FX rate, accrual input, erroneous NAV and correction fact is caller-supplied and asserted, never fetched; each run is an independent recompute or citation from its own declared inputs. The pack cites receipts only, never recomputes a NAV and never re-derives a materiality verdict, and it makes no claim of CSSF 24/856 compliance and is not a regulatory filing. The half-cent and 1 percent figures in art-374 are industry conventions. They are neither codified rules nor circular thresholds. Special-report checklist, UCITS and UCI Part II only, CSSF Circular 24/856 point 138: a special report is required only where the error relates to a UCITS or a UCI Part II and total compensation (to the UCI plus all investors) exceeds EUR 50,000 or compensation to one single investor exceeds EUR 5,000; the special report reviews all the errors. Below both thresholds for a UCITS or UCI Part II, the separate report carries a sample-based review of the errors. Table 9 rows for SIF and SICAR funds: above one or both thresholds, the separate report carries a sample-based review of the errors and no special report is issued; below both thresholds, the separate report carries a sample-based review of the errors. Table 9 rows for closed-ended funds: a significant NAV calculation error in a closed-ended UCI, whether UCITS Part II or SIF and SICAR, carries no intervention under Table 9, with the footnote that the approved statutory auditor verifies, as part of its statutory audit, that the NAV accurately reflects the value of the UCI assets and liabilities calculated in line with the constitutive documents or the prospectus. Do not extend the UCITS and UCI Part II special-report trigger to SIF, SICAR or closed-ended funds. Notification window, CSSF Circular 24/856 point 158: notification to the CSSF is due 4 to 8 weeks after detection, for both compensation cases and no-compensation cases; the same window applies to both, with no different window for either case. Out of scope: fair-value opinions, independent valuations, determinations that a NAV error legally occurred, evidence that declared inputs were accurate, and tax or legal advice are all outside this chain.

OpenChainGraph · 4 Steps cryptographic mandate Hash-Anchored §4 chain_depth:4 Client-Side · Zero PII
Chain Topology: Recompute Fund NAV → Test NAV-Error Materiality → Compile NAV-Error Evidence Pack → Agent-Action Audit-Trail Aggregator
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 4 Steps
1 ROOT node
Recompute Fund NAV art-373-recompute-fund-nav
Recomputes the NAV per share from caller-supplied holdings, accruals, liabilities and shares outstanding, with component breakdown and input digests, and its own execution_hash. Every price, FX rate and accrual input is supplied and asserted by the caller, never fetched. This run attests the arithmetic over declared inputs only, never a fair-value opinion and never whether the declared prices are accurate.
MCP Call · recompute_fund_nav
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "recompute_fund_nav",
    "arguments": {}
  },
  "id": 1
}
↓
2 STAGE 2 node
Test NAV-Error Materiality art-374-test-nav-error-materiality
Compares an erroneous NAV per share against the corrected NAV per share cited from the step 1 output_payload nav_per_share, under a declared materiality policy, and outputs a material or immaterial verdict with affected-period math and its own execution_hash. The half-cent absolute threshold and the 1 percent relative threshold are industry conventions, stated as such in the kernel. This run attests the arithmetic of the error comparison under the declared policy, never an accounting opinion and never a determination that a fund must reprocess.
MCP Call · test_nav_error_materiality
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "test_nav_error_materiality",
    "arguments": {}
  },
  "id": 1
}
↓
3 STAGE 3 node
Compile NAV-Error Evidence Pack art-660-compile-nav-error-evidence-pack
Bundles the step 1 and step 2 receipts into a CSSF Circular 24/856-shaped disclosure pack, citing each receipt by execution_hash plus tool_id and echoing the step 2 materiality verdict, error and declared policy verbatim. HAND COPY: the caller copies the NAV per share, the erroneous NAV, and the art-374 output_payload by hand into the art-660 run. Nothing is auto-joined. The pack performs zero NAV recomputation and zero materiality-threshold arithmetic of its own, it does not re-verify that the supplied art-374 output_payload corresponds to the cited execution_hash, it makes no claim of CSSF 24/856 compliance, and it is not a regulatory filing. Correction and notification fields are caller-supplied and asserted.
MCP Call · compile_nav_error_evidence_pack
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compile_nav_error_evidence_pack",
    "arguments": {}
  },
  "id": 1
}
↓
4 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
}
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: A published NAV looks a tenth of a cent high against the recomputation. Does the declared policy call the error material, and what does the evidence bundle cite?
Run the AINumbers MCP tool `run_chain` with {"chain":"nav-error-disclosure-evidence-pack"} and read `art-374-test-nav-error-materiality.materiality_verdict`.
Re-run with `inputs` for `art-374-test-nav-error-materiality`, reusing the values that result echoed, with `corrected_nav_per_share` changed so the corrected NAV is 9.90. 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/nav-error-disclosure-evidence-pack.html