u/SiefensRobotEmporium

Every AI chat today works like a goldfish. It only remembers whatever fits inside a rolling context window. Once the window moves, the AI forgets. This is why hallucinations happen and why companies keep building expensive RAG systems and knowledge silos to patch the same problem.

A better approach already exists. It is a XanaNode substrate.

In XanaNode, every message in a conversation becomes a real node. For example:

- **event** for the timestamp of the message

- **person** for who said it

- **claim** for what was said

- **fragment** for the exact text

- **knowledge_gap** if the user expresses uncertainty

- **question** when the user asks something

- **response** when the AI answers

And the relationships between them are typed and explicit:

- **supports**

- **contradicts**

- **derived_from**

- **explains**

- **transcludes**

- **possible_match**

This means the conversation is not a blob of text. It becomes a structured knowledge graph with provenance and lineage.

If AI used this as its context, it would not need to re‑read the entire conversation every time. It would not lose track of what happened earlier. It would not need a bigger token window. It would query the substrate the same way humans query memory.

This does not make hallucinations disappear. LLMs are still next‑token predictors. But it gives them grounding, structure, and a real memory system instead of a sliding text buffer.

Companies are spending billions on RAG, vector databases, and “show your sources” audits. All of this is trying to fix the same missing piece. AI needs a real memory architecture.

A XanaNode substrate is that architecture.

I've started a new project under Mr Siefen's Robot Emporium called XanaNode.

The short version:

XanaNode is an attempt to build an open protocol for interoperable knowledge substrates — systems where relationships, provenance, claims, sources, contradictions, fragments, and context are treated as first-class parts of knowledge instead of being lost inside documents.

It is not a wiki.

It is not a graph database.

It is not another note-taking app.

It is a framework for preserving, navigating, publishing, and federating structured knowledge across independently authored systems. The main protocol models knowledge as connected people, concepts, claims, sources, events, media, organizations, technologies, and relationships.

The project is split into a few repositories:

XanaNode

The core protocol, ontology, schemas, registries, examples, governance model, and validation rules. The main idea is that documents are not enough. Knowledge lives in provenance, lineage, evidence, contradiction, explanation, association, and context.

XanaNode Core SDK

A renderer-independent SDK for reading Markdown nodes, parsing YAML front matter, generating protocol IDs, building typed relationships, creating fragments, detecting xana:// references, validating artifacts, and exporting protocol files. It provides CLI commands for init, validate, build, and inspect.

XanaNode Workspace

A local-first workspace engine that sits between the protocol and future user interfaces. It initializes substrates, manages .xananode workspace state, handles authors, imports and assets, wraps Git as human-friendly snapshots, computes knowledge health, and builds through the Core SDK.

XanaNode Hugo

A Hugo implementation of the protocol. It can publish human-readable pages, a relationship graph, substrate data, relationship data, node exports, schemas, fragment data, and review suggestions for links and transclusions.

XanaNode Studio

The early Studio repository is for a local-first desktop application for creating, managing, and publishing XanaNode substrates with structured relationships, provenance, federation, and built-in version history.

I also registered:

XanaNode.com

XanaNode.org

XanaNode.net

The long-term goal is fairly ambitious: a federated knowledge system where knowledge stays locally owned, relationships stay visible, disagreement is preserved, and AI systems can work with structured context instead of chewing through piles of disconnected text.

Or, stated less dramatically:

I want better plumbing for knowledge.

Something open.

Something portable.

Something that does not require surrendering everything to one platform, one app, one database, or one AI vendor.

Still early.

Still experimental.

Very much under construction.

But the bones are there.

I'd love feedback from people interested in:

• Knowledge graphs

• Provenance

• Semantic publishing

• AI memory and context systems

• Static sites

• Local-first tools

• Project Xanadu style transclusion

• Open protocols

What would make a system like this useful to you?

For the last few years I've been exploring a problem that I suspect is becoming increasingly important as AI systems become more capable.

​

The tldr version is that I think we've spent decades optimizing for publishing documents while largely neglecting the structure that connects them.

​

Vannevar Bush pointed at this problem in 1945 with Memex and associative trails. Doug Engelbart, Ted Nelson, Project Xanadu, Hyperland (Douglas Adams), and others continued exploring related ideas. Yet most of the modern web still treats the document as the primary unit of knowledge and the hyperlink as a very thin connection between documents.

​

A link tells us that one thing points at another.

​

It usually doesn't tell us whether the relationship is:

​

* evidence for

* contradiction of

* extension of

* derived from

* influenced by

* revision of

* example of

* authored by

​

Humans reconstruct those relationships from context. Machines generally don't.

​

What originally got me interested was AI hallucinations and agent failures. The more I looked at the problem, the more it seemed like many failures attributed to AI might actually originate in the underlying knowledge substrate. If provenance, authority, evidence chains, and relationship structure are weak, the systems built on top of them inherit those weaknesses.

​

That led me down a rabbit hole I now call "The Lost Lineage."

​

There seems to be a partially forgotten lineage of ideas running from Bush → Engelbart → Nelson → Hyperland and beyond that focused on relationships, provenance, transclusion, and associative navigation rather than documents.

​

I've started building a prototype called XanaNode.

​

The core idea is that relationships become first-class objects rather than metadata hidden inside documents.

​

Instead of a graph where nodes are mostly articles and edges are generic links, I'm experimenting with a system where:

​

* concepts are built from claims

* claims are supported by evidence

* sources preserve provenance

* media preserves authorship and lineage

* relationships have explicit types and weights

* contradictory explanations can coexist

* navigation follows explanatory paths rather than folders or categories

​

I'm not claiming this is a new idea. In many ways it feels like revisiting and extending ideas that have existed for decades but never became dominant.

​

What I'm trying to figure out now is:

​

1. What existing systems have explored this space well?

2. What failure modes would you expect from a relationship-first knowledge system?

3. How would you handle governance, versioning, competing interpretations, and conflicting claims at scale?

4. Are there research areas, papers, or projects I should be looking at that I may have missed?

​

I'd especially love input from people working in knowledge representation, databases, hypermedia, information retrieval, HCI, digital libraries, semantic systems, or agent architectures.

​

I'm interested in criticism as much as validation. The goal isn't to build a prettier wiki. The goal is to understand whether there are missing primitives in how we represent and navigate knowledge itself.

​

The current prototype lives at: builtbybots.com which was an AI generated blog site that I realized was actually helping me discover the problem. I have trashed all of that and put the begining of XanaNode there. It's not great, it's not even fully up to the schema I wrote. It's at a point where I really want to see what others think before I go too far down the rabbit hole.

​