Skip to content

Corpus 2026-07-06 (`latest-corpus`, refreshed daily)

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 May 08:59

Always-current corpus for rbi-source-mcp — the indexed RBI regulatory document database (hybrid FTS5 + sqlite-vec retrieval).

This release is a moving alias. Assets are clobber-replaced on every successful build. Consumers polling here never see a 404 window.

Latest build

field value
build_date 2026-07-06
build_mode diff
build_commit 4085a0eea0e47adbb5e022ecb17f402fc99794fb
build_run #28765315197
schema_version 1
embedding_model @cf/baai/bge-base-en-v1.5
embedding_dim 768

Cadence

  • Daily at 02:00 UTC: incremental diff build; ~5 min, ~50 CF Neurons.
  • Monthly on the 1st at 03:00 UTC: full rebuild; ~30 min, ~3000 CF Neurons. Catches silent RBI re-uploads (PDFs replaced without bumping the list-page date) that diff-mode can't see by definition.

Install

pip install rbi-source-mcp
rbi-source-fetch-corpus                   # pulls THIS alias
rbi-source-fetch-corpus --verify-sigstore # cryptographic verify

Verify

  • SHA256: shasum -a 256 -c corpus.sqlite.xz.sha256
  • Sigstore: the .sigstore.json bundles are signed by corpus-release.yml@refs/heads/main via GitHub Actions OIDC.
    cosign verify-blob \
      --bundle corpus.sqlite.xz.sigstore.json \
      --certificate-identity 'https://github.com/harshilmathur/RBI-Source-MCP/.github/workflows/corpus-release.yml@refs/heads/main' \
      --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
      corpus.sqlite.xz

Smoke gate

Each build passes a paired eval gate before publish:

  • absolute: ≥80% hit-rate on the eval suite
  • regression: <5pp drop vs the prior latest-corpus build

Eval JSON attached as eval.json (used by the next run's regression check) plus eval-current.json (this run's snapshot for forensics).

Forensics on prior corpora

Per-build provenance for this corpus is stamped inside the SQLite at corpus_meta (key/value rows: build_commit, build_run_id, build_mode, embedding_*, schema_version). For older builds: see this workflow's run history — each run carries a 30-day artifact with the corpus + eval.