惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

U
Unit 42
F
Fortinet All Blogs
Martin Fowler
Martin Fowler
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
IT之家
IT之家
Blog — PlanetScale
Blog — PlanetScale
罗磊的独立博客
V
V2EX
Vercel News
Vercel News
Apple Machine Learning Research
Apple Machine Learning Research
J
Java Code Geeks
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
Tailwind CSS Blog
I
InfoQ
Engineering at Meta
Engineering at Meta
WordPress大学
WordPress大学
S
SegmentFault 最新的问题
H
Help Net Security
腾讯CDC
D
Docker
P
Proofpoint News Feed
GbyAI
GbyAI
博客园 - 三生石上(FineUI控件)
aimingoo的专栏
aimingoo的专栏

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
MemoryGraph – Git for knowledge, built to capture researc...
Altea Vane · 2026-05-08 · via DEV Community

Altea Vane

The problem nobody talks about

$100B+ is wasted annually in research duplication.
Economists estimate that the failure to share negative results
burns between 5% and 10% of the entire global research budget
every year.

Not because researchers are lazy or careless.
Because no infrastructure exists to capture what
doesn't work — without asking for extra effort.

The root cause is publication bias.

Labs fund projects based on partial or incorrect assumptions
because they don't know about failed attempts elsewhere.
They end up blindly replicating the same mistakes.

The consequences are concrete:

If lab A doesn't publish the failure of formula X,
labs B, C, and D will spend months of work and precious
rare materials synthesizing and testing the same
useless formula independently.

This happens every day. Across every scientific discipline.

The failed hypothesis at 11pm.
The dead end that took three weeks.
The pivot that would have saved the next person three months.

This knowledge disappears. Into lab notebooks nobody reads,
or nowhere at all.

Every existing tool — Notion, Obsidian, Roam — asks for
a deliberate act of documentation after the work is done.
More work. No reward. No adoption.

The idea

What if the research process left a trace automatically,
as a side effect of thinking?

That's MemoryGraph.

Every unit of thought lives as a typed node in a personal
knowledge graph:

  • Observation — something you noticed
  • Hypothesis — something you believe might be true
  • Conclusion — something you've established
  • DeadEnd — something that didn't work
  • OpenQuestion — something you don't know yet

Each node carries a full temporal history — every change
in belief, every pivot, every moment confidence shifted and why.

The graph is never a snapshot. It is a recording.

Git for knowledge. Architecturally.

Git MemoryGraph
Repository Personal knowledge graph
Commit NodeState — a belief at a moment in time
Fork SubgraphToken — a signed copy of selected nodes
Diff Semantic delta between two trajectories
Pull request MergeProposal with conflict detection

When two researchers need to share knowledge, one issues
a SubgraphToken — a signed, scoped selection of nodes.
The recipient gets an isolated fork. They develop it freely.
If they find something valuable, they propose a merge.

The dark matter of research finally has a place to live.

What's built so far

  • ✅ Graph store with Kuzu (embedded, zero infra)
  • ✅ Full node versioning — nothing ever deleted
  • ✅ Memory Agent — LLM-powered entity extraction
  • ✅ Quality gate before every graph write
  • ✅ Contradiction detection
  • ✅ Link Agent — semantic edge suggestion
  • ✅ LLM-agnostic — works with Anthropic, OpenAI, or local

Stack

  • Language: Python 3.11+
  • Graph DB: Kuzu (embedded)
  • LLM: agnostic — any model via structured prompting
  • License: AGPL-3.0

Looking for

  • Researchers who want to try it on a real project
  • Builders who want to implement any phase of the roadmap
  • Critics who want to find the failure modes

github.com/alteavane/memory-graph

Open an issue. Fork the repo. Break the design.
The goal is not consensus — it's the best possible system.