Release archive
3.2.190

CRYPTO-SOURCE-PROVENANCE-PRESERVATION (Report Logic)

Release v3.2.190 focuses on CRYPTO-SOURCE-PROVENANCE-PRESERVATION (Report Logic).

FixedInternal
CRYPTO-SOURCE-PROVENANCE-PRESERVATION (Report Logic)

Release digest

Fixed

  • CRYPTO-SOURCE-PROVENANCE-PRESERVATION (Report Logic) — Crypto project normalization now preserves explicit section_sources, source_provenance, and source_families source-family rows when they are attached in Vartovii data, including source labels and row-level date aliases such as fetched_at, observed_at, last_updated, published_at, and date.

Internal

  • Added focused coverage proving declared source-family provenance removes false Source provenance model report gaps, keeps raw source URLs out of PDF view-model citation rows, and still treats missing source labels as payload gaps before freshness or confidence can be assessed.
  • Updated docs/architecture/CRYPTO_REPORTS.md, docs/reports/audits/2026-06-01_CRYPTO_REPORT_DATA_GAP_ANALYSIS.md, and knowledge-base/docs/crypto/dashboard-ui.md because this tightens the report-facing source-provenance normalization contract. Public-docs decision: user-facing crypto docs now mention preserved source-family labels and date aliases without claiming source verification, audit coverage, safety, or investment suitability.

Technical notes