okft 0.1.0__tar.gz

okft-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,21 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: pytest tests/ -q
+      - run: okft lint examples/acme_brain --strict

okft-0.1.0/.gitignore

@@ -0,0 +1,7 @@
+.venv/
+__pycache__/
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+.DS_Store

okft-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

okft-0.1.0/PKG-INFO

@@ -0,0 +1,144 @@
+Metadata-Version: 2.4
+Name: okft
+Version: 0.1.0
+Summary: Lint and serve Open Knowledge Format (OKF) bundles — a validator and MCP server for the OKF v0.1 spec
+Project-URL: Homepage, https://github.com/PoorvaJ-WW/okft
+Project-URL: Specification, https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md
+Author: Poorva
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: knowledge-graph,lint,llm,markdown,mcp,okf,open-knowledge-format
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Text Processing :: Markup :: Markdown
+Requires-Python: >=3.10
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: mcp>=1.2.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Provides-Extra: serve
+Requires-Dist: mcp>=1.2.0; extra == 'serve'
+Description-Content-Type: text/markdown
+
+# okft
+
+**Lint and serve [Open Knowledge Format](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md) (OKF) bundles.**
+
+OKF is Google's open spec for representing organizational knowledge as a
+directory of markdown files with YAML frontmatter — a knowledge graph that
+both humans and AI agents can read natively. `okft` covers the two
+sides of keeping a bundle healthy and useful:
+
+- **`okft lint`** — validate a bundle against the OKF v0.1 spec, plus hygiene
+  checks (broken links, orphaned concepts, malformed timestamps). Wire it
+  into CI so your knowledge bundle can't rot silently.
+- **`okft serve`** — expose a bundle to any MCP-capable AI agent (Claude,
+  Gemini CLI, Cursor, …) as a set of navigation tools: overview, read,
+  search, list. Deterministic graph traversal, no embeddings, no database.
+
+## Install
+
+```sh
+pip install okft          # lint only
+pip install 'okft[serve]' # lint + MCP server
+```
+
+## Lint
+
+```sh
+okft lint path/to/bundle
+```
+
+```text
+analytics/tables/orders.md:1 error E003 frontmatter must include a non-empty `type` field
+analytics/metrics/churn.md:24 warning W001 link target does not resolve in bundle: /analytics/tables/order
+engineering/runbook.md:1 warning W004 concept is never linked from any other document
+
+12 concepts checked: 1 error(s), 2 warning(s)
+```
+
+Exit code is `1` on errors (or on warnings with `--strict`), so it drops
+straight into CI. `--format json` emits machine-readable findings.
+
+### Rules
+
+| Code | Severity | Check |
+|------|----------|-------|
+| E001 | error    | concept file has no YAML frontmatter block |
+| E002 | error    | frontmatter is not parseable YAML |
+| E003 | error    | missing or empty `type` field |
+| E004 | error    | reserved file (`index.md` / `log.md`) has frontmatter |
+| W001 | warning  | link target does not resolve inside the bundle¹ |
+| W002 | warning  | `timestamp` is not ISO 8601 |
+| W003 | warning  | `tags` is not a list of strings |
+| W004 | warning  | orphan concept — nothing links to it (`--no-orphans` to skip) |
+| W005 | warning  | bundle root has no `index.md` |
+| W006 | warning  | `log.md` headings are not ISO 8601 dates |
+| W007 | warning  | concept has no `title` |
+
+¹ The spec requires consumers to *tolerate* broken links, so they are
+warnings, never conformance errors.
+
+Both standard markdown links (`/analytics/tables/customers.md`, relative
+paths) and `[[wiki-style]]` links are resolved.
+
+## Serve to an AI agent
+
+```sh
+okft serve path/to/bundle
+```
+
+Runs an MCP server (stdio) with four tools:
+
+| Tool | Purpose |
+|------|---------|
+| `okf_overview` | root index + every concept grouped by type |
+| `okf_read` | one concept: frontmatter, body, outbound & inbound links |
+| `okf_search` | ranked full-text search with snippets |
+| `okf_list` | filter concepts by `type` and/or `tag` |
+
+Register it with Claude Code:
+
+```sh
+claude mcp add acme-brain -- okft serve /path/to/bundle
+```
+
+or in any MCP client config:
+
+```json
+{
+  "mcpServers": {
+    "acme-brain": { "command": "okft", "args": ["serve", "/path/to/bundle"] }
+  }
+}
+```
+
+## Try it
+
+A small example bundle ships in [`examples/acme_brain`](examples/acme_brain):
+
+```sh
+okft lint examples/acme_brain
+okft serve examples/acme_brain
+```
+
+## CI example (GitHub Actions)
+
+```yaml
+- uses: actions/setup-python@v5
+  with: { python-version: "3.12" }
+- run: pip install okft
+- run: okft lint knowledge/ --strict
+```
+
+## Status
+
+Tracks OKF **v0.1**. The spec is young and so is this tool — issues and PRs
+welcome, especially reports of real-world bundles that lint incorrectly.
+
+## License
+
+Apache-2.0

