# Concepts Extracted from Stakeholder Interviews

## Purpose

This document is the structured concept layer behind Workstream 1 stakeholder interviews. It extracts named concepts, BFO bucket classifications, and relationships from 12 internal interviews across four organizational layers (Standards and Innovation, Data Platforms, AI and Search, Operations and Business).

The extract feeds slide 4 of `TotalEnergies_SKG_Stakeholder_Perspective_Summary.html` (Knowledge Graph: interview concepts mapped to the BOB BFO 7-bucket ontology). Use this file when editing the static SVG on slide 4, updating the stakeholder matrix, or tracing which interview voice surfaced each concept.

**Primary outputs linked to this extract:**

- Knowledge Graph slide (BFO 7-bucket concept map)
- Stakeholder Map slide (12 interviewees around TSF / SousLeSens)
- Pain point matrix and executive communication kit narrative

---

## BFO 7-Bucket Framework

The BOB BFO 7-bucket ontology classifies interview concepts using ISO/IEC 21838-2 (Basic Formal Ontology). Occurents (Process, Temporal) sit above Continuants (Material, Site, Information, Quality, Role). Bucket colors and layout match `docs/ontology/bob_ontology.html`. Slide 4 renders a static inline SVG (export-safe, no CDN or iframe) with 7 bucket regions and 24 interview-salient concept nodes.

| Bucket label (bob_ontology) | BFO class | Color | ISO 21838-2 anchor | Modeling question |
|--------|-----------|-------|-------------------|-------------------|
| Process (WHAT) | Process / HOW-IT-HAPPENS | `#C0392B` | Occurrent (`BFO_0000015`) | What happens, in what sequence, with which participants? |
| Temporal (WHEN) | Temporal region / WHEN | `#148F77` | Occurrent (`BFO_0000008`) | Over what decision or governance cycle does value accrue? |
| Material (WHO) | Material entity / WHAT/WHO | `#2980B9` | Continuant (`BFO_0000040`) | Which systems, programmes, or physical assets are involved? |
| Site (WHERE) | Site / WHERE | `#27AE60` | Continuant (`BFO_0000029`) | Where does the process or asset sit geographically or operationally? |
| Information (HOW WE KNOW) | Information content entity / HOW-WE-KNOW | `#D68910` | Continuant (`BFO_0000031`) | Which standards, vocabularies, or formal knowledge structures ground meaning? |
| Quality (HOW IT IS) | Quality / HOW-IT-IS | `#717D7E` | Continuant (`BFO_0000019`) | What observable attributes (quality, lineage) describe current state? |
| Role (WHY) | Realizable entity / WHY (POTENTIAL) | `#7D3C98` | Continuant (`BFO_0000023`, `BFO_0000016`) | Which capabilities, governance roles, or integration functions must exist? |

**Visual source (Knowledge Graph slide):** Inline SVG in `TotalEnergies_SKG_Stakeholder_Perspective_Summary.html` slide 4. Reference interactive copy: `assets/ontology/te_interviews_ontology.html`.

**Ontology reference:** `docs/ontology/bob_ontology.html` (canonical BFO bucket layout), `docs/ontology/BFO7Buckets.ttl`, `docs/ontology/ontology.md`

**Knowledge Graph slide:** Static inline SVG in `TotalEnergies_SKG_Stakeholder_Perspective_Summary.html` slide 4 (viewBox `0 -48 1180 590`, `preserveAspectRatio="xMidYMid meet"`). Self-contained; no vis-network, iframe, or CDN. Shows 24 curated nodes and 11 semantic relationships plus 13 BFO axiom edges; CDF→TSF dashed for platform boundary tension.

---

## Concepts by Bucket

### HOW-IT-HAPPENS (Process)

