Monday, October 12, 2026

AI-XF — AI eXchange Format

A portable, vendor-neutral format for curated knowledge that both humans and AI agents produce and consume. It adds what a reasoning agent needs on top of a folder of markdown: stable identity, typed relationships, provenance, media identity, federation, and change semantics.


AI-XF is a strict superset of Google Cloud's Open Knowledge Format (OKF) v0.2. Every AI-XF bundle is also a valid OKF bundle: OKF-only agents read it today, AI-XF-aware agents read the same files and see more.


Spec SPEC.md — v0.5 released; v0.6 proposed (one resolution order across bundles)

Experiments experiments/ — runnable evidence: federation (E1–E7), freshness and interoperability (E8–E9), maturity journeys into a database, from a wiki and into another system (E10–E12), canonical form and withheld links (E13–E14), resolution order with an independent implementation (E15); numbers in RESULTS.md

Curation policy (non-normative) CURATOR.md — seven rules and four numbers to paste into an agent's instructions

Worked example examples/ — passes the validator at Level 3

Validator tools/ai-xf-validate.py — conformance ladder, --stats (curation health and freshness), --federation, --resolve (explains how one link resolves); no dependencies

Canonical form (v0.5) tools/ai-xf-canon.py — writes the one canonical serialisation of a concept and its sha256: content hash (SPEC §5.7, Appendix D); needs PyYAML



The idea in one paragraph

Keep knowledge as markdown files with YAML frontmatter, exactly as OKF says. Give each concept a permanent id so files can move. Give each link a rel so an agent knows whether B replaces A or B depends on A. Carry OKF's trust fields unchanged so a human-reviewed concept means the same thing in every bundle. Give binary assets a content hash so a diagram keeps its identity when it moves. Let bundles from different teams cite each other by namespace/id. Record what happens when new knowledge meets old: an open contradiction, a merge, a claim gaining support. And when a concept leaves, keep it as a tombstone that says so, rather than deleting it. Everything stays "just files"




No comments:

Post a Comment