simon824 opened a new issue, #376:
URL: https://github.com/apache/hugegraph-ai/issues/376

   ### Search before asking
   
   - [x] I had searched in the 
[feature](https://github.com/apache/hugegraph-ai/issues?q=is%3Aissue+label%3A%22Feature%22)
 and found no similar feature requirement.
   
   
   ### Feature Description (功能描述)
   
   We've built an open-source **operational ontology platform** and would like 
to contribute it to `hugegraph-ai`. It fills the layer between raw data and the 
existing AI features: a governed model of business objects, links, actions and 
permissions that GraphRAG, agents and applications can share.
   
   **About the name**
   
   `KINA` is an acronym for **K**nowledge **I**n **A**ction: knowledge only 
creates value when it can be acted upon. The name mirrors the platform's two 
halves — the ontology (objects / links, the "knowledge") and the action runtime 
(actions / functions / policies, the "action") — closed by the self-improvement 
loop, where action telemetry feeds back to refine the knowledge itself. 
   
   **What it does**
   
   - Ontology as code: objects / links / actions / functions / policies 
declared in YAML, reviewed via PR, compiled into table schemas and a 
**HugeGraph graph projection** (derived, rebuildable; degrades to SQL-only 
without a HugeGraph endpoint)
   - Action runtime with Cedar-style authorization (deny-by-default), markings, 
audit, idempotency
   - Agent surface: first-class MCP server + LLM agent engine; agents share the 
same policy surface as humans, writes require human approval
   - Governed self-improvement: telemetry → LLM-proposed DSL diffs → 
deterministic eval suites → tiered release (T0 auto-merge … T3 human-only)
   
   **Status**: v0.3, ~8.6k lines of Python + React console; 456 backend / 241 
frontend tests green; Apache-2.0 headers in place. Docs are mostly zh-CN — 
we'll translate to English.
   
   **Known gaps — community partners are welcome to co-build**
   
   1. **Self-evolution in real scenarios**: validate the RSI loop on real 
domain business scenarios, keep tuning it, and make self-evolution smarter
   2. **Third-party integrations**: support more third-party components (graph 
engines, LLMs, storage backends, BI/ERP connectors) to improve the system's 
extensibility and universality
   3. **Ontology definition**: make modeling more usable and flexible
   
   Contributions in any of these directions are very welcome — we're excited to 
build this together with the community.
   
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to