Public Q&A, patterns, and announcements for graph-native intelligence.
→ Discussions · kenningai.com
This repo isn't code. It's the home for Discussions. The rest of Kenning AI lives at kenningai.com and in the other repos on this org.
Q&A — Architecture questions, modeling problems, debugging help. How would you structure this ontology? Why does traversal explode when I add this edge? Is this a temporal problem or an indexing problem? Post freely — the answers compound into a searchable reference.
Patterns — Canonical use cases, written up as small architecture walkthroughs. Each one: a diagram, 200–400 words, the decision points worth thinking about. Early patterns will cover fraud triage with the graph as reviewer-memory, temporal knowledge transfer between agents, and federated ontology joins across disconnected data domains.
Announcements — Releases, talks, papers. Low volume, maintainer-only posts.
General — Everything else.
- Be precise. Vague questions get vague answers.
- Search before posting — the forum exists so questions compound instead of repeat.
- No product pitches. No recruiter DMs. This is a technical space.
- Disagreement is welcome. Condescension isn't.
- mcp-temporal-knowledge — Temporal knowledge graph memory for AI agents
- sec-engine — MCP server exposing SEC EDGAR financial data to LLMs
In Old Norse poetry, a kenning names things not by what they are, but by their relationships to other things. A ship is a "wave-steed." The ocean is "whale-road." The sun is "sky-candle." The thing has no meaning in isolation — meaning is constituted by relationship.
That's the thesis. This is where we build it in public.