about
I'm an Ontologist first. That's the bread and butter underneath everything else: deciding what things fundamentally are, and how they relate, before anyone gets to argue about what to call them.
Twenty years in, the honest answer to "what do you do" stopped being a single job title a while ago. Four things that only make sense together, add up to the title, not the other way around.
Ontological Engineer + Docs as Product Builder + Docs Engineering = Knowledge Architect
AI Knowledge Architect│├── Product│ ├── Roadmaps│ ├── RAG│ ├── Analytics, Insights & Feedback│ ├── Flex Product ← Kraken's Energy Flexibility product line│ └── User Persona Development ← persona-centred docs + resolution tracking│├── Tactical / Process / Ops│ ├── Translation ← AI-first, 10+ languages, Kraken│ ├── Governance ← single-source-of-truth content governance│ └── Forensics at scale ← the doc forensics practice│├── Docs Engineering / Tooling│ └── Docs Engineering + Knowledge Engineering (decision traces, not just decisions)│└── Research├── Context Graphs├── Knowledge Graphs├── Ontology├── MCP vs Skills└── Grid project ← the applied research domain
the same structure, as a graph
[ SVG graph diagram — placeholder ]Generated externally from the BinoyWatts Cypher query and embedded here.
currently learning
The Research pillar above isn't a list of things I've settled. It's a live watch list, and it changes as fast as I do.
- Where context graphs actually diverge from knowledge graphs in production, not just in definition
- MCP versus skills as competing distribution models for how an agent learns your product
- What the grid project keeps teaching me about applying all of this somewhere the stakes are real