okft-0.1.0/README.md

@@ -0,0 +1,119 @@
+# okft
+
+**Lint and serve [Open Knowledge Format](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md) (OKF) bundles.**
+
+OKF is Google's open spec for representing organizational knowledge as a
+directory of markdown files with YAML frontmatter — a knowledge graph that
+both humans and AI agents can read natively. `okft` covers the two
+sides of keeping a bundle healthy and useful:
+
+- **`okft lint`** — validate a bundle against the OKF v0.1 spec, plus hygiene
+  checks (broken links, orphaned concepts, malformed timestamps). Wire it
+  into CI so your knowledge bundle can't rot silently.
+- **`okft serve`** — expose a bundle to any MCP-capable AI agent (Claude,
+  Gemini CLI, Cursor, …) as a set of navigation tools: overview, read,
+  search, list. Deterministic graph traversal, no embeddings, no database.
+
+## Install
+
+```sh
+pip install okft          # lint only
+pip install 'okft[serve]' # lint + MCP server
+```
+
+## Lint
+
+```sh
+okft lint path/to/bundle
+```
+
+```text
+analytics/tables/orders.md:1 error E003 frontmatter must include a non-empty `type` field
+analytics/metrics/churn.md:24 warning W001 link target does not resolve in bundle: /analytics/tables/order
+engineering/runbook.md:1 warning W004 concept is never linked from any other document
+
+12 concepts checked: 1 error(s), 2 warning(s)
+```
+
+Exit code is `1` on errors (or on warnings with `--strict`), so it drops
+straight into CI. `--format json` emits machine-readable findings.
+
+### Rules
+
+| Code | Severity | Check |
+|------|----------|-------|
+| E001 | error    | concept file has no YAML frontmatter block |
+| E002 | error    | frontmatter is not parseable YAML |
+| E003 | error    | missing or empty `type` field |
+| E004 | error    | reserved file (`index.md` / `log.md`) has frontmatter |
+| W001 | warning  | link target does not resolve inside the bundle¹ |
+| W002 | warning  | `timestamp` is not ISO 8601 |
+| W003 | warning  | `tags` is not a list of strings |
+| W004 | warning  | orphan concept — nothing links to it (`--no-orphans` to skip) |
+| W005 | warning  | bundle root has no `index.md` |
+| W006 | warning  | `log.md` headings are not ISO 8601 dates |
+| W007 | warning  | concept has no `title` |
+
+¹ The spec requires consumers to *tolerate* broken links, so they are
+warnings, never conformance errors.
+
+Both standard markdown links (`/analytics/tables/customers.md`, relative
+paths) and `[[wiki-style]]` links are resolved.
+
+## Serve to an AI agent
+
+```sh
+okft serve path/to/bundle
+```
+
+Runs an MCP server (stdio) with four tools:
+
+| Tool | Purpose |
+|------|---------|
+| `okf_overview` | root index + every concept grouped by type |
+| `okf_read` | one concept: frontmatter, body, outbound & inbound links |
+| `okf_search` | ranked full-text search with snippets |
+| `okf_list` | filter concepts by `type` and/or `tag` |
+
+Register it with Claude Code:
+
+```sh
+claude mcp add acme-brain -- okft serve /path/to/bundle
+```
+
+or in any MCP client config:
+
+```json
+{
+  "mcpServers": {
+    "acme-brain": { "command": "okft", "args": ["serve", "/path/to/bundle"] }
+  }
+}
+```
+
+## Try it
+
+A small example bundle ships in [`examples/acme_brain`](examples/acme_brain):
+
+```sh
+okft lint examples/acme_brain
+okft serve examples/acme_brain
+```
+
+## CI example (GitHub Actions)
+
+```yaml
+- uses: actions/setup-python@v5
+  with: { python-version: "3.12" }
+- run: pip install okft
+- run: okft lint knowledge/ --strict
+```
+
+## Status
+
+Tracks OKF **v0.1**. The spec is young and so is this tool — issues and PRs
+welcome, especially reports of real-world bundles that lint incorrectly.
+
+## License
+
+Apache-2.0

okft-0.1.0/examples/acme_brain/analytics/index.md

@@ -0,0 +1,12 @@
+# Analytics
+
+Warehouse tables and canonical metric definitions.
+
+## Metrics
+
+- [Weekly Active Users](/analytics/metrics/weekly_active_users.md)
+
+## Tables
+
+- [customers](/analytics/tables/customers.md)
+- [billing](/analytics/tables/billing.md)

okft-0.1.0/examples/acme_brain/analytics/metrics/weekly_active_users.md

@@ -0,0 +1,25 @@
+---
+type: metric
+title: Weekly Active Users (WAU)
+description: Unique users with at least one core API transaction in a rolling 7-day window.
+tags: [growth, executive-dashboard]
+timestamp: 2026-06-15T10:30:00Z
+---
+
+# Weekly Active Users (WAU)
+
+The count of distinct user IDs that triggered at least one core backend API
+transaction within a rolling 7-day window.
+
+## Computation rules
+
+Internal QA and test accounts are excluded:
+
+```sql
+WHERE user_id NOT IN (SELECT user_id FROM staging.internal_testers)
+```
+
+## Related
+
+- [customers](/analytics/tables/customers.md) — primary user dimension
+- [billing](/analytics/tables/billing.md) — correlate usage with subscription state

