Technical White Paper · 2026
The Semantic Brain of the Organization
How to Connect Every Experience to Every Concept — a comprehensive technical and strategic white paper on ontology, semantic graphs, and the ExperienceStatement as the hallmark data primitive that connects human experience to machine-navigable knowledge at organizational scale.
Randy Stewart Miller · May 2026
Executive Summary
Modern organizations generate vast amounts of experience data but have no system to understand it — to connect it across domains, infer meaning from patterns, and translate it into actionable intelligence about workforce readiness, operational risk, and learning effectiveness.
The central question this architecture answers: Does this person, in this role, with this history, know how to do this job safely and competently — right now?
01
The Problem No One Has Solved
Every organization is drowning in data about its own people, yet chronically blind to what that data means. A worker completes a confined space entry training course. The LMS records a "completed" status and a score. Six months later, that same worker is involved in a confined space incident. The safety system records the incident. The maintenance system records the corrective work order. The HR system records a performance note.
Core Organizational Blind Spot
None of these systems talk to each other. No system asks: Was the worker's training sufficient? Did the incident reveal a gap in the training content? Is the work order linked to the corrective action from the incident?
xAPI (the Tin Can API) was a noble attempt to solve part of this problem. By standardizing the format of learning records into actor-verb-object statements, it created a lingua franca for learning data. But it stopped there. It recorded what happened but not what it meant. It captured events but not concepts. It stored data but could not reason about it.
02
The ExperienceStatement: Beyond Actor-Verb-Object
The ExperienceStatement is the hallmark data primitive of this architecture — the reason the platform was invented. It extends the xAPI model not just technically but philosophically: it treats every human experience in the organization as a semantically rich event that carries meaning far beyond "who did what to what."
| Layer | Fields | What It Captures |
|---|---|---|
| Actor | actor.uid, actor.name, actor.mbox | Who — anonymized, privacy-preserving, universal identifier |
| Verb | verb.id (URI), verb.display | The governed action — drawn from the Verb Registry |
| Object | object.id, object.definition.type | What was acted upon — a course, procedure, permit |
| Result | score, completion, success, duration | Measurable outcome — pass/fail, score, time spent |
| Semantic Context | concept_uris[], scheme_uris[], graph_edges[] | Ontological meaning — what concepts this event evidences |
| Timestamp | ISO 8601 datetime | When — enabling temporal analysis and decay detection |
"The ExperienceStatement is not a log entry. It is a neuron. It fires when a human being has an experience that matters — and through the semantic graph, that firing propagates meaning across the entire organizational brain. I built this architecture because I believed that connecting those neurons was the key to unlocking what organizations actually know about their people."
03
The Semantic Graph Architecture
The semantic graph is not a visualization tool or a reporting layer. It is the connective tissue of the entire platform — the infrastructure through which every entity, every event, every record is linked to a governed vocabulary of organizational concepts.
ConceptScheme
Domain vocabularies — grouped namespaces for experience-states, safety, competencies, operations, maintenance, AI analytics, and more. Each scheme governs a bounded set of concepts.
Concept
Individual semantic nodes — each with a canonical URI, preferred label, definition, domain, and metadata. Concepts are the vocabulary; the graph is the grammar.
ConceptRelationship
Edges between concepts — using predicates like broader_than, requires, evidences, mitigates, governs, teaches, assesses, proves. These form the ontological backbone.
ConceptMapping
Edges between entity records and concepts — connecting real-world data to the ontology. This is where data becomes intelligence.
04
Concept Schemes and Ontology Design
experience-states:
- learning-state
- operational-state
- risk-state
- evidence-state
competencies:
- task-proficiency
- qualified-operator
- safety-critical-competency
safety:
- incident-investigation
- corrective-action
- hazard-control
- permit-to-work
- lockout-tagout
- confined-space-entry
operations:
- procedure-execution
- simops
- shift-handover
- field-observation
maintenance:
- work-order
- preventive-maintenance
- asset-reliability
- calibration
ai-analytics:
- gap-analysis
- semantic-enrichment
- explainable-recommendation
- drift-detection
Randy Stewart Miller · May 2026
The ExperienceStatement architecture was conceived and first built by Randy Stewart Miller.