Model, edit, and validate iNNfo knowledge models
iNNfo is the hub for the iNNfo ecosystem. The iNNfo Modeler opens any workspace folder in a single tree-driven editor, and @cognnitive/innfo-core parses, resolves, and validates every model against the spec chain.
Open a folder — parse, edit, and validate iNNfo models in one place, right in the browser.
What is iNNfo?
A monorepo that ties the iNNfo ecosystem together: the iNNfo Modeler editor, the innfo-core library, an MCP server for AI agents, and the full spec chain.
iNNfo Modeler
The innfo-editor app — a Vue 3 workspace editor. Open any folder, parse it
into one normalized model tree, edit nodes with metamodel-driven forms and block
sheets, and validate against the iNNfo spec — all in the browser.
@cognnitive/innfo-core
The shared TypeScript library — parser, spec-chain resolver, and validator. Framework agnostic, with IO drivers for the browser and Node. Both the Modeler and the MCP server run on top of it.
@cognnitive/innfo-mcp
A Model Context Protocol server that exposes iNNfo as semantic tools — list, read, validate, and safely mutate models — so any MCP-capable AI agent can work with your models directly.
How the iNNfo Modeler works
Three steps from folder to a validated, editable model.
Open workspace
Pick a folder via the File System Access API — or resume a recent one. The Modeler stores the handle in IndexedDB for a fast reopen, no re-upload needed.
Single parse pass
One recursive pass walks the workspace. Each _NN.md file becomes a model
node and its structural children fold into the same normalized tree — concepts,
elements, fields, markers, and matrices in one graph.
Edit & validate
Select any node in the sidebar tree and edit it in block sheets or a table view. Validation runs automatically on every parse — a status badge surfaces the full compliance report against the spec.
Ecosystem Architecture
The four-level spec chain that powers every iNNfo model.
defiNNe
The meta-specification. Defines structure, versioning, and RFC 2119 conventions for the entire ecosystem — the rules every other level follows.
iNNfo
The central specification. A single-file _NN.md model with YAML
frontmatter and a unified system of concepts, elements, markers, and relationships.
Templates
Domain templates: business, procedures, and organization. Each declares its concepts, markers, and matrices on top of the iNNfo spec.
Models
Concrete data instances like Ghostbusters (business) or Engineering Team (organization). Lightweight — just data and a pointer to their parent template.
Built for AI agents
iNNfo is plain Markdown, so any coding agent can read it. iNNfo adds the tools to let them model, generate, and transform with you.
innfo-mcp server
A stdio MCP server exposing seven semantic tools — list_models,
read_model, get_spec, get_template,
validate_model, apply_change, and
validate_model_url — so agents mutate models safely and re-validate on
every step.
Import & Export pipeline
The Modeler's Import and Export panels generate a ready-to-run agent prompt. Drop
sources into traNNsform/input/ to turn them into iNNfo models, or export a
model to a self-contained HTML visualizer in traNNsform/output/.
Use iNNfo with AI
A built-in checklist connects your workspace to an external coding agent — Claude Code, Google Antigravity, or OpenCode — with step-by-step guidance you can track as you go.
100% compatible with Open Knowledge Format
Every iNNfo document is a valid OKF knowledge bundle. The iNNfo specification is a strict superset of OKF v0.1.
Shared substrate
OKF and iNNfo share the same base format: Markdown files with YAML frontmatter. No
proprietary tooling, no centralized schema registry. If you can read Markdown, you can
read both formats — cat a file to read it, git clone a repo
to ship it.
OKF conformance met
OKF v0.1 requires: (1) parseable YAML frontmatter on every non-reserved
.md file, (2) a non-empty type field, (3) reserved filenames
following OKF conventions. iNNfo meets all three: every _NN.md has
frontmatter, the level+template system provides type semantics, and
index.md follows the same progressive-disclosure convention.
Extensions tolerated
OKF explicitly states:
"consumers MUST NOT reject a bundle because of unknown additional frontmatter keys,
unknown type values, or missing optional fields."
iNNfo adds spec_version, level, parent,
concepts, markers, matrices — all tolerated by
OKF consumers.
A workspace = an OKF Bundle
An iNNfo workspace is exactly the directory-of-Markdown-files structure OKF defines as
a knowledge bundle. Each _NN.md maps to an OKF
concept document. Wikilinks [[target]] and standard Markdown
links coexist for cross-linking between concepts.
Monorepo at a glance
npm workspaces: one editor app, three packages, the spec chain, and the traNNsform pipeline.
├── apps/
│ └── innfo-editor/ // Vue 3 workspace editor — the iNNfo Modeler
├── packages/
│ ├── innfo-core/ // TS parser, resolver, validator
│ ├── innfo-mcp/ // MCP server for AI agents
│ └── pipeline-gates/ // Validation & integration gates
├── specs/ // defiNNe, iNNfo, templates, samples
├── traNNsform/ // Agent-driven import/export pipeline
└── docs/ // This website
Sample Models
Three ready-to-open iNNfo models — one per template — ship with the repo. Open any of them in the Modeler to explore the tree, edit nodes, and validate against the spec chain.
Ghostbusters
A complete business model for a fictional ghost-catching franchise. Covers analysis
(SWOT, risks, assumptions), business idea, objectives, market segments, finance,
legal, and operations — a single _NN.md with the full concept tree.
specs/latest/level2/business/samples/Ghostbusters_V_0-1-2_business_NN.md
Code Review Process
A structured procedure for PR-based code reviews: roles (Author, Reviewer,
Maintainer), a step-by-step workflow with tool bindings, artifacts (checklist,
report), and an expedited hotfix path — one _NN.md document.
specs/latest/level2/procedures/samples/CodeReviewProcess_V_1-0-0_procedures_NN.md
Engineering Team
An organization model mapping an engineering team — roles, structure, and the relationships between them — built on the organization template. The starting point for modeling how a team actually works.
specs/latest/level2/organization/samples/EngineeringTeam_V_1-0-0_organization_NN.md
Get in Touch
Questions about the ecosystem or the Modeler? We'd love to hear from you.