| Concept | Definition | Stakeholders | Related concepts / edges |
|---------|------------|--------------|--------------------------|
| Semantic mapping (MAP) | Aligning equipment descriptions, tags, functional locations, and documents to governed ontology concepts; reduces manual reconciliation across FPSOs and platforms. | Boulanger, Jouret, Leclerc, Mourot | SousLeSens **enables** MAP; Job card transfer **requires** MAP; MAP **produces** controlled vocabulary |
| Ontology vetting (VET) | Formal audit of the TE Business Objects ontology for ISO 21838-2 (BFO) alignment, conducted with NCOR in the Cross-FPSO mission. | Leclerc, Boulanger, Guillermou | VET **validates** TSF |
| Job card transfer (JCT) | Cross-FPSO transfer of maintenance and inspection records (Pazflor to Dalia); first ML prototype delivered 23,000 functional location matches. | Campan, Leclerc | LifeX cycle **triggers** JCT; JCT **requires** MAP |
| Data product creation (DPC) | Governed packaging of operational data for downstream platform consumption; requires semantic input to avoid duplicate pipelines. | Soleilhavoup, Campan, Jouret, Teixugueira-de-Castro | Semantic authority **governs** DPC; LifeX **requires** DPC |
| RAG pipeline (RAG) | Retrieval-augmented generation and agentic search workflows consuming semantic resources as structured grounding input. | Maze, Jallais, Vallejo-Vaca | Controlled vocabulary **grounds** RAG |
| Semantic contextualization | Linking operational source data to Cognite CDF enterprise models using TSF-governed concepts to reduce manual reinterpretation. | Teixugueira-de-Castro, Jouret, Soleilhavoup | Cognite CDF **consumes** TSF |
| ML training pipeline | Machine learning workflows on internal GPU infrastructure for subsurface and operational data; benefits from ontology API access. | Maze | API access **enables** interoperability |
| DMP completion | Data Management Plan governance prerequisite for affiliate readiness; blockers include incomplete ownership and quality rules. | Colombani, Mourot, Vallejo-Vaca | Data governance **uses** Collibra |
| Ontology semanticization of standards | Formalizing CFIHOS, SIFOS, ISO 14224, and related standards into TSF-compatible structures. | Leclerc, Jouret, Boulanger | CFIHOS **aligns with** BFO |

### WHEN (Time)

| Concept | Definition | Stakeholders | Related concepts / edges |
|---------|------------|--------------|--------------------------|
| LifeX decision cycle (LXC) | Weekly CAPEX / OPEX investment update cycle for Angola FPSO life extension; boardroom-visible, funded programme. | Campan, Leclerc, Jouret, Teixugueira-de-Castro | LXC **triggers** job card transfer; LifeX **occurs in** FPSO |
| DMP lifecycle (DMP) | End-to-end affiliate governance cycle from DMP drafting through Collibra migration, ownership assignment, and reporting readiness. | Mourot, Colombani, Vallejo-Vaca | Data governance **uses** Collibra |

### WHAT/WHO (Material Entity)

| Concept | Definition | Stakeholders | Related concepts / edges |
|---------|------------|--------------|--------------------------|
| TSF | TotalEnergies Semantic Framework: central semantic control layer maintained by OneTech EP since 2021; BFO-aligned, externally recognized in CFIHOS, JIP36, PCA, AFNOR, ISO work. | Leclerc, Guillermou, Boulanger, Teixugueira-de-Castro, Jouret, Mourot | TSF **grounded in** BFO; Cognite CDF **consumes** TSF |
| SousLeSens (SLS) | Semantic tool and graph infrastructure for vocabulary management, semantic mapping, and controlled term publication. | Leclerc, Boulanger, Mourot | SLS **part of** TSF; SLS **enables** semantic mapping |
| Cognite CDF (CDF) | Industrial data platform receiving contextualized equipment and operational data; center of Quantum migration and LPG modeling. | Teixugueira-de-Castro, Jouret, Soleilhavoup, Colombani, Vallejo-Vaca | CDF **consumes** TSF |
| Collibra (COL) | Data catalog and governance platform for business objects, lineage, ownership, and reporting readiness. | Mourot, Soleilhavoup, Guillermou, Colombani | Data governance **uses** COL |
| LifeX (LX) | Asset life extension programme for Angola FPSOs (Block 17: Pazflor, Dalia); funded weekly decision cycle with direct CAPEX and OPEX exposure. | Leclerc, Campan, Jouret, Teixugueira-de-Castro | LX **occurs in** FPSO; LXC **triggers** JCT |
| Business Objects (BO) | TotalEnergies ontology layer formally audited for BFO alignment in the 2025-2026 Cross-FPSO mission. | Leclerc, Guillermou, Mourot | VET **validates** TSF (via BO audit) |
| Microsoft Fabric | OneTech data platform landscape component alongside Cognite and Databricks. | Vallejo-Vaca, Guillermou | Interoperability target for TSF outputs |
| GPU infrastructure | Internal DataTech infrastructure for NLP and LLM pipeline execution. | Maze | Hosts RAG and ML training |

### WHERE (Space)

