evo-ak 0.1.0__tar.gz

evo_ak-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.
+

evo_ak-0.1.0/PKG-INFO

@@ -0,0 +1,163 @@
+Metadata-Version: 2.4
+Name: evo-ak
+Version: 0.1.0
+Summary: Shared tooling for agent harnesses: harness schema, multi-source knowledge graph, Claude Code plugins
+Author: maycuatroi
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/maycuatroi1/evo-agents
+Keywords: agents,harness,knowledge-graph,mcp,claude-code
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML>=6.0
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Requires-Dist: ruff>=0.6; extra == "test"
+Provides-Extra: graphify
+Requires-Dist: graphifyy==0.9.73; extra == "graphify"
+Dynamic: license-file
+
+# evo-agents
+
+Shared tooling for agent harnesses: a cluster of repos plus the manifest, plans and documents that
+tell a coding agent how the cluster fits together.
+
+The first piece is a multi-source knowledge graph. Connectors read git repos, the harness itself,
+wikis and project CLIs, speak one JSON Lines protocol (`kg/1`), and feed an append-only log per
+project. A deterministic pipeline turns that log into a SQLite graph that agents query over MCP.
+Every node and edge carries provenance and a sensitivity label, and a session only sees what its
+clearance allows.
+
+Status: early prototype. Interfaces will change.
+
+## Install
+
+```sh
+uv tool install evo-ak               # or: pip install evo-ak (PyPI name; the command is evo-agents)
+uv tool install git+https://github.com/maycuatroi1/evo-agents   # unreleased main
+# or, from a checkout: python -m pip install -e '.[test]'
+```
+
+The core needs Python 3.10+ and PyYAML; nothing else.
+
+## Quick start
+
+A harness opts in with a `knowledge.yaml` next to its `harness.yaml`:
+
+```yaml
+version: 1
+project: demo
+policy:
+  levels: [public, internal, customer, secret]
+  sinks:
+    - id: claude-code@anthropic
+      kind: agent-session
+      clearance: {level: internal}
+sources:
+  - id: harness            # plans, contracts, bindings, docs of the harness itself
+    connector: harness
+    label: {level: internal, integrity: U}
+  - id: app                # a repo declared in harness.yaml
+    connector: git
+    repo: app
+    refresh: 1h            # due for kg sync --due once an hour
+    label: {level: internal, integrity: U}
+  - id: wiki               # any command that speaks kg/1
+    connector: exec
+    command: [my-cli, kg-connector, wiki]
+    credentials: [{key: my.wiki.token, env: WIKI_TOKEN}]
+    label: {level: customer, integrity: U}
+identifiers:
+  - kind: UseCase
+    pattern: '\bKB-\d{2}\b'
+```
+
+A markdown file whose frontmatter `id:` matches an identifier pattern is where that code is defined;
+a copy says `derived_from:` in its frontmatter, and `kg status` lists codes defined in more than one place.
+
+Then, from the harness:
+
+```sh
+evo-agents harness validate          # schema and reference checks for every harness file
+evo-agents kg sync --build           # run connectors, build the graph
+evo-agents kg status                 # freshness, coverage and held deletions per source
+evo-agents kg build --verify         # rebuild from scratch and compare hashes
+evo-agents kg query kg_search "KB-01"
+evo-agents kg query kg_impact --arg 'paths=["app:src/search.py"]'
+```
+
+Corpus and graph live in `~/.evo/kg/<project>/` (override with `EVO_KG_HOME`), never in a repo. Every
+source sync and every build appends one line to `audit.jsonl` there: ids, times, counts and versions,
+never item content.
+
+To keep graphs fresh, give sources a `refresh` interval (`30m`, `6h`, `1d`). `kg sync --due` runs only
+the sources whose interval has passed since their last ok run; `--all` does that for every project that
+has synced on this machine. On macOS, `kg schedule install` loads a LaunchAgent that runs
+`kg sync --due --all --build` every hour (`kg schedule print` shows the plist, `kg schedule uninstall`
+removes it; output goes to `~/.evo/kg/schedule.log`).
+
+## Using it from Claude Code
+
+```sh
+claude plugin marketplace add https://github.com/maycuatroi1/evo-agents
+claude plugin install evo-kg@evo-agents
+```
+
+The plugin registers the MCP server `evo-kg`, a `using-project-graph` skill, and three hooks. The
+server binds to the project of the session directory; pass `--project` in `.mcp.json` to pin one, or
+run `evo-agents kg bind --project NAME DIR` once to tie a directory and everything below it to a project
+(`kg bind --list` and `kg bind --remove DIR` manage those bindings).
+
+| Tool | Use |
+|---|---|
+| `kg_search` | find ids by name, code, path or words |
+| `kg_context` | connected subgraph around a question or ids, within a token budget |
+| `kg_node` | one node: properties, evidence, edges |
+| `kg_path` | shortest path between two ids, or the trace chains from one (requirement, step, code, test) |
+| `kg_impact` | what depends on ids, `repo:path` files or a unified diff, before you change them |
+| `kg_status` | bound project, clearance, snapshot age, coverage per source, session label |
+| `kg_more` | continue a truncated result |
+
+Hooks:
+
+- SessionStart prints a short note: the bound project and the snapshot age.
+- PostToolUse, after every evo-kg call, joins the labels of what the result revealed into a session
+  label under `~/.evo/kg/sessions/`. It only rises; `kg_status` shows it.
+- PreToolUse, before Grep, Glob, or `rg` or `grep` in Bash, may add a note with the ids of graph
+  nodes named like the search. It never allows or blocks the call. Set `EVO_KG_GREP_HINTS=0` to turn it
+  off.
+
+The plugin needs [uv](https://docs.astral.sh/uv/) on `PATH` and pins the release it runs: the server
+starts with `uvx --from evo-ak==0.1.0 evo-agents`, which downloads and caches that version on first start. The hooks
+run `uvx --offline --from evo-ak==0.1.0 evo-agents`, so they never wait on the network; they stay silent when `uvx`
+is missing or until the server has cached the package.
+
+## Writing a connector
+
+A connector is a generator in process or any executable. It writes JSON objects, one per line:
+`hello` first, then `item`, `tombstone`, `listing`, `state`, `error`, `log`, and `closed` last.
+Item IDs are `<source>:<kind>:<native key>`; every item carries a revision and a content hash over
+canonical JSON. Deletions are only inferred from a scoped `listing` that ends with
+`complete: true`, so a connector that dies half-way never deletes anything.
+
+```sh
+evo-agents kg connector test -- my-cli kg-connector wiki --fixture tests/fixtures/wiki
+```
+
+checks protocol, determinism, replay and permutation, truncated listings, golden output and labels.
+
+## Layout
+
+```
+evo_agents/
+  harness/    schema and loader for harness.yaml, knowledge.yaml, contracts.yaml, plans
+  kg/         protocol, connectors, corpus, pipeline, store, policy, MCP server
+plugins/      Claude Code marketplace (plugin evo-kg)
+```
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

evo_ak-0.1.0/README.md

@@ -0,0 +1,141 @@
+# evo-agents
+
+Shared tooling for agent harnesses: a cluster of repos plus the manifest, plans and documents that
+tell a coding agent how the cluster fits together.
+
+The first piece is a multi-source knowledge graph. Connectors read git repos, the harness itself,
+wikis and project CLIs, speak one JSON Lines protocol (`kg/1`), and feed an append-only log per
+project. A deterministic pipeline turns that log into a SQLite graph that agents query over MCP.
+Every node and edge carries provenance and a sensitivity label, and a session only sees what its
+clearance allows.
+
+Status: early prototype. Interfaces will change.
+
+## Install
+
+```sh
+uv tool install evo-ak               # or: pip install evo-ak (PyPI name; the command is evo-agents)
+uv tool install git+https://github.com/maycuatroi1/evo-agents   # unreleased main
+# or, from a checkout: python -m pip install -e '.[test]'
+```
+
+The core needs Python 3.10+ and PyYAML; nothing else.
+
+## Quick start
+
+A harness opts in with a `knowledge.yaml` next to its `harness.yaml`:
+
+```yaml
+version: 1
+project: demo
+policy:
+  levels: [public, internal, customer, secret]
+  sinks:
+    - id: claude-code@anthropic
+      kind: agent-session
+      clearance: {level: internal}
+sources:
+  - id: harness            # plans, contracts, bindings, docs of the harness itself
+    connector: harness
+    label: {level: internal, integrity: U}
+  - id: app                # a repo declared in harness.yaml
+    connector: git
+    repo: app
+    refresh: 1h            # due for kg sync --due once an hour
+    label: {level: internal, integrity: U}
+  - id: wiki               # any command that speaks kg/1
+    connector: exec
+    command: [my-cli, kg-connector, wiki]
+    credentials: [{key: my.wiki.token, env: WIKI_TOKEN}]
+    label: {level: customer, integrity: U}
+identifiers:
+  - kind: UseCase
+    pattern: '\bKB-\d{2}\b'
+```
+
+A markdown file whose frontmatter `id:` matches an identifier pattern is where that code is defined;
+a copy says `derived_from:` in its frontmatter, and `kg status` lists codes defined in more than one place.
+
+Then, from the harness:
+
+```sh
+evo-agents harness validate          # schema and reference checks for every harness file
+evo-agents kg sync --build           # run connectors, build the graph
+evo-agents kg status                 # freshness, coverage and held deletions per source
+evo-agents kg build --verify         # rebuild from scratch and compare hashes
+evo-agents kg query kg_search "KB-01"
+evo-agents kg query kg_impact --arg 'paths=["app:src/search.py"]'
+```
+
+Corpus and graph live in `~/.evo/kg/<project>/` (override with `EVO_KG_HOME`), never in a repo. Every
+source sync and every build appends one line to `audit.jsonl` there: ids, times, counts and versions,
+never item content.
+
+To keep graphs fresh, give sources a `refresh` interval (`30m`, `6h`, `1d`). `kg sync --due` runs only
+the sources whose interval has passed since their last ok run; `--all` does that for every project that
+has synced on this machine. On macOS, `kg schedule install` loads a LaunchAgent that runs
+`kg sync --due --all --build` every hour (`kg schedule print` shows the plist, `kg schedule uninstall`
+removes it; output goes to `~/.evo/kg/schedule.log`).
+
+## Using it from Claude Code
+
+```sh
+claude plugin marketplace add https://github.com/maycuatroi1/evo-agents
+claude plugin install evo-kg@evo-agents
+```
+
+The plugin registers the MCP server `evo-kg`, a `using-project-graph` skill, and three hooks. The
+server binds to the project of the session directory; pass `--project` in `.mcp.json` to pin one, or
+run `evo-agents kg bind --project NAME DIR` once to tie a directory and everything below it to a project
+(`kg bind --list` and `kg bind --remove DIR` manage those bindings).
+
+| Tool | Use |
+|---|---|
+| `kg_search` | find ids by name, code, path or words |
+| `kg_context` | connected subgraph around a question or ids, within a token budget |
+| `kg_node` | one node: properties, evidence, edges |
+| `kg_path` | shortest path between two ids, or the trace chains from one (requirement, step, code, test) |
+| `kg_impact` | what depends on ids, `repo:path` files or a unified diff, before you change them |
+| `kg_status` | bound project, clearance, snapshot age, coverage per source, session label |
+| `kg_more` | continue a truncated result |
+
+Hooks:
+
+- SessionStart prints a short note: the bound project and the snapshot age.
+- PostToolUse, after every evo-kg call, joins the labels of what the result revealed into a session
+  label under `~/.evo/kg/sessions/`. It only rises; `kg_status` shows it.
+- PreToolUse, before Grep, Glob, or `rg` or `grep` in Bash, may add a note with the ids of graph
+  nodes named like the search. It never allows or blocks the call. Set `EVO_KG_GREP_HINTS=0` to turn it
+  off.
+
+The plugin needs [uv](https://docs.astral.sh/uv/) on `PATH` and pins the release it runs: the server
+starts with `uvx --from evo-ak==0.1.0 evo-agents`, which downloads and caches that version on first start. The hooks
+run `uvx --offline --from evo-ak==0.1.0 evo-agents`, so they never wait on the network; they stay silent when `uvx`
+is missing or until the server has cached the package.
+
+## Writing a connector
+
+A connector is a generator in process or any executable. It writes JSON objects, one per line:
+`hello` first, then `item`, `tombstone`, `listing`, `state`, `error`, `log`, and `closed` last.
+Item IDs are `<source>:<kind>:<native key>`; every item carries a revision and a content hash over
+canonical JSON. Deletions are only inferred from a scoped `listing` that ends with
+`complete: true`, so a connector that dies half-way never deletes anything.
+
+```sh
+evo-agents kg connector test -- my-cli kg-connector wiki --fixture tests/fixtures/wiki
+```
+
+checks protocol, determinism, replay and permutation, truncated listings, golden output and labels.
+
+## Layout
+
+```
+evo_agents/
+  harness/    schema and loader for harness.yaml, knowledge.yaml, contracts.yaml, plans
+  kg/         protocol, connectors, corpus, pipeline, store, policy, MCP server
+plugins/      Claude Code marketplace (plugin evo-kg)
+```
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

evo_ak-0.1.0/evo_agents/__init__.py

@@ -0,0 +1,3 @@
+"""Shared tooling for agent harnesses."""
+
+__version__ = "0.1.0"

evo_ak-0.1.0/evo_agents/__main__.py

@@ -0,0 +1,3 @@
+from evo_agents.cli import main
+
+raise SystemExit(main())

evo_ak-0.1.0/evo_agents/cli.py

@@ -0,0 +1,69 @@
+"""Command line entry point: ``evo-agents``."""
+
+from __future__ import annotations
+
+import argparse
+import json
+import sys
+from pathlib import Path
+
+from evo_agents import __version__
+from evo_agents.harness import validate_harness
+from evo_agents.schema import errors
+
+
+def _harness_validate(args) -> int:
+    targets = args.paths or [str(Path.cwd())]
+    reports = []
+    for target in targets:
+        reports.extend(validate_harness(target))
+    failed = [r for r in reports if not r.ok]
+    if args.json:
+        print(json.dumps({"ok": not failed, "files": [r.to_json() for r in reports]}, ensure_ascii=False, indent=2))
+        return 1 if failed else 0
+    for report in reports:
+        errs = errors(report.issues)
+        warns = [i for i in report.issues if i.severity == "warning"]
+        mark = "OK  " if report.ok else "FAIL"
+        print(f"{mark} {report.kind:<9} {report.path}  ({len(errs)} error(s), {len(warns)} warning(s))")
+        shown = report.issues if args.verbose else errs + warns[:5]
+        for issue in shown:
+            print(f"       {issue}")
+        if not args.verbose and len(warns) > 5:
+            print(f"       ... {len(warns) - 5} more warning(s); use -v to see all")
+    print(f"{len(reports)} file(s), {len(failed)} with errors")
+    return 1 if failed else 0
+
+
+def build_parser() -> argparse.ArgumentParser:
+    parser = argparse.ArgumentParser(prog="evo-agents", description="Shared tooling for agent harnesses.")
+    parser.add_argument("--version", action="version", version=f"evo-agents {__version__}")
+    sub = parser.add_subparsers(dest="group", required=True)
+
+    harness = sub.add_parser("harness", help="read and validate harness manifests")
+    hsub = harness.add_subparsers(dest="command", required=True)
+    validate = hsub.add_parser("validate", help="validate harness.yaml, contracts.yaml, knowledge.yaml and plans")
+    validate.add_argument("paths", nargs="*", help="harness roots (default: the one containing the cwd)")
+    validate.add_argument("--json", action="store_true", help="machine-readable output")
+    validate.add_argument("-v", "--verbose", action="store_true", help="show every warning")
+    validate.set_defaults(func=_harness_validate)
+
+    from evo_agents.kg.cli import register as register_kg
+
+    register_kg(sub)
+    return parser
+
+
+def main(argv: list[str] | None = None) -> int:
+    parser = build_parser()
+    args = parser.parse_args(argv)
+    try:
+        return int(args.func(args) or 0)
+    except KeyboardInterrupt:
+        return 130
+    except BrokenPipeError:
+        return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())