LoreSpec – Structured knowledge extraction from AI conversations
Captures Toulmin argument structure for decisions when most tools just store flat facts.
goes through a video and captures notes and diagrams from the conversation
Smart frame filtering plus knowledge graph extraction—useful but Fireflies.ai and Otter.ai exist.
Knowledge workers, meeting organizers, training teams
Fireflies.ai · Otter.ai · Sembly AI
How it works:
- Extracts frames using change detection (not just every Nth frame), with periodic capture for slow-evolving content like screen shares - Filters out webcam/people-only frames automatically via face detection - Transcribes audio (OpenAI Whisper API or local Whisper — no API needed) - Sends frames to vision models to identify and recreate diagrams as Mermaid code - Builds a knowledge graph (entities + relationships) from the transcript - Extracts key points, action items, and cross-references between visual and spoken content - Generates a structured report with everything linked together
Supports OpenAI, Anthropic, and Gemini as providers — auto-discovers available models and routes each task to the best one. Checkpoint/resume so long analyses survive failures.pip install planopticon planopticon analyze -i meeting.mp4 -o ./output
Also supports batch processing of entire folders and pulling videos from Google Drive or Dropbox.Example: We ran it on a 90-minute training session: 122 frames extracted (from thousands of candidates), 6 diagrams recreated, full transcript with speaker diarization, 540-node knowledge graph, and a comprehensive report — all in about 25 minutes.
Python 3.10+, MIT licensed. Docs at https://planopticon.dev.
Captures Toulmin argument structure for decisions when most tools just store flat facts.
Knowledge graph generation from papers, but Elicit and Consensus already do literature synthesis.
Provenance-first RAG beats anonymous text chunks, but Cursor and Continue already own this space.
LLM infers schema once, Go does 10k-row extraction—avoids token waste.
Extracts tracked changes and comment threads when most DOCX parsers only grab text.
Learns from Claude Code failures, stores insights—but requires Ollama and unclear workflow impact.