| Concept | Definition | Stakeholders | Related concepts / edges |
|---------|------------|--------------|--------------------------|
| Pazflor / Dalia FPSOs (FPSO) | Two Angola Block 17 floating production units; source and target for cross-FPSO job card transfer and LifeX evidence. | Campan, Leclerc, Jouret | LifeX **occurs in** FPSO |
| Block 17 Angola (B17) | Offshore licence block hosting LifeX FPSO assets and inspection programmes. | Campan, Leclerc | FPSO **located in** B17 |

### HOW-WE-KNOW (Information Content Entity)

| Concept | Definition | Stakeholders | Related concepts / edges |
|---------|------------|--------------|--------------------------|
| BFO | Basic Formal Ontology (ISO/IEC 21838-2:2021): top-level formal ontology grounding TSF; validated in NCOR audit. | Leclerc, Boulanger, Guillermou | TSF **grounded in** BFO; BFO **formalized in** OWL; ISO **defines** BFO |
| OWL | Web Ontology Language: W3C standard for expressing TSF and Business Objects ontologies. | Leclerc, Boulanger, Maze | BFO **formalized in** OWL |
| SKOS | Simple Knowledge Organization System: W3C vocabulary standard for taxonomies and controlled term publication. | Leclerc, Boulanger, Jallais | Used alongside OWL for Smart Search taxonomies |
| CFIHOS (CFI) | Capital Facilities Information Handover Standard; TSF aligned; applied in Cognite modeling. | Leclerc, Jouret, Boulanger | CFI **aligns with** BFO |
| Controlled vocabulary (CV) | Governed term lists for domain jargon used in search classification, RAG relevance, and AI prompt grounding. | Jallais, Maze, Boulanger | CV **grounds** RAG; MAP **produces** CV |
| Data Management Plan (DMP) | Affiliate governance document specifying ownership, quality rules, and reporting readiness; prerequisite before scaling dashboards (Colombani foundations-first narrative). | Colombani, Mourot, Vallejo-Vaca | DMP **precedes** data quality; Collibra **tracks** DMP migration |
| ISO 21838-2 (ISO) | International standard codifying Basic Formal Ontology; NCOR audit benchmark for TE Business Objects alignment. | Leclerc, Guillermou, Boulanger | ISO **defines** BFO |
| ISO 14224 | Equipment taxonomy and failure mode standard referenced for Cognite LPG model alignment. | Jouret, Boulanger | Used alongside CFIHOS and SIFOS |
| PPDM, OSDU, Allotrope | Industry standards for subsurface and laboratory data modeling reviewed in cross-branch consistency work. | Boulanger | Bridge business language to platform implementation |

### HOW-IT-IS (Qualities)

| Concept | Definition | Stakeholders | Related concepts / edges |
|---------|------------|--------------|--------------------------|
| Data quality (DQ) | Measurable completeness, accuracy, and conformance of operational and governance data before executive reporting. | Colombani, Vallejo-Vaca, Guillermou | DMP **precedes** DQ; COL **tracks** DQ |
| Lineage traceability (LIN) | Traceable provenance of data lineage and concept ownership for compliance and COMEX reporting. | Campan, Mourot, Vallejo-Vaca | DQ **requires** LIN; Collibra exposes lineage metadata |

### WHY (POTENTIAL) (Realizable Entities)

| Concept | Definition | Stakeholders | Related concepts / edges |
|---------|------------|--------------|--------------------------|
| Semantic authority (SA) | Organizational role owning and governing concept definitions across domains and platforms; currently implicit in TSF maintainers. | Leclerc, Guillermou, Boulanger | SA **governs** DPC; SA **manages** TSF positioning |
| Data governance (DG) | Operational accountability for data quality, lineage, and ownership at affiliate and domain level. | Guillermou, Mourot, Colombani, Vallejo-Vaca | DG **uses** Collibra |
| Interoperability (INT) | Capability to exchange and consume meaning across Cognite, Collibra, Fabric, search, and AI platforms. | Mourot, Vallejo-Vaca, Maze, Teixugueira-de-Castro | API access **enables** INT |
| API access (API) | Technical capability to expose semantic assets as queryable services for AI, search, and platform teams. | Maze, Soleilhavoup, Vallejo-Vaca | API **enables** INT |
| Auditability | Traceability of lineage and concept provenance for investment-ready LifeX and COMEX outputs. | Campan, Guillermou, Mourot | Requires LIN and governed DPC |
| Platform integration | Operating model connecting TSF outputs to Cognite, Collibra, Fabric, and search without competing authority. | Teixugueira-de-Castro, Soleilhavoup, Vallejo-Vaca | TSF as **service**, not rival platform |
| Modeler ownership | Named modeler roles responsible for maintaining conceptual models across branches and Cognite delivery. | Boulanger, Teixugueira-de-Castro, Jouret | Bridges business concepts to implementable models |

