What was observed
Documentation quickly becomes outdated when it is separate from the entities, relations and routes that a software system actually uses.
RESEARCH QUESTION
How can software become explainable through its own knowledge graph?
This research question studies whether software can explain its purpose, evidence, dependencies and limits through the same graph that generates its public pages and machine-readable records.
active
validated
v1.0.0
EDITORIAL FRAME
What this entry establishes.
A concise view of its scope, position, limitations and supporting sources.
Why it matters
A project can have pages, JSON-LD, search data, relation exports and source files that disagree unless one structured graph acts as the authority layer.
What is being tested
The knowledge graph itself can become the primary documentation layer when pages, identifiers, graph neighborhoods, search documents and relation panels are generated from the same source records.
Current understanding
Explainability improves when the public interface exposes the graph instead of hiding it. A page should show what it is, what it connects to, what evidence supports it and where its claims remain limited.
How the question is being tested
- Generated entity pages (active) The Electronic Artefacts site generates canonical pages, identifiers, JSON-LD, search documents and graph neighborhoods from typed Markdown records.
- Relationship panels (observed) Project, program, concept and publication pages expose typed relations so readers can inspect why records are connected.
What has emerged so far
The site already demonstrates a partial answer. Its public HTML, identifiers, JSON-LD, search documents and local graph files are generated from typed records rather than maintained as separate explanations.
What remains unknown
- Add more derived relation patterns while preserving editorial review.
- Make graph neighborhoods easier to inspect from public pages.
- Define what counts as enough evidence before a relation becomes canonical.
Research timeline
- 2026-03-01 / Documentation reframing The site architecture was reframed as a public graph rather than a set of manually maintained portfolio pages.
- 2026-07-09 / Research-question entity added Research questions became graph entities, allowing projects and software to point back to the questions they test.
Software, projects and evidence
Vestiges
Voice Capture Studio
VASTE
Electronic Artefacts Lightweight Template
Linked Data and Public Knowledge Pages
Knowledge Graphs for Cultural Infrastructure
AI Search, Structured Content and Knowledge Graph SEO
Why Graphs Are More Powerful Than Folders
Contextual Execution and Graph Runtimes
Knowledge Hub Foundations
Knowledge Hub Third Wave
Conceptual and technical context
Tags and disciplines
Knowledge GraphLinked DataDocumentationExplainable SoftwareStatic Site GenerationInformation ArchitectureSoftware ArchitectureKnowledge SystemsWeb Development
Observation
Documentation drifts when it sits outside the system it describes. A static page can be accurate on the day it is written and misleading after a few structural changes.
Problem
Electronic Artefacts needs public software records that remain useful to people, search engines and future agents. That requires stable identifiers, typed relations, readable pages and machine-readable exports generated from the same source.
Hypothesis
A knowledge graph can become the documentation layer. If the graph records the entities, relations, sources and versions, then the public site can generate explanations instead of manually duplicating them.
Current Understanding
The graph does not remove editorial responsibility. It makes responsibility visible. A relation still needs judgment, but once accepted it can update pages, search, JSON-LD and local graph neighborhoods together.
Unknowns
The next problem is interface depth. The graph should be visible enough to support understanding without turning every page into an administrative console.
How can software become explainable through its own knowledge graph?
Cite this page
How can software become explainable through its own knowledge graph?. 1.0.0. Electronic Artefacts, 2026-07-09. https://electronicartefacts.com/research/questions/self-explaining-knowledge-graph-software/
TYPED RELATIONSHIPS
Connected work and ideas.
Each relation names what connects the two entries and why that connection matters.
Vestiges
Vestiges is listed as a current software or project answer for the research question "How can software become explainable through its own knowledge graph?".
Voice Capture Studio
Voice Capture Studio is listed as a current software or project answer for the research question "How can software become explainable through its own knowledge graph?".
VASTE
VASTE is listed as a current software or project answer for the research question "How can software become explainable through its own knowledge graph?".
Electronic Artefacts Lightweight Template
Electronic Artefacts Lightweight Template is listed as a current software or project answer for the research question "How can software become explainable through its own knowledge graph?".
Knowledge Graph
The research question "How can software become explainable through its own knowledge graph?" applies Knowledge Graph as part of its current model.
Graph Runtime
The research question "How can software become explainable through its own knowledge graph?" applies Graph Runtime as part of its current model.
Linked Data
The research question "How can software become explainable through its own knowledge graph?" applies Linked Data as part of its current model.
Metadata
The research question "How can software become explainable through its own knowledge graph?" applies Metadata as part of its current model.
Entity Identity
The research question "How can software become explainable through its own knowledge graph?" applies Entity Identity as part of its current model.
Provenance
The research question "How can software become explainable through its own knowledge graph?" applies Provenance as part of its current model.
Hypertext
The research question "How can software become explainable through its own knowledge graph?" applies Hypertext as part of its current model.
Personal Knowledge System
The research question "How can software become explainable through its own knowledge graph?" applies Personal Knowledge System as part of its current model.
JSON-LD
The research question "How can software become explainable through its own knowledge graph?" uses JSON-LD as a relevant technical reference.
RDF
The research question "How can software become explainable through its own knowledge graph?" uses RDF as a relevant technical reference.
Web Animations
The research question "How can software become explainable through its own knowledge graph?" uses Web Animations as a relevant technical reference.
Linked Data and Public Knowledge Pages
Linked Data and Public Knowledge Pages documents context, evidence or vocabulary for the research question "How can software become explainable through its own knowledge graph?".
Knowledge Graphs for Cultural Infrastructure
Knowledge Graphs for Cultural Infrastructure documents context, evidence or vocabulary for the research question "How can software become explainable through its own knowledge graph?".
AI Search, Structured Content and Knowledge Graph SEO
AI Search, Structured Content and Knowledge Graph SEO documents context, evidence or vocabulary for the research question "How can software become explainable through its own knowledge graph?".
Why Graphs Are More Powerful Than Folders
Why Graphs Are More Powerful Than Folders documents context, evidence or vocabulary for the research question "How can software become explainable through its own knowledge graph?".
Contextual Execution and Graph Runtimes
Contextual Execution and Graph Runtimes documents context, evidence or vocabulary for the research question "How can software become explainable through its own knowledge graph?".
Knowledge Hub Foundations
The research question "How can software become explainable through its own knowledge graph?" belongs to the Knowledge Hub Foundations collection for editorial navigation.
Knowledge Hub Third Wave
The research question "How can software become explainable through its own knowledge graph?" belongs to the Knowledge Hub Third Wave collection for editorial navigation.
22 useful links
Use these connections to move from this page toward nearby projects, concepts and references.