Launch an initiative without starting from scratch
When a team starts from an existing reality, it recopies the data, redefines the concepts and reconfigures the access rules. The same work three times over, for every initiative. Context inheritance removes this triple restart.
Three things you duplicate without noticing
Data is only a third of the problem
What gets recopied at the same time is the ontology (the very definition of the concepts): what is a "model", a "part", which attributes define them, how they connect. And with it, the whole set of rules: who can see, who can modify, which restrictions apply to which concept.
Nobody ever recopies an ontology or a rule set with perfect fidelity. The result isn't a faithful variant: it's a cousin environment, resembling the official one without any guarantee of conforming to it.
The real cost isn't in storage
An initiative starting from a copy starts from a foundation that's already outdated
It inherits a snapshot of the ontology and rules as they existed at the moment of copying, not their current version. If the reference then evolves, nothing guarantees the initiative is informed, nor that it keeps conforming to it.
Over time, the organization ends up with a constellation of contexts that all resemble, from a distance, the official reference without being it — each one, in its own way, not quite faithful.
Inherit, rather than rebuild
You start from a link, not a copy
A working context attaches to a parent context, which stays the reference source. The initiative automatically sees its data, its ontology and its rules without any of these three layers needing to be recopied or manually reconfigured. The team then adds what is specific to it.
The fairest image remains that of a family inheritance: what a grandfather owns (his estate, but also his principles for passing it on) is seen by his son, who adds what belongs to him, without ever having to recopy everything to benefit from it.
An initiative that inherits a context therefore never has to wonder whether its ontology is aligned or whether its privacy rules are up to date: they are, by construction.
Launch an initiative from a shared foundation
Without ever duplicating the data, the ontology or the rules to start working.
Engineering
Open a derived context to simulate the impact of a change, knowing that the definition of every concept handled stays that of the reference.
Sales
Adapt an offer for a specific market by automatically inheriting the rules that already protect sensitive data, without redefining them one by one.
R&D
Build a test environment faithful to production (data, concepts and rules included), explore it, then discard it without having introduced any drift.
Several teams, several sites, several clients can launch their own initiatives from the same foundation. The reference evolves once, in the right place, and every initiative that inherits from it benefits instantly, with no manual propagation.
What it changes for trust
An initiative that inherits a context is never an approximate variant of the truth: it is literally built on it, with its data, ontology and rules intact, up to date, and automatically applied.
There is only one source, and initiatives that attach to it without ever detaching.
Getting started becomes a light gesture
Where a full environment used to need rebuilding before work could start, attaching to an official context is now enough. Testing an idea no longer costs the same as deploying it.
Subscribe to our newsletter
Insight on knowledge graphs, straight to your inbox.