---

## Material Entities (legacy grouping)

Concrete systems, platforms, and physical programmes:

- **TSF**, **SousLeSens**, **Cognite CDF**, **Collibra**, **Microsoft Fabric**, **LifeX**, **Business Objects**, **GPU infrastructure**

Referenced in benchmark context but not on the knowledge graph slide: Palantir (knowledge graph comparator in Workstream 2).

---

## Processes

Workflows surfaced as direct operational needs:

- Semantic mapping, ontology vetting, job card transfer, data product creation, RAG pipeline, semantic contextualization, ML training, DMP completion, standards semanticization

---

## Realizable Entities

Capabilities, roles, and functions not yet formally assigned:

- Semantic authority, data governance, interoperability, API access, auditability, platform integration, modeler ownership

---

## Qualities / Information Entities

Formal knowledge structures and observable attributes:

- **Information:** BFO, OWL, SKOS, CFIHOS (CFI), controlled vocabulary (CV), Data Management Plan (DMP), ISO 21838-2 (ISO), ISO 14224, PPDM/OSDU/Allotrope
- **Qualities:** data quality (DQ), lineage traceability (LIN)

---

## Relationships

Directed relationships from interview content and the Knowledge Graph slide. Arrow direction: subject → relation → object.

| Subject | Relation | Object | Edge type on slide |
|---------|----------|--------|-------------------|
| TSF | grounded in | BFO | structural |
| SousLeSens | part of | TSF | structural |
| SousLeSens | enables | Semantic mapping | structural |
| Ontology vetting | validates | TSF | structural |
| CFIHOS | aligns with | BFO | structural |
| ISO 21838-2 | defines | BFO | structural |
| BFO | formalized in | OWL | structural |
| Data Management Plan | precedes | Data quality | governance |
| Collibra | tracks | Data quality | governance |
| Data quality | requires | Lineage traceability | governance |
| Semantic mapping | produces | Controlled vocabulary | structural |
| Job card transfer | requires | Semantic mapping | structural |
| LifeX cycle | triggers | Job card transfer | operational chain |
| LifeX | occurs in | Pazflor / Dalia FPSOs | structural |
| Cognite CDF | consumes | TSF | structural |
| Data governance | uses | Collibra | structural |
| Semantic authority | governs | Data product creation | governance |
| API access | enables | Interoperability | structural |
| Controlled vocabulary | grounds | RAG pipeline | structural |
| LifeX | requires | Data product creation | operational chain |
| Data product creation | governed by | Semantic authority | governance |

---

## Stakeholder ↔ Concept Matrix

