Project-level knowledge base system for AI Agents, with automatic Git repository scanning, specification linting, and automated updates.
okf turns your Git repository into a living, queryable knowledge base that humans and AI Agents can use. Every piece of knowledge is a Markdown concept file with YAML frontmatter, generated from your code and documents automatically and kept up to date on every commit.
- Features
- How it works
- Installation — Quick Start (30 seconds)
- Usage
- Stable Identity, Manifest & Agent Discovery
- Documentation
- Project Structure
- Module Reference
- OKF Concept Format
- API Usage
- Lint Rules
- Build & Test
- OKF v0.2 Specification Support
- Contributing
- License
- 📁 Open Knowledge Format — Open knowledge format based on Markdown + YAML Frontmatter
- 📄 Document Import — Import PDF, DOCX, XLSX, PPTX, HTML, CSV, TXT directly (pure-Go conversion, no Python/CGO);
okf add report.pdfjust works - 🔍 Auto-Generation — Automatically generates knowledge base by scanning Git repository source code
- ⚡ Incremental Updates — Incremental updates based on Git commits
- 🛠 Git Hook — One-click installation, automatic knowledge base updates on every commit
- 📋 Lint Checking — Built-in specification compliance checker (16 rules)
- 🔎 Advanced Query — Filter by type, tags, or full-text search
- 🧠 Hybrid Semantic Search — Local natural-language search: chunk-level MiniLM embeddings + BM25, fused with weighted RRF; large imported documents also gain source-tracked derived chunks and per-source result deduplication (fully offline, no CGO)
- 🤖 Agent-facing MCP — Standard MCP tools for repository status/init/refresh/query/context plus durable note/event/feedback capture
- 🏗 Modular Architecture — Clean, layered design following Go best practices
flowchart LR
A[Your Git repository] -->|"okf init / scan"| B[.okf/knowledge<br/>Markdown concepts]
C["PDF · DOCX · XLSX · PPTX<br/>HTML · CSV · TXT"] -->|"okf add"| B
D[git commit] -->|"okf hook / sync"| B
B --> E["okf lint<br/>OKF v0.2 checks"]
B --> F["okf search / query"]
B --> G["MCP server<br/>status · init · refresh · query · context"]
G --> H[AI Agents]
Pick one of these three install methods:
Linux / macOS:
curl -fsSL https://raw.githubusercontent.com/superops-team/okf/main/scripts/install.sh | bashWindows (PowerShell):
irm https://raw.githubusercontent.com/superops-team/okf/main/scripts/install.ps1 | iexIf the one-liner fails with
Unexpected token/"parse errors (caused by proxies HTML-encoding the response), use the download-then-run method:iwr -useb "https://raw.githubusercontent.com/superops-team/okf/main/scripts/install.ps1" -OutFile install.ps1; .\install.ps1
The installer:
- Automatically detects your OS (Linux / macOS) and CPU architecture (amd64 / arm64)
- Downloads the latest pre-built binary from GitHub Releases
- Verifies SHA256 checksums
- Installs to
/usr/local/bin/(or~/.local/bin/without sudo)
go install github.com/superops-team/okf/cmd/okf@latestDownload pre-built binaries for your platform from the Releases page.
| OS | Architecture | Archive |
|---|---|---|
| Linux | amd64 (x86_64) | okf_<version>_linux_amd64.tar.gz |
| Linux | arm64 (aarch64) | okf_<version>_linux_arm64.tar.gz |
| macOS | amd64 (Intel) | okf_<version>_darwin_amd64.tar.gz |
| macOS | arm64 (Apple Silicon) | okf_<version>_darwin_arm64.tar.gz |
| Windows | amd64 | okf_<version>_windows_amd64.zip |
| Windows | arm64 | okf_<version>_windows_arm64.zip |
# Initialize knowledge base from your repo
cd /your/repo
okf init
# Show knowledge base information
okf show
# Search concepts
okf search -q "database"
# Import a real document (converts PDF/DOCX/XLSX/... to Markdown)
okf add report.pdf
# Lint check
okf lint
# Semantic (natural-language) search — build the index once, then search
okf vector index
okf search -q "check my notes for errors" -semantic
# Install Git Hook (automatic updates on every commit)
okf hook -type post-commit
# Start the MCP server for a repository. Relative --dir values resolve under --repo;
# absolute --dir values remain absolute.
okf mcp --repo /your/repo --dir .okf/knowledgeThe MCP server supports dual protocol eras from the same okf mcp entry point:
- Legacy
2024-11-05: initialize-based, 20 tools, Prompts, Resources, ping — unchanged. - Modern
2026-07-28: stateless, per-request_metavalidation,server/discover,resultType: complete+ serverInfo_metaon all success responses. One era per stdio process; mixed-era requests rejected.
The modern era exposes exactly 11 service-backed tools: okf_status, okf_init, okf_refresh, okf_query, okf_context, okf_note, okf_log, okf_feedback, okf_ask, okf_resolve, okf_manifest. Legacy bundle-state tools (okf_load_bundle, okf_search, etc.) are not available in the modern era.
A portable Agent Skill (skill://okf/SKILL.md) renders the canonical W01–W07 workflow. It is available as a Resource in both eras and via skills/list/skills/get in the modern era (client capability gate). The immutable registry provides SHA-256 digest, size validation, URI confinement, and zero knowledge-runtime I/O for Skill operations.
Writes require a stable idempotency_key, use deterministic identities, reject unknown or incorrectly typed fields, and fail closed for path escape, symlink-root, size-limit, and credential-like metadata violations. The server persists only feedback explicitly submitted by the caller; it does not inspect a host application's private event bus. See docs/knowledge/mcp-server.md and docs/knowledge/durable-capture.md.
okf search -semantic performs natural-language search over concepts, using a locally embedded MiniLM model (384-dim vectors) and an HNSW index — no network, no external runtime required. Long documents are split into heading-aware chunks, and results blend a semantic channel with a BM25 lexical channel via weighted Reciprocal Rank Fusion.
# Build (or incrementally update) the vector index — one-time, per knowledge base
okf vector index
# Inspect index state (chunks, concepts, index format version)
okf vector status
# Full rebuild (after content changes, or when upgrading index format)
okf vector rebuild
# Search semantically (hybrid: semantic + BM25, fused with weighted RRF)
okf search -q "check my notes for errors" -semantic
# Pure semantic, no lexical channel
okf search -q "how do I rebuild the index" -semantic -lexical-weight 0Results are annotated with their source: semantic, lexical, or both. If no index exists, -semantic warns and falls back to lexical search. The MCP server exposes the same capability via okf_semantic_search.
okf eval scores retrieval against a golden query set and can compare strategies side by side:
okf eval -golden pkg/eval/testdata/golden_semantic.json -path docs/knowledge -compareMeasured on this repository's own knowledge base (28 queries, 26 positive, K=5):
| Strategy | Recall@5 | MRR |
|---|---|---|
lexical-substring (pre-0.5.0 behaviour) |
0.0769 | 0.0769 |
bm25-only |
0.8077 | 0.6538 |
semantic-only |
0.9615 | 0.7096 |
hybrid-default |
0.9615 | 0.7256 |
- Chunked indexing: concepts are split on
##–####headings into ≤1024-character chunks (code fences and tables are never split), each carrying aTitle > Sectionbreadcrumb. This matters because MiniLM truncates at 256 tokens: indexing whole concepts dropped 70.6% of this repository's knowledge-base content, so text past the truncation point was unsearchable. - Hybrid retrieval: the semantic channel (HNSW over chunk vectors) and the BM25 channel are fused with weighted RRF (
k=60, equal weights by default). Tune with-lexical-weight;0disables the lexical channel. BM25 tokenizes identifiers into subwords (okf_semantic_search→okf/semantic/search) and CJK text into overlapping bigrams, with no dictionary dependency. - Reproducibility: indexes below 2048 chunks are searched by exact scan rather than HNSW's approximate traversal, because the approximate path does not return every node even when asked for all of them, and which nodes it misses shifts between rebuilds. Combined with a fixed RNG seed and deterministic tie-breaks, this makes results identical across rebuilds — verified by rebuilding this knowledge base repeatedly and confirming the evaluation metrics do not move.
- Index cost (measured, 7 concepts → 97 chunks): chunking increases index size ~20x (14.5 KB → 287 KB) and build time ~6x (128 ms → 800 ms). Both scale with content volume, not concept count.
- Index format is not backward compatible: chunk-level keys differ across index format generations.
okf vector statusreports the format version; loading a pre-v3 (v2) index fails withindex_rebuild_requiredand namesokf vector rebuild(search falls back to lexical meanwhile) rather than silently returning wrong results. The identity-aware v3 keys arev3:id:<okf_id>for stable concepts andv3:legacy:<fingerprint>for legacy concepts; assigning stable IDs viaokf identity ensure --applyalso reportsvector_rebuild_required=true. - Embedded resources: the ONNX Runtime CPU library (per-OS, ~10–15 MB), the pure-tokenizers native library (~5–6 MB), a quantized MiniLM model (~23 MB), and
tokenizer.jsonare embedded into the binary viago:embedand extracted to the user cache directory on first use (checksum-verified). Building for each platform only embeds that platform's resources (scripts/fetch-ort.sh,scripts/fetch-tokenizers.sh, andscripts/fetch-model.shfetch them at build time; the runtime never goes online). - Dynamic loading (transparency): the ONNX Runtime and pure-tokenizers shared libraries are loaded at runtime via
dlopenfrom the extracted cache — the binary is self-contained but not statically linked. Cache location:os.UserCacheDir()/okf/(override withOKF_ORT_DIR). - Large-document lifecycle: document imports over 2000 words additionally persist source-tracked
__cNconcepts with heading context andderived: true. Semantic results are deduplicated by source document and report the hidden count asdup=N; this letsokf sync -pruneremove generated whole/chunk files safely without touching author-owned files. - Limits: MiniLM embeddings are English-centric. Persisted document chunks and BM25's CJK bigrams improve Chinese retrieval, but a purely Chinese query against English content still relies on the semantic channel alone.
Embedderis an interface, leaving room for stronger models (e.g. BGE-M3) or remote APIs later. - Licenses: pure-onnx (MIT), coder/hnsw (CC0-1.0), ONNX Runtime (MIT), MiniLM-L6-v2 model (Apache-2.0).
This release adds optional stable concept identity, a metadata-only Manifest, hierarchical grouped retrieval, and project-scoped AI-agent integration. All additions are additive: legacy concepts without okf_id keep working unchanged, and omitting group-by preserves the existing ungrouped search output exactly.
Concepts may carry an optional okf_id field matching ^okf_[0-9a-f]{32}$ (canonical URI okf://concept/<okf_id>). Concepts without it remain legacy-unstable and are fully valid — nothing about the required OKF v0.2 field set changes. IDs are only added through an explicit migration; there is no silent random assignment.
# Dry-run (default): lists planned additions, prints NO random IDs, leaves files byte-identical,
# and repeats deterministically (byte-identical JSON).
okf identity ensure --json
# Apply: validates the whole plan before writing, atomically replaces each file, and is idempotent
# (a second run reports zero changes).
okf identity ensure --apply
# Resolve a stable ref against the current bundle path (survives renames/moves).
okf identity resolve --ref okf://concept/okf_... --jsonDuplicate or invalid IDs fail closed with duplicate_concept_id / invalid_concept_id before any file or index is touched; a cross-file write failure rolls back already-replaced files. MCP exposes the same resolution as okf_resolve.
Stable concepts are keyed v3:id:<okf_id>; legacy concepts fall back to deterministic v3:legacy:<fingerprint>. A pre-v2 or v2 index is never mixed with v3 lookups: okf vector status reports incompatible, search/status returns index_rebuild_required and names okf vector rebuild. Assigning IDs with okf identity ensure --apply reports vector_rebuild_required=true.
okf tool manifest lists concepts by bounded frontmatter and file metadata only — it never reads Markdown bodies, loads embeddings, or builds/touches the vector index. Multi-megabyte bodies are bounded by the frontmatter bytes plus one 4 KiB read prefetch.
# Default: at most 100 items, offset 0, ordered by normalized path then ID.
okf tool manifest --json
# Pagination + filters (limit 1..500; within a dimension OR, across dimensions AND).
okf tool manifest --offset 100 --limit 50 --types source,note --tags go --jsonEach item carries identity/ref, path, title/description, type, tags, effective status, trust tier, stale data, latest generated/verified timestamp, source count (≤3 source strings) and an estimated_tokens = ceil(file_bytes/4) label. Broken frontmatter omits only that file with a stable warning code (manifest_frontmatter_missing|too_large|invalid) and scanning continues. MCP exposes the identical contract as okf_manifest.
Append -group-by chunk|concept|source|folder to okf search (and -group-by to okf eval) to project the already-fused, scored candidates into groups before final dedupe/TopK shaping. Omitting the flag keeps the existing ungrouped output and scores byte-for-byte unchanged.
# One representative per source (no source monopolization), plus hit/concept/source counts.
okf search -q "retrieval" -group-by source
# Group derived chunks under their parent concept; folder keys are bundle-relative "/", root is ".".
okf search -q "vector index" -group-by conceptThe representative is always the first raw member (its score is unchanged, never re-aggregated into a sum). Folder projection rejects absolute paths and .. escapes, falling back to concept grouping with a warning rather than producing unsafe keys. Any value outside the four groups fails with invalid_group_by (no silent fallback).
okf agent plan|apply|status|remove installs deterministic project-local configuration for Cursor, Claude Code, and Codex without touching user-global settings or storing any credentials.
# Plan is read-only: reports every proposed path/action/redacted hash and writes nothing.
okf agent plan --client cursor --format json
# Apply needs an explicit confirmation in non-interactive mode; it is idempotent (apply twice → zero diff)
# and preserves every unknown/owned-elsewhere config key and comment.
okf agent apply --client cursor --yes
okf agent apply --client cursor --yes # second run: zero diff
okf agent status --client cursor
okf agent remove --client cursor --yesOwnership is marked with the non-secret OKF_MANAGED=agentconfig-v1 token. An existing entry that is malformed, unowned, or has unbalanced markers is reported as conflict and left byte-identical — there is no --force. Cursor uses .cursor/mcp.json + .cursor/rules/okf.md; Claude Code uses .mcp.json + .claude/skills/okf/SKILL.md; Codex uses .codex/config.toml + a managed AGENTS.md block. Use --client all (the default) for all three.
Governance and code references live in each concept's Markdown frontmatter as extension fields (governance, code_refs), stored in Concept.CustomFields — the core Concept struct is unchanged. The pkg/memorymeta package provides typed accessors, normalizers, and validators.
| Level | Meaning |
|---|---|
constraint |
Mandatory guardrail; agent must adhere. |
hold |
Execution freeze; agent SHOULD request user confirmation (advisory warning only; server never blocks writes). |
context |
Informative domain knowledge (default when unspecified). |
Unknown values are treated as context with a warning in non-strict mode, or rejected by okf lint --strict.
code_refs is a list of repo-relative path patterns. Bounds: max 16 patterns, 256 bytes each, 32 path segments, 2 ** operators (each matching at most 8 segments). Absolute paths, .. traversal, NUL, and backslash are rejected.
# Find concepts governing a specific file (lexical match; file need not exist)
okf tool manifest --for-path pkg/mcp/server.go --mode hit
# Filter by governance level
okf tool manifest --governance constraint,hold--stale-refs performs the only filesystem scan (max 50,000 entries) to report code_refs that match no file on disk; symlink escape or unreadable directories return incomplete + warnings rather than silently empty.
okf tool manifest --mode summary # okf_id, title, type, governance, ≤80-char description
okf tool manifest --mode hit # summary + tags, code_refs, status, stale_after
okf tool manifest --mode full # all metadata (default, backward compatible)
okf tool manifest --max-tokens 4000 # token budget: item bytes/4 (Go encoding/json), no envelopeWhen --max-tokens is set, the pipeline is filter → sort → offset → limit → budget. Results include next_offset, omitted_count (budget_omitted vs total_remaining), and truncated. A budget smaller than the first eligible item returns budget_too_small with min_required_tokens.
okf tool query -q "redis cache invalidation" --memory-check
okf tool query -q "..." --memory-check --dup-threshold 0.25--memory-check returns a dedicated MemoryCheckResult (no_similar or possible_duplicate with top-3 candidates and Jaccard scores), skipping normal query ranking. It builds a BM25 index over at most 1,000 durable concepts (note/event/feedback by default; --type restricts to one type), takes top-10, then re-ranks by deterministic Unicode token Jaccard. It is read-only — no writes, no blocking.
# Read full body of specific concepts by stable ID (query OR refs, at least one)
okf tool context --refs okf_abc123,okf_def456 --budget-tokens 2000CLI flags use hyphens (--for-path, --max-tokens, --stale-refs, --memory-check, --dup-threshold, --refs). MCP/JSON fields use underscores (for_path, max_tokens, stale_refs, memory_check, dup_threshold, refs).
- Knowledge base index — module overview
- CLI reference
- Lint rules
- MCP server
- Durable knowledge capture
- v0.2 example — income statement
.
├── cmd/okf/ # CLI entry point
│ └── main.go # Main application
├── pkg/
│ ├── okf/ # Core types and public API
│ │ ├── types.go # Concept, KnowledgeBundle definitions
│ │ ├── api.go # LoadBundle, SaveBundle
│ │ ├── errors.go # Error types
│ │ ├── helpers.go # Helper functions
│ │ └── meta/ # Version information
│ ├── parser/ # Markdown + YAML parser
│ │ └── parser.go
│ ├── query/ # Query engine
│ │ └── query.go
│ ├── lint/ # Specification checker
│ │ └── lint.go
│ ├── git/ # Git integration
│ │ ├── git.go # Git operations
│ │ └── generator.go # Knowledge base generation
│ ├── convert/ # Pure-Go document conversion (PDF/DOCX/XLSX/PPTX/HTML/CSV/TXT → Markdown)
│ ├── mcp/ # MCP server (status/init/refresh/query/context + durable capture)
│ └── tool/ # Durable note/event/feedback capture tools
├── go.mod
├── README.md # English version (default)
└── README.zh-CN.md # Chinese version
| Module | Path | Purpose |
|---|---|---|
| okf | pkg/okf/ | Core type definitions (Concept, KnowledgeBundle) and public API |
| parser | pkg/parser/ | Markdown + YAML frontmatter parsing and serialization |
| query | pkg/query/ | Advanced query builder and matching engine |
| lint | pkg/lint/ | OKF specification compliance checking (16 rules) |
| git | pkg/git/ | Git repository scanning, code analysis, knowledge base generation |
| convert | pkg/convert/ | Pure-Go document import (PDF/DOCX/XLSX/PPTX/HTML/CSV/TXT/DOC → Markdown) |
| mcp | pkg/mcp/ | MCP server for AI agent integration |
| tool | pkg/tool/ | Durable note/event/feedback capture |
---
type: table
title: users
description: User accounts table
resource: bigquery.project.dataset.users
tags:
- production
- pii
timestamp: "2024-01-15T10:30:00Z"
---
## Users Table
Stores all user account information.import (
okf "github.com/superops-team/okf/pkg/okf"
"github.com/superops-team/okf/pkg/git"
"github.com/superops-team/okf/pkg/lint"
)
// Load knowledge base
bundle, err := okf.LoadBundle(".okf/knowledge", nil)
// Search concepts
results := bundle.Search("database")
// Lint check
result := lint.LintBundle(concepts, lint.DefaultConfig())
// Generate from Git
bundle, err := git.GenerateBundle(cfg, false)| Code | Severity | Description |
|---|---|---|
| OKF001 | ERROR | type field is required and must not be empty |
| OKF002 | WARNING | title is recommended but missing (derived from filename in v0.2) |
| OKF003 | WARNING | description is too short |
| OKF004 | INFO | type uses mixed case (valid for spec-defined types such as Attested Computation) |
| OKF005 | WARNING | generated.at is recommended but missing, or not a valid ISO 8601 timestamp |
| OKF006 | WARNING | tags contain uppercase or spaces |
| OKF007 | WARNING | content body is empty |
| OKF009 | WARNING | content lines are too long |
| OKF010 | WARNING | duplicate tags found |
| OKF011 | WARNING | required tag is missing |
| OKF012 | WARNING | sources is recommended but missing |
| OKF013 | WARNING | duplicate title across concepts |
| OKF014 | ERROR | Attested Computation requires runtime field |
| OKF015 | WARNING | stale_after is not a valid YYYY-MM-DD date |
| OKF016 | INFO | legacy timestamp detected; consider migrating to generated.at |
| OKF017 | INFO | verified is recommended to elevate the trust tier |
# Build
go build ./...
# Build CLI
go build -o okf ./cmd/okf/
# Run all tests
go test ./...
# Run benchmarks
go test -bench=. -benchmem ./...okf ships a reproducible IR (information-retrieval) quality benchmark that quantifies search quality using canonical metrics.
| Metric | Definition |
|---|---|
| Recall@K | Fraction of expected relevant docs found in top-K results |
| Precision@K | Fraction of top-K results that are relevant |
| MRR | Mean Reciprocal Rank — 1/rank of the first relevant result |
| NDCG@K | Normalized Discounted Cumulative Gain (binary relevance) |
tools/eval.shThis runs 20 golden queries (18 positive, 2 negative) across all 7 document formats and prints per-case and aggregate scores.
| Metric | All cases | Positive only |
|---|---|---|
| Recall@5 | 1.0000 | 1.0000 |
| Precision@5 | 0.9000 | 1.0000 |
| MRR | 0.9000 | 1.0000 |
| NDCG@5 | 1.0000 | 1.0000 |
All 18 positive queries return the correct top-1; both negative queries
return zero results. The golden set lives in
pkg/eval/testdata/golden_queries.json and metric implementations in
pkg/eval/.
This project implements the OKF v0.2 specification with full backward compatibility for v0.1.
- Provenance —
sourcesfield with material references, usage counts, and credibility signals - Trust —
generated(by/at) andverified(list of verification events) fields with trust tier derivation (unverified → machine-confirmed → human-reviewed) - Lifecycle —
status(stable/draft/deprecated) andstale_after(YYYY-MM-DD) fields - Attested Computation — new concept type with
runtime,parameters,computation,executor, andattesterfields - Reserved filenames —
index.md(directory listing) andlog.md(update history) - Only
typeis required —titleis now optional and derived from filename if missing
- v0.1
timestampfield is automatically mapped togenerated.at - v0.1 body
# Citationssection is automatically extracted tosources - Legacy
generated: true(boolean) is preserved for backward compatibility - All v0.1 concepts parse without errors in v0.2 mode
See examples/v0.2/income-statement/ for the complete Appendix A income statement example from the spec. The v0.2 core types document covers the full field reference.
Contributions are welcome! The project follows a strict SDD → TDD workflow:
- SDD — write a change proposal under
openspec/changes/<change-id>/(proposal.md/design.md/spec.md/tasks.md) - TDD — write tests first (red), then implement (green), then refactor
- Consistency — land a
conformance.mdmapping spec ↔ implementation ↔ tests - Gate — every change must pass
tools/gauntlet.sh: build, vet, gofmt, staticcheck, tests with-race, coverage ≥ 60%, shuffle, and mutation testing
See AGENTS.md for the full development guide.
Apache License 2.0. See the LICENSE file for the full license text.