The Knowledge Graph
A navigable projection of the protocol's published knowledge.
The World Skills Protocol is more than a collection of documents.
Every published definition, concept and relationship forms part of a coherent body of knowledge.
The Knowledge Graph projects this body of knowledge into an explorable network, allowing humans, software systems and AI agents to navigate the protocol exactly as it has been published—without interpretation, inference or hidden assumptions.
It exists to make the protocol understandable without changing its meaning.
Section 1 — What is the Knowledge Graph?
The Knowledge Graph is the canonical projection of the World Skills Protocol.
It transforms the protocol's published concepts and relationships into an interconnected graph while preserving exactly the semantics established by the protocol itself.
Every node represents a concept formally published by the protocol.
Every edge represents a relationship explicitly declared by the protocol.
The graph is therefore not an independent source of knowledge.
It is a structured reading of the canonical corpus.
Nothing appears in the graph unless it has first been published by the protocol.
Likewise, nothing published by the protocol is intentionally omitted from the graph.
The graph exists to expose structure—not to create it.
Section 2 — Why does it exist?
As the protocol grows, understanding how concepts relate to one another becomes increasingly important.
Reading Records sequentially explains individual concepts.
The Knowledge Graph explains how those concepts fit together.
Instead of navigating documents one by one, readers can explore the protocol through its architecture.
Developers can discover dependencies.
AI systems can traverse published relationships.
Researchers can understand how definitions connect.
The graph therefore provides a navigable representation of the protocol while preserving the authority of the Records themselves.
The protocol remains the source.
The graph remains its projection.
Section 3 — How is it built?
The Knowledge Graph is generated directly from the published corpus.
The projection process reads the protocol's Records and extracts only the concepts and relationships that those Records explicitly publish.
The graph generator never invents concepts.
It never creates relationships.
It never derives semantics from implementation data.
Each projection is generated from a specific version of the published corpus and therefore represents a precise documentary state of the protocol.
When the corpus evolves, a new projection is generated.
Previous projections remain historical artefacts and are never rewritten.
The graph therefore reflects the evolution of the protocol while preserving the integrity of every published state.
Section 4 — What does the graph guarantee?
The Knowledge Graph guarantees that every published relationship originates from the protocol itself.
Every node corresponds to a published concept.
Every edge corresponds to a published relationship.
Every projection is reproducible from the published corpus.
Because the graph is generated rather than manually maintained, its structure can always be traced back to the Records that define it.
This provides complete documentary traceability.
Every relationship can be justified.
Every concept can be located.
Every projection can be regenerated from the same documentary state.
The graph is therefore deterministic, reproducible and auditable.
Section 5 — What the graph deliberately does not guarantee
The Knowledge Graph is intentionally limited.
These limitations are architectural guarantees rather than missing features.
The graph does not contain operational data.
It does not represent database instances.
It does not expose unpublished relationships.
It does not infer semantics.
It does not interpret the protocol.
If an implementation stores additional information that has never been published by the protocol, that information does not appear in the graph.
Likewise, if a relationship exists only in an implementation and has never been established by a Record, the graph intentionally ignores it.
The graph projects concepts.
It does not project individual occurrences of those concepts.
The graph therefore represents what the protocol publishes—not everything an implementation knows.
Section 6 — Concepts and instances
The World Skills Protocol distinguishes concepts from their individual occurrences.
A concept belongs to the protocol.
An occurrence belongs to an implementation.
For example, the protocol may establish that a Framework can be reidentified.
This relationship belongs to the graph because it is part of the published architecture.
A particular Framework being reidentified by another Framework is an implementation event.
Such occurrences remain outside the graph and are instead exposed through the protocol's discovery mechanisms.
This separation ensures that the graph remains stable while implementations continue to evolve.
Section 7 — Relationship with the canonical corpus
The Knowledge Graph never replaces the protocol.
Records remain the only normative source.
The graph exists solely to improve navigation, exploration and understanding.
Whenever a concept or relationship appears in the graph, its authority comes entirely from the Record that established it.
If a relationship has never been published by the protocol, the graph cannot display it.
Conversely, once a relationship is established by the corpus, it becomes eligible for projection without requiring manual modelling.
The graph therefore follows the protocol.
The protocol never follows the graph.
Section 8 — Relationship with AI systems
Large Language Models and intelligent software benefit from structured knowledge.
Instead of relying solely on natural-language search, they can navigate explicit concepts and published relationships.
This reduces ambiguity.
It improves discoverability.
It allows software agents to understand how published concepts relate without requiring additional interpretation.
Because the graph contains only protocol-approved knowledge, AI systems receive information whose origin remains fully traceable.
Every answer can ultimately be traced back to the Record that established the underlying concept or relationship.
Section 9 — Versioning
Each Knowledge Graph projection corresponds to a specific documentary state of the protocol.
Whenever the corpus changes, a new projection is generated.
Earlier projections remain preserved as historical representations.
They are never modified retrospectively.
This ensures that references made against a previous projection remain reproducible and auditable even after the protocol evolves.
The graph therefore evolves by publication rather than by mutation.
Conclusion
The Knowledge Graph exists to make the World Skills Protocol easier to explore without changing what it says.
It does not replace the Records.
It does not interpret them.
It does not infer what has not been published.
Its purpose is simple:
to expose the architecture that already exists within the protocol and make that architecture navigable for both humans and machines.
Explore the Protocol
Understand how concepts, Records and published relationships connect across the World Skills Protocol.