| Concept | Stakeholders | Bucket |
|---------|-------------|--------|
| TSF | Leclerc, Guillermou, Boulanger, Teixugueira-de-Castro, Jouret, Mourot | WHAT/WHO |
| SousLeSens | Leclerc, Boulanger, Mourot | WHAT/WHO |
| Cognite CDF | Teixugueira-de-Castro, Jouret, Soleilhavoup, Colombani, Vallejo-Vaca | WHAT/WHO |
| Collibra | Mourot, Soleilhavoup, Guillermou, Colombani | WHAT/WHO |
| LifeX / LifeX cycle | Campan, Leclerc, Jouret, Teixugueira-de-Castro | WHAT/WHO / WHEN |
| Business Objects | Leclerc, Guillermou, Mourot | WHAT/WHO |
| Pazflor / Dalia FPSOs | Campan, Leclerc, Jouret | WHERE |
| Block 17 Angola | Campan, Leclerc | WHERE |
| Semantic mapping | Boulanger, Jouret, Leclerc, Mourot | HOW-IT-HAPPENS |
| Ontology vetting | Leclerc, Boulanger, Guillermou | HOW-IT-HAPPENS |
| Job card transfer | Campan, Leclerc | HOW-IT-HAPPENS |
| Data product creation | Soleilhavoup, Campan, Jouret, Teixugueira-de-Castro | HOW-IT-HAPPENS |
| RAG pipeline | Maze, Jallais, Vallejo-Vaca | HOW-IT-HAPPENS |
| DMP lifecycle | Mourot, Colombani, Vallejo-Vaca | WHEN |
| BFO alignment | Leclerc, Boulanger, Guillermou | HOW-WE-KNOW |
| OWL | Leclerc, Boulanger, Maze | HOW-WE-KNOW |
| SKOS | Leclerc, Boulanger, Jallais | HOW-WE-KNOW |
| Data Management Plan (DMP) | Colombani, Mourot, Vallejo-Vaca | HOW-WE-KNOW |
| ISO 21838-2 | Leclerc, Guillermou, Boulanger | HOW-WE-KNOW |
| CFIHOS / ISO standards | Leclerc, Jouret, Boulanger | HOW-WE-KNOW |
| Controlled vocabulary | Jallais, Maze, Boulanger | HOW-WE-KNOW |
| Data quality (DQ) | Colombani, Vallejo-Vaca, Guillermou | HOW-IT-IS |
| Lineage traceability (LIN) | Campan, Mourot, Vallejo-Vaca | HOW-IT-IS |
| Semantic authority | Leclerc, Guillermou, Boulanger | WHY (POTENTIAL) |
| Data governance | Guillermou, Mourot, Colombani, Vallejo-Vaca | WHY (POTENTIAL) |
| Interoperability | Mourot, Vallejo-Vaca, Maze, Teixugueira-de-Castro | WHY (POTENTIAL) |
| API access / API boundary | Maze, Soleilhavoup | WHY (POTENTIAL) |
| Platform integration | Teixugueira-de-Castro, Soleilhavoup, Vallejo-Vaca | WHY (POTENTIAL) |
| ROI gate | Soleilhavoup, Teixugueira-de-Castro | WHY (POTENTIAL) |
| Smart search | Jallais, Vallejo-Vaca | HOW-IT-HAPPENS |
| Agentic search / AI copilots | Vallejo-Vaca, Maze, Jallais | HOW-IT-HAPPENS |
| Conceptual modeling | Boulanger, Jouret | HOW-IT-HAPPENS |
| OPEX / CAPEX grounding | Campan, Soleilhavoup, Guillermou | WHEN / WHY (POTENTIAL) |
| Affiliate readiness | Colombani, Vallejo-Vaca | WHY (POTENTIAL) |
| Modeler ownership | Boulanger, Teixugueira-de-Castro, Jouret | WHY (POTENTIAL) |

**Stakeholder map (slide 3) layers:**

| Layer | Interviewees | Posture |
|-------|-------------|---------|
| Standards and Innovation | Leclerc, Guillermou, Boulanger | Strong advocates / institutional supporters |
| Data Platforms | Teixugueira-de-Castro, Jouret, Soleilhavoup, Mourot, Vallejo-Vaca, Colombani | Pragmatic platform owners; Soleilhavoup = ROI gate |
| AI and Search | Maze, Jallais | API and vocabulary consumers |
| Operations and Business | Campan | Mission-critical LifeX consumer |

---

## Divergences / Tensions

Key disagreements and framing gaps surfaced across interviews:

| Tension | Advocates / skeptics | What interviews revealed |
|---------|---------------------|--------------------------|
| **ROI gate** | Soleilhavoup, Teixugueira-de-Castro vs Leclerc, Boulanger | Platform and product architects require proof in money, time, or safety before investing in ontology work. Standards advocates accept longer horizons but need LifeX as the measurable case. |
| **Platform vs neutral semantic layer** | Teixugueira-de-Castro, Soleilhavoup vs Leclerc, Guillermou | Cognite and data-product teams want TSF positioned as a **capability inside** the data-platform reference model, not a competing authority. TSF maintainers want vendor-neutral, ISO-grounded meaning owned by TotalEnergies. |
| **Catalog vs semantic layer** | Mourot, Colombani vs Leclerc, Boulanger | Collibra owners need a clear perimeter: catalog governance (ownership, lineage, DMP) vs SousLeSens semantic modeling. Without agreed mapping of Business Objects into Collibra, both tools drift apart. |
| **Foundations first** | Colombani, Guillermou vs innovation urgency | Affiliate readiness, DMP completeness, and data quality are prerequisites before scaling dashboards or semantic outputs. Semantic pilots risk rejection if ownership and quality foundations are not explicit. |
| **Graph enough without ontology** | Cognite delivery narrative vs TSF team | Some platform messaging implies operational graphs suffice without formal ontology. Modeling teams (Jouret) and standards teams disagree: value is enrichment and contextualization relational models cannot express. |
| **Portfolio navigability** | Guillermou, management audiences vs Leclerc portfolio breadth | TSF innovation is technically mature but dispersed. Sponsors cannot navigate the project inventory or see connections to business outcomes without packaging and prioritization (LifeX first). |
| **Embedded experts vs remote platform build** | Campan vs platform-centric delivery | Operations wants domain experts embedded in weekly LifeX workflows, not semantic work happening "three floors up" in platform dashboards. |

