Is The Library the same as the Living Vault?
No. The Library is distribution (install across harnesses). The Living Vault is governance and measurement inside Fabric. They complement each other; neither replaces the other.
From distribution to governance inside Fabric
Four similarly named systems serve different roles. This map shows how install, catalog projection, measurement, and Fabric-native governance connect. There is no automatic sync between every box; each arrow is an intentional, documented handoff. The public demo runs at zero Fabric cost; a live Rayfin deploy on Fabric exercises the same model end to end.
Keep the names straight
The Library
Distribution catalog. Installs the same agentic assets across Claude Code, Codex, Copilot, Grok, and devices.
the-fabric-library
Upstream catalog for asset-side projection into fabric-library.json. Not the same repo as The Library.
The Living Vault
Rayfin Fabric app: system of record + effectiveness monitor. This is the operational product surface.
the-vault (cousin)
Separate personal skill library. Tooling source only; does not feed the Living Vault catalog.
Microsoft Fabric
Hosts the Rayfin app bundle and semantic model. Live read/write path deploys on request; demo SWA runs at zero Fabric cost.
Power BI
Optional analytics consumer of the Fabric semantic model. The Vault's Monitor is the live ops UI; Power BI is not a substitute.
Intentional handoffs (not auto-sync)
| From | To | What moves | Who triggers it |
|---|---|---|---|
| The Library | Harness workspaces | Installed skills, agents, MCP servers | Contributor / library install |
| the-fabric-library | The Living Vault | fabric-library.json catalog projection |
Admin import or accepted submission |
| Harness session logs | The Living Vault | Metadata-only utilization rows | Optional local collectors (self-host) |
| Rayfin semantic model | Power BI | Nine-entity star schema | Analyst bind (optional) |
Live stack proof (2026-06-19)
Four captures from the same live Fabric session: SQL facts, ops Monitor, executive Overview, and optional Power BI downstream.
Closed loop: The Library distributes assets across harnesses. the-fabric-library projects the governed catalog. The Living Vault measures which assets earn their place. Telemetry reads local harness logs (metadata only) and never ships in the public demo build.
Common confusions
Is the-fabric-library the same as The Library?
No. Different repos and roles. the-fabric-library is the upstream
catalog projection source for fabric-library.json. The
Library is the cross-harness install catalog.
Is Power BI the product?
No. The Monitor and /model canvas are the live operational UI. Power BI is an optional downstream consumer of the same Rayfin semantic model.
Does the demo read my machine?
No. The public SWA ships synthetic utilization JSON only. Real harness telemetry stays in gitignored local snapshots when you self-host. See the telemetry guide.