okft-0.1.0/examples/acme_brain/analytics/tables/billing.md

@@ -0,0 +1,25 @@
+---
+type: table
+title: billing
+description: Subscription invoices, one row per invoice line item.
+resource: bigquery://acme-prod/warehouse/billing
+tags: [warehouse, finance]
+timestamp: 2026-06-01
+---
+
+# billing
+
+Invoice line items. Grain: `invoice_id` + `line_no`.
+
+# Schema
+
+| column      | type      | notes                        |
+|-------------|-----------|------------------------------|
+| invoice_id  | STRING    | primary key (with line_no)   |
+| customer_id | STRING    | FK to [customers](/analytics/tables/customers.md) |
+| amount_inr  | NUMERIC   | paise precision              |
+| period_end  | DATE      | subscription period covered  |
+
+## Related
+
+- [customers](/analytics/tables/customers.md) — join on `customer_id`

okft-0.1.0/examples/acme_brain/analytics/tables/customers.md

@@ -0,0 +1,26 @@
+---
+type: table
+title: customers
+description: One row per customer account; the primary user dimension table.
+resource: bigquery://acme-prod/warehouse/customers
+tags: [warehouse]
+timestamp: 2026-06-01
+---
+
+# customers
+
+One row per customer account. Grain: `customer_id`.
+
+# Schema
+
+| column        | type      | notes                          |
+|---------------|-----------|--------------------------------|
+| customer_id   | STRING    | primary key                    |
+| email         | STRING    | lowercased at ingestion        |
+| plan          | STRING    | free, pro, enterprise          |
+| created_at    | TIMESTAMP | account creation               |
+
+## Related
+
+- [billing](/analytics/tables/billing.md) joins on `customer_id`
+- Used by [Weekly Active Users](/analytics/metrics/weekly_active_users.md)

okft-0.1.0/examples/acme_brain/engineering/index.md

@@ -0,0 +1,5 @@
+# Engineering
+
+Architecture and platform concepts.
+
+- [Service mesh](/engineering/service_mesh.md)

okft-0.1.0/examples/acme_brain/engineering/service_mesh.md

@@ -0,0 +1,18 @@
+---
+type: architecture
+title: Service mesh
+description: Envoy-based mesh handling east-west traffic between backend services.
+tags: [platform]
+timestamp: 2026-07-12
+---
+
+# Service mesh
+
+All east-west traffic between backend services flows through Envoy sidecars.
+mTLS is enforced mesh-wide; plaintext service-to-service calls are rejected.
+
+## Operational notes
+
+- Retries are budgeted per-route; do not add client-side retries on top.
+- API transactions counted by [Weekly Active Users](/analytics/metrics/weekly_active_users.md)
+  are measured at the mesh ingress, not inside individual services.

okft-0.1.0/examples/acme_brain/index.md

@@ -0,0 +1,9 @@
+# Acme Knowledge Bundle
+
+Canonical business definitions and system knowledge for Acme, in
+[Open Knowledge Format](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md).
+
+## Areas
+
+- [Analytics](/analytics/index.md) — metrics and warehouse tables
+- [Engineering](/engineering/index.md) — architecture concepts

okft-0.1.0/examples/acme_brain/log.md

@@ -0,0 +1,13 @@
+# Bundle log
+
+## 2026-07-12
+
+- Added [service mesh](/engineering/service_mesh.md) concept after the Envoy rollout.
+
+## 2026-06-15
+
+- Corrected the WAU exclusion rule in [weekly active users](/analytics/metrics/weekly_active_users.md).
+
+## 2026-06-01
+
+- Initial bundle: analytics tables and core metrics.

okft-0.1.0/pyproject.toml

@@ -0,0 +1,38 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "okft"
+version = "0.1.0"
+description = "Lint and serve Open Knowledge Format (OKF) bundles — a validator and MCP server for the OKF v0.1 spec"
+readme = "README.md"
+license = "Apache-2.0"
+requires-python = ">=3.10"
+authors = [{ name = "Poorva" }]
+keywords = ["okf", "open-knowledge-format", "knowledge-graph", "llm", "mcp", "lint", "markdown"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Topic :: Software Development :: Quality Assurance",
+    "Topic :: Text Processing :: Markup :: Markdown",
+]
+dependencies = [
+    "pyyaml>=6.0",
+]
+
+[project.optional-dependencies]
+serve = ["mcp>=1.2.0"]
+dev = ["pytest>=8.0", "mcp>=1.2.0"]
+
+[project.scripts]
+okft = "okft.cli:main"
+
+[project.urls]
+Homepage = "https://github.com/PoorvaJ-WW/okft"
+Specification = "https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/okft"]