sniperunder123/okf-knowledge

---

⚠️ Disclaimer — this is vibe‑coded. Built fast, for fun, by one person with an AI pair‑programmer. It’s tested and it works, but it’s an unofficial indie project (not affiliated with Google or Anthropic), shipped as‑is with zero guarantees — use at your own risk. Spot a bug? Issues and PRs welcome. 🌊

TL;DR — Knowledge ends up trapped in wikis, Notion, 3,000‑line READMEs, and people’s heads — where AI agents can’t use it well. OKF represents knowledge as a directory of small Markdown files: each file is one concept (a table, an endpoint, a metric, a runbook…), with a tiny YAML header, linked to other concepts like wiki pages. The result is a navigable knowledge graph that agents read natively, that you version in git, and that no vendor owns. This repo is a /okf command that builds and maintains those bundles for you.

---
type: BigQuery Table          # the only required field
title: Orders
description: One row per completed customer order.
resource: bigquery://acme/sales/orders
tags: [sales, orders]
generated: { by: human:maintainer, at: 2026-05-28T00:00:00Z }   # optional, OKF v0.2
---

# Orders

Part of the [sales dataset](/datasets/sales.md). Feeds [gross revenue](/metrics/gross-revenue.md).

---

🤔 The problem OKF solves

Your organization’s knowledge is real but unusable by machines:

• 📚 Scattered across Confluence, Notion, Google Docs, READMEs, Slack threads, and people’s memory.
• 🔒 Locked in proprietary tools that need accounts, APIs, and scraping to read.
• 🧱 Monolithic — the one big doc that’s either loaded whole (expensive, slow) or ignored.