context-layer

There is a lot of talk about context layers these days. I thought the best way to learn a new concept was to try to build one. This is a toy model, but the core ideas are rather simple.

• A data platform is full of signals: semantic models, query history, who opens what, what is certified, what is refreshed. That is enough to rank definitions.
• It is very hard to maintain a knowledge graph by hand, and the ones that exist drift. The graph has to build itself.
• The agent has to be stateless and replaceable.
• A context layer is here to be useful, not to be perfect.

The bet is that a context built automatically, at least to start, and ranked on how the platform already behaves gets better as the platform is used. I do not know yet whether that holds. What I do like is that it uses the semantic models already there and asks for no new modelling.

So far the industry splits on who settles a conflict: the platform, by scoring it, which scales with usage, or a person, by reviewing it, which scales with reviewer time; I prefer the first, time will tell.

The harvest delivers one thing: a knowledge graph of the tenant - every term, its competing definitions ranked, and what feeds what. That graph is the context. It runs nightly on its own.

See it on a real tenant

!pip install fabcontext
import fabcontext
url = fabcontext.harvest("Workspace_A")

The first call creates the lakehouse - in a workspace called context_layer you make first - and every later one updates it. It returns the URL an agent asks against.

The ranking, what is harvested, the schema, how to ask, the limits: docs/guide.md.

Client

The agent can be anything - Claude, GitHub Copilot, Scout, Microsoft 365 Copilot. It installs nothing and needs one thing: a read-only Power BI connection. It finds the published ranking itself, at an address that is the same in every tenant. One DAX query asks which definition wins; a second runs it. One folder per tool: client/.

Licence

MIT - see LICENSE.