Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

OpenDots on FeltDB

未关闭
  • 哪里不对？
#83 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
sqlite, typescript
领域
backend, databases

调研方向

Start with the linked OpenDotsFeltDB project and the issue’s description of OpenDots’ FeltDB migration and feltdb.flow contract. The issue does not name a requested change, files, or tests, so the first step is to clarify whether any integration work is wanted; it does not define what completion would look like.

由索引模型根据 Issue 内容生成。

描述

Hi — I wanted to introduce myself and share some work I’ve been doing around OpenDots.
https://github.com/rkendel1/OpenDotsFeltDB

I’m building a software platform around the idea that AI agents should be able to build, operate, and manage real software — with a human staying in control of what matters.

One of the foundational pieces I’ve been building is FeltDB:

FeltDB
@feltdb/core on npm

FeltDB is a durable state layer designed around a different model from the traditional “application + database” approach. Instead of treating the database as an external system that applications map their objects into, the application’s state model itself becomes explicit and durable.

You define the application’s state as collections and relationships, FeltDB provides the durable storage and transactional semantics, and the application can treat that state as part of its architecture rather than maintaining a separate persistence model.

The important part is that FeltDB is completely free to use. I’m building it as a foundation that developers can actually adopt, rather than as a hosted database service with a usage meter attached to it.

I think there is a potentially significant architectural idea here: applications can have a formal, inspectable state contract rather than having persistence hidden behind an ORM, SQL schema, migrations, caches, and application-specific storage code. That’s what I mean when I describe FeltDB as a paradigm shift.

I’ve been testing that idea by applying it to OpenDots.

I migrated OpenDots completely off SQLite and onto FeltDB. OpenDots now has a feltdb.flow contract describing its 18 runtime collections and their relationships. The application validates that its runtime state matches that contract and fails closed if they drift apart. State survives process restarts, and SQLite is no longer part of the runtime architecture.

So OpenDots on FeltDB is now a real combination I’m developing, rather than just an experiment.

Around that I’m also building some other infrastructure:

OpenDots is the piece I’m most interested in here: the development control plane where humans manage projects, work, tasks, agents, context, approvals, and results.

Compute is an execution environment I’m building that gives software and agents a consistent computer/runtime they can actually work inside. I realize that overlaps conceptually with the “give an agent a computer” direction, so I’m intentionally not approaching this as a replacement for what OpenDots is doing. I’m more interested in seeing whether these ideas can complement one another.

Chip is the agent runtime — the thing that actually performs work for an agent — and AppPort is the capability protocol I’m using to connect applications, services, and execution environments.

The direction looks roughly like:

Human → OpenDots → execution environment → agent

with FeltDB providing the durable state underneath.

But the pieces are deliberately independent. FeltDB can be used without OpenDots. OpenDots can be used as its own control plane. Compute is its own execution platform. Chip is its own agent runtime.

I’m reaching out because I think the FeltDB/OpenDots combination is particularly interesting, and because I’d rather introduce the work directly than assume the projects have to become one thing.

If this is interesting to you, I’d be happy to show you what I’ve built and talk through where I think the architecture could go.

Thanks
Randy

主要语言
TypeScript
星标
2.8k
派生
344
平均合并
1 天 8 小时
30 天内合并 PR
33

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

CopilotKit/OpenDots 的其他 Issue

查看 CopilotKit/OpenDots 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。