**Convergent finding:** No stakeholder disputes that shared meaning matters. The blocker is the missing operational proof point where absent semantics produced traceable cost, delay, or decision error. LifeX is the agreed anchor.

---

## Source References

### Interview transcripts (primary)

| Stakeholder | Transcript file |
|-------------|----------------|
| Jean-Charles Leclerc | `Jean-Charles_Leclerc/SLS_TSF.docx`, `Jean-Charles_Leclerc/Memo PJC - Data Exposition - JCL_To_NT.docx`, `Jean-Charles_Leclerc/CR-OT-DAT-012_01+EN.docx` |
| Benoit Guillermou | `Benoit_Guillermou/Jeremy RAVENEL_Benoit GUILLERMOU (TotalEnergies) - Interview  (1).docx` |
| Josephine Boulanger | `Josephine_Boulanger/Jeremy RAVENEL_Josephine BOULANGER (TotalEnergies) - Interview  (2).docx` |
| David Teixugueira-de-Castro | `David_Teixugueira-De-Castro/Jeremy RAVENEL_David TEIXUGUEIRA-DE-CASTRO (TotalEnergies) - Interview .docx` |
| Bastien Jouret | `Bastien_Jouret/Jeremy RAVENEL_Bastien JOURET (TotalEnergies) - Interview  (2).docx` |
| Benoit Soleilhavoup | `Benoit_Soleilhavoup/Jeremy RAVENEL_Benoit SOLEILHAVOUP (TotalEnergies) - Interview  (1).docx` |
| Francois-Xavier Mourot | `Francois-Xavier_Mourot/Jeremy RAVENEL_Francois Xavier MOUROT (TotalEnergies) - Interview .docx` |
| Sonia Vallejo-Vaca | `Sonia_Vallejo-Vaca/Jeremy RAVENEL_Sonia VALLEJO-VACA (TotalEnergies) - Interview  (1).docx` |
| Pascal Colombani | `Pascal_Colombani/Jeremy RAVENEL_Pascal COLOMBANI (TotalEnergies) - Interview .docx`, `Pascal_Colombani/Entretien - Pascal Colombani (EP Data Officer).docx` |
| Elie Maze | `Elie_Maze/Jeremy RAVENEL_Elie MAZE (TotalEnergies) - Interview.docx` |
| Pierre Jallais | `Pierre_Jallais/Jeremy RAVENEL_Pierre JALLAIS (TotalEnergies) - Interview .docx` |
| Julien Campan | Synthesized from archive delivery narrative and stakeholder deck profiles (no standalone `.docx` transcript in WS1 folder) |

### Supporting synthesis sources

- `TotalEnergies_SKG_Stakeholder_Perspective_Summary.html` (Knowledge Graph slide 4, Stakeholder Map slide 3, 12 profile slides)
- `archive/skg-communication-kit-delivery/src/content.md` (Interview Findings, TSF positioning, LifeX business case)
- `TotalEnergies_SKG_Workstream1_Pain_Point_Matrix.xlsx`
- `Interviews Checklist.xlsx`

### BFO / ontology references

- `assets/ontology/te_interviews_ontology.html` (interview concepts mapped to BFO 7 buckets; slide 4 embed source)
- `docs/ontology/bob_ontology.html` (canonical BFO bucket layout reference)
- `docs/ontology/BFO7Buckets.ttl`
- `docs/ontology/ontology.md`

---

*Last updated: June 2026. Knowledge Graph slide 4 uses static inline SVG (viewBox 0 -48 1180 590, export-safe). Slide nodes: MAP, VET, JCT, DPC, RAG, LXC, TSF, SLS, LX, CDF, COL, FPSO, BFO, CV, DMP, OWL, SKOS, ISO, CFI, DQ, LIN, SA, DG, API (24 nodes, 11 semantic relationships). Full extract lists 30+ concepts.*