An open model, specification, and interoperability protocol for preserving the evolution of collective knowledge.
NEMO addresses a problem shared by technical, creative, scientific, analytical, and operational teams: knowledge is generated continuously, but its reasoning, provenance, alternatives, and evolution are usually scattered across tools and eventually lost.
NEMO is designed to preserve not only what a team knows, but how that knowledge appeared, changed, was challenged, gained evidence, became a decision, and influenced action.
NEMO combines four complementary elements:
- A conceptual model for knowledge objects and their relationships.
- An open specification defining minimum semantics and conformance.
- An interoperability protocol for exchanging knowledge between tools, agents, repositories, and workspaces.
- A NEMO-Ready model for declaring and testing implementation support.
NEMO is not tied to software development. It is applicable to any team involved in design, investigation, analysis, implementation, experimentation, decision-making, or long-lived complex work.
NEMO preserves the evolution of collective knowledge.
Documents, code, conversations, tickets, experiments, diagrams, and reports are artifacts or sources. NEMO connects them into a traceable knowledge history.
NATIA is intended to become the first official support platform and reference implementation of NEMO.
In other words:
NATIA is NEMO-Ready.
NATIA does not define the standard. NEMO remains independent so that other products, repositories, agents, and platforms can implement it.
RFC-0001: NEMO Foundation— initial scope, principles, terminology, architecture, interoperability model, governance direction, and NEMO-Ready foundation.
During the founding phase, accepted editorial work is written directly to main. Numbered RFCs are the canonical mechanism for evolving NEMO.
docs/00-VISION.md— purpose, scope, principles, and non-goals.docs/01-CORE-MODEL.md— core knowledge objects and relationships.docs/02-SPECIFICATION.md— initial normative requirements and portable representation.docs/03-PROTOCOL.md— protocol capabilities and operations.docs/04-NEMO-READY.md— proposed implementation conformance levels.
WORKFLOW.md— original working conventions and semantic marks.architecture/— transversal architecture notes.projects/— project and research-line notes.
These materials preserve NEMO's origin as a practical technical-memory repository. They will be progressively aligned with the broader specification without erasing their history.
NEMO is currently at 0.1-draft.
The immediate objective is to stabilize vocabulary, core semantics, object representation, and the first transport binding before claiming formal interoperability.
- Continuity over accumulation.
- Provenance by default.
- Evidence and belief are different.
- Conversations are sources, not final truth.
- Knowledge must remain portable.
- Human and artificial contributors coexist.
- Evolution must remain visible.
- Implementations may differ; semantics must survive.