ART-558 · NAV Calc Receipt Chain, Upstream Lineage
Record Fund Positions
Gives a fund's declared positions snapshot, as of a stated valuation date, its own citable execution_hash: the upstream input-receipt that a NAV calculation currently hashes internally, and that a separate wiring step can instead cite via an optional positions_ref rather than re-declaring the same holdings. Accepts a supplied list of holdings (security, quantity, currency) and a declared shares_outstanding, and attests that this exact declared snapshot exists for this exact fund and date. Holdings are echoed in this receipt in cleartext by design: the point is a citable hash over the declared snapshot, not a commitment that hides it.
Positions Snapshot Lineage
Supplied Holdings, Never Fetched
Not a Custodian Verification
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
What this does NOT prove
Every holding row and shares_outstanding here are supplied by you and merely asserted: this tool performs zero custodian, fund-administrator, or market-data lookups (zero-egress, no network calls of any kind, never a live position feed). It attests that a declared positions snapshot exists exactly as stated for the given fund and date. This is never a verification against a custodian or fund-administrator record, and never a NAV or pricing computation (that is art-373-recompute-fund-nav and a sibling pricing-inputs node). A restated snapshot cites the prior artifact's execution_hash via the standard OpenChainGraph supersedes field: no separate status registry.
Fund & Valuation Date
Holdings (JSON array: security_id, quantity, currency)
–
Holding Count
Shares Outstanding
–
Valuation Date
Holdings
| Security | Quantity | Currency |
|---|
What was NOT proven
Compliance Flags
Provenance
The declared fund_id, valuation_date, holdings, and shares_outstanding are digested together into this artifact's execution_hash: that hash IS the positions_digest a downstream NAV artifact cites via positions_ref, never a second canonicalization. A restated snapshot for the same fund and date is a new artifact that cites this one's execution_hash via the top-level supersedes field: there is no reverse link and no status registry.
⚠ DECISION-SUPPORT DRAFT. Not a custodian verification, not a live position feed, not a NAV or pricing computation. Holdings and shares_outstanding inputs are supplied and asserted only.
OpenChainGraph v0.4 artifact · execution_hash:
–