Supporting system · data governance

MESH_SILOS

Map reporting silos into one crosswalk. No data moved, no network, every decision written down.

  • Version 0.8.68
  • Licence EUPL-1.2
  • Python 3.11+
  • Tests 188 files
Two columns of records joined by a crosswalk.
Illustration: two columns of stacked blocks facing each other, joined by thin crosswalk lines.

What it does

Banks, insurers, CRM exports and legacy databases, all read-only. Columns that describe the same entity are matched, and the crosswalk records every decision so that a model can be explained two years later.

The output is not a warehouse. It is the mapping: crosswalks, golden records, code tables and the BI/SQL/dbt artefacts that consume them, generated locally on a laptop that never opens a socket.

The air gap is enforced, and its limits are published

A socket guard installed at import time refuses outbound connections through six entry points. That claim would be cheap if it stopped there, so the documentation also names the four legacy resolvers the guard does not patch: a guarantee that hides its own holes is not a guarantee.

  • Stack

    Python 3.11+ · FastAPI · DuckDB · Pydantic. Offline by design, not by configuration.

  • Archive

    mesh-silos.tar.gz, roughly 2.5 MB, the full tree at the last commit.