World's first open-source enterprise world model.
Rust agent-memorybitemporalgraphragknowledge-baseknowledge-graphllmontologypgvectorpostgresqlragrustself-hostedsemantic-searchtemporal-knowledge-graphworld-model
README says what Utopia is for, and a walkthrough runs one path end to end (#928)
WaylandYang6e86bc08ba9a
diff --git a/README.md b/README.mdindex 67551fb2..77f3cfc5 100644--- a/README.md+++ b/README.md@@ -48,6 +48,19 @@ We gave it a somewhat romantic name, **Utopia**. Ptolemy's geocentric model wasWhere existing vector stores and knowledge graphs work to get present knowledge right, one of Utopia's founding aims is to record the whole course of changing understanding. Engineered, that becomes a **bitemporal knowledge graph**. When a decision is reviewed later, the system can produce the full course it took and the grounds it rested on. To make this hold up in practice we have iterated at length against public corpora spanning enterprise records, education, finance, law and research. Temporality is only one facet; for how knowledge is taken in, how the future is reasoned about, and how logic bounds action, see [utopia.bi/philosophy](https://utopia.bi/philosophy).+## Use cases++What Utopia is for, in the shape of the question someone brings. Each is available today unless it says otherwise; each needs a chat model configured, and each leaves the doubtful cases to a person in Review.++| Who and what | Input | Question, and what comes back | What the base adds over search or RAG |+|---|---|---|---|+| **A contract chain.** Legal or procurement, a master agreement amended several times. | The agreement and its amendments, as PDF or Word. | *Which payment terms applied on 15 March 2024, and who were the parties?* The terms in force on that date, the amendment they came from, the sentence. | Each fact carries when it held and where it was said; a later amendment closes the earlier term instead of overwriting it. The [contracts corpus](scripts/bench/corpora/contracts/README.md) is this scenario, with the questions it has to answer. |+| **Who held what, when.** HR, finance or research records that change: handovers, corrections, restatements. | Announcements, minutes, filings, dated as they were written. | *Who led project X in Q2 2023, and what did we believe about it at the time?* The holder for that period, and separately what the base knew then. | Two clocks: when something was true, and when the base learned it. A correction links to what it replaced. The [temporal QA bench](scripts/bench/README.md) measures this. |+| **An agent that reads the base.** Engineering or operations teams with Claude Desktop, Cursor or their own agent. | An existing base; the agent connects over MCP with a token scoped to it. | *Facts about this entity as of a date; the path between two things; what changed last week.* Structured answers with stable identifiers and evidence; anything the agent wants to record goes to a person first. | Reads are typed and dated, not passages; writes are proposals. The [MCP guide](web/src/docs/mcp.md) lists the tools. |+| **Observations from a system.** Robotics, monitoring, security tooling: a system that already knows what it saw and when. | One push per observation, in the extraction contract itself, with the observation's time. New in rc7. | *Where was this object at 08:05, and where is it now?* The value that held at that moment and the observation it rests on. | No model between the system and the graph; a functional attribute closes its earlier value when a later observation arrives. The [walkthrough](docs/walkthrough.md) runs this end to end with `curl`. |++The walkthrough is the shortest way to see the whole path: sample data, ingestion, a question, the answer with its evidence, and what the base does not do.+## FeaturesOne Rust binary and one Postgres. Full-text search is embedded in the binary, vectors go in pgvector, and the job queue is a table: nothing else to run.diff --git a/README.zh-CN.md b/README.zh-CN.mdindex d5537b74..147beb24 100644--- a/README.zh-CN.md+++ b/README.zh-CN.md@@ -48,6 +48,19 @@ https://github.com/user-attachments/assets/aa226443-75de-437e-bd80-88e592ed8457不同于现有向量知识库、知识图谱工作追求当下知识的正确,Utopia 的设计初衷之一是记录完整的认知变化历程。工程上实现为**双时态知识图谱**。在决策复盘时,该系统可以拿到完整的决策过程与依据。为了提升可用性,我们基于公开的企业信息、教育、金融、法律、科研等领域语料库做了大量迭代。时态能力只是其中一面,如何接纳知识、如何推演未来、如何让逻辑约束行动,见 [utopia.bi/philosophy](https://utopia.bi/philosophy)。+## 适用场景++Utopia 能解决什么问题,按人带着来的那个问题来说。除注明外都是现在就能用的;每一条都需要配一个对话模型,拿不准的地方都留给人在审核里定。++| 谁、什么问题 | 输入 | 问什么,得到什么 | 比检索和 RAG 多出来的 |+|---|---|---|---|+| **合同链。** 法务或采购,一份主协议被多次修订。 | 主协议和历次修订,PDF 或 Word。 | *2024 年 3 月 15 日适用的付款条款是什么,当事方是谁?* 那一天生效的条款、它来自哪次修订、原句。 | 每条事实带着它成立的时间和出处;后来的修订关闭前一条,而不是覆盖。[合同语料](scripts/bench/corpora/contracts/README.md) 就是这个场景,附带它必须答对的问题。 |+| **谁在什么时候担任什么。** 人事、财务、科研里会变的记录:交接、更正、重述。 | 公告、纪要、申报文件,按写下的日期。 | *2023 年二季度谁负责 X 项目,当时我们对它的认识是什么?* 那段时间的负责人,以及分开给出的、当时库里知道的内容。 | 两根时间轴:事情何时成立,库何时得知。一次更正链回它替换的那条。[时态问答 bench](scripts/bench/README.md) 量的就是这个。 |+| **读库的智能体。** 用 Claude Desktop、Cursor 或自建 agent 的工程、运维团队。 | 已有的知识库;agent 用限定到这个库的令牌通过 MCP 接入。 | *某实体在某天的事实;两个东西之间的路径;上周变了什么。* 带稳定标识和证据的结构化答案;agent 想写入的东西先交给人。 | 读到的是带类型和日期的事实,不是段落;写入是提议。[MCP 指南](web/src/docs/mcp.md) 列了全部工具。 |+| **来自系统的观测。** 机器人、监控、安全工具:系统自己知道看见了什么、在什么时候。 | 一次观测一次推送,直接用抽取契约,带观测时间。rc7 新增。 | *这个物体 08:05 在哪,现在在哪?* 那一刻成立的值,以及它所依据的那次观测。 | 系统和图之间没有模型;函数型属性在后一次观测到来时关闭前一个值。[走通示例](docs/walkthrough.md) 用 `curl` 把这条路从头跑到尾。 |++走通示例是看完整路径最短的办法:样例数据、摄入、提问、带证据的回答,以及这个库做不到的事。+## 功能系统由 Rust 二进制和 Postgres 服务组成。我们通过 pgvector 和队列表设计减轻了技术栈和服务依赖的负担。