Verified Financial Artifacts. A category private finance has been missing.
A Verified Financial Artifact is a document that carries a deterministic fingerprint, a public verification URL, and an engine-graded refusal to soften — independent of the SaaS platform that produced it. The reader resolves the URL, the fingerprint matches the engine state, the refusal discipline is structural. Capital Refinery's /p/<token> primitive ships today on the Continuous IC Memo and the IRA; the same primitive is designed to extend across the institutional document layer below.
A verified artifact resolves without a login.
When an LP, lender, or board director opens the link, they see the recommendation, the evidence behind each figure, and a fingerprint that matches the engine’s state at issuance — with no account and no dependency on our system.
What a Verified Financial Artifact is
Three primitives make a document Verified rather than just produced:
- Deterministic fingerprint — a cryptographic hash linking the artifact to the engine state at issuance. The reader can confirm independently that the document was not edited after generation. No SaaS dependency, no login, no opportunity for post-issuance editing.
- Public verification URL — the document resolves at a token-authenticated URL (e.g., /p/<token> or /p/ira/<token>) where the engine output renders read-only. The receiving counterparty verifies independently; the artifact stands alone.
- Engine-graded refusal to soften — the engine refuses to grade what it cannot observe. Sentiment, narrative coherence, management communication style are marked not_observable rather than imputed. The discipline is structural, enforced by the engine code, and identical regardless of which reader is looking.
The artifact types in the Verified Financial Artifact layer
The fingerprint + share-token + refusal-to-soften primitive ships today on two artifact types — the Continuous IC Memo and the IRA, each resolving at a public /p/<token> verification URL. The same primitive is designed to extend across the institutional document layer; the remaining types below are in development:
The structured decision basis at the moment of IC approval, with per-cell provenance on every figure and a cryptographic anchor on the decision-commit. Months or years later, an LP reading the memo can verify independently that the document matches the engine state at issuance.
The propagation of a specific shock against the live position — break order, headroom loss, time-to-consequence — rendered from the live record at issuance. The reviewer can resolve the verification URL to confirm the run is reproducible from the same engine state.
The borrower's covenant compliance state — observed values, covenant thresholds, time-to-consequence on each — with the fingerprint linking the attestation to the engine state at issuance. The artifact stands independent of the borrower's bank book or the lender's portfolio monitoring system.
The structured board pack rendered from the live record — fund health, portfolio Risk Signals aggregation, decision timeline, action items. Every figure traces to source; the fingerprint confirms the export matches the engine state when the board materials were distributed.
The structured quality-of-earnings analysis on a target business — adjusted EBITDA walk, working-capital normalization, customer concentration analysis, key-person dependency mapping — produced before the buy-side QoE rebuild and verifiable as engine output rather than seller marketing.
The structured request for covenant relief or modification, with the borrower's structural state graded against the lender's firm policy — observed value, threshold, severity, requested modification. The artifact is the structured alternative to a workout email chain.
What this category replaces
- Signed PDFs that prove the document was signed but not that the content is engine-graded — Verified Financial Artifacts go further: the content's structural basis is itself verifiable
- SaaS-locked dashboards that require platform access to read — Verified Financial Artifacts stand alone; the receiving counterparty doesn't need a login, an account, or platform access
- Decoration-based 'AI generated reports' that claim authority without disclosing evidence basis — Verified Financial Artifacts disclose the engine, the axes, the thresholds, and the refusals explicitly
- Marketing-tier audit trails that show 'we logged this' without verification — Verified Financial Artifacts let the receiving party verify, not just trust the producer
The technical architecture
- Deterministic fingerprint — derived from the full engine state at issuance (lane, axes, observed values, threshold configuration, refusals). Same inputs always produce the same fingerprint; any input change produces a different one.
- Share-token issuance — operator or GP issues a token from the deal home or memo view; the token resolves to a public URL with the LP-sanitized or operator-attested snapshot.
- HMAC-signed token validation — tokens are HMAC-signed against the platform's auth secret; tampering invalidates the token, the URL refuses to resolve.
- Audit log — every share-token issuance is logged to a JSONL audit trail (tenant, deal, lane, principal, IP, user-agent, token-hash fingerprint); raw tokens are never persisted.
- Refusal discipline encoded in the engine — every render path includes the refusal logic; signals that cannot be observed mark not_observable structurally rather than imputing.
Where Verified Financial Artifacts could extend
The primitive applies to any institutional document where evidence basis and engine state matter — beyond the two types Capital Refinery ships today (the Continuous IC Memo and the IRA), the architecture extends naturally to additional artifact classes:
- Audit committee report — board-pack drill-in with audit findings traced to engine state at finding time
- Sustainability / ESG disclosure — observed metrics vs firm policy thresholds with the same refusal discipline
- LP-side capital call notice — structured against the fund's stated investment policy with evidence on alignment
- Sponsor mark methodology disclosure — independent valuation review reconciled to sponsor's stated mark, with delta surfaced
- Workout proposal — borrower-side restructuring request with structural evidence on the proposed modification
What this category refuses
- Verified Financial Artifacts are not blockchain — the fingerprint is cryptographic, but the architecture doesn't require distributed ledger infrastructure. The verification is at the platform-issued URL, not via on-chain proof.
- Verified Financial Artifacts are not AI-generated narrative — the engine output is deterministic; the artifact's content is engine-graded, not LLM-authored
- Verified Financial Artifacts are not workflow tools — the primitive is the document itself standing alone after issuance, not a multi-party workflow with tracked state
- Verified Financial Artifacts are not co-brandable — every artifact ships engine-identical regardless of which counterparty or partner issued it. White-label requests are refused on this structural basis (the artifact's portability depends on engine-identical rendering)
Sources cited
- AICPA Attestation Standards (SSAE 18 and successors) — the conceptual reference for third-party attestation in financial reporting
- PCAOB Auditing Standards — the conceptual reference for audit verification discipline (engine-graded refusal parallels auditor independence and skepticism)
- NACD (National Association of Corporate Directors) — board pack governance principles → https://www.nacdonline.org
- COSO Enterprise Risk Management framework — risk governance discipline that informs the firm-policy threshold pattern → https://www.coso.org
- ILPA Principles — LP-facing reporting standards that inform the LP-sanitized verification snapshot pattern → https://ilpa.org/principles/
- Capital Refinery internal: docs/features/investor/lp_provenance_page.md, docs/features/reporting/provenance_signed_exports.md, docs/features/platform/share_issuance_audit.md
The verified-artifact mechanism extends from issuance to lifecycle. Every signed export carries an IC anchor; when a new IC commits for the same deal, the prior artifacts are automatically classified — aligned, superseded, or no current anchor — without a reviewer touching a thing. See Signed Export Governance →
See a Verified Financial Artifact in the wild.
The Cedarbrook IRA at /cedarbrook resolves to a public verification page. The Falcon IC memo at /falcon does the same. Both carry a fingerprint, both stand independent of the platform, both make their refusals visible. Talk to us about requesting a sample for your DDQ.