Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

OpenDots on FeltDB

Aperta
  • Qualcosa non va?
#83 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
sqlite, typescript
Ambito
backend, databases

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
2.8k
Fork
344
Merge medio
1g 8h
PR unite (30g)
33

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CopilotKit/OpenDots

Tutte le issue di CopilotKit/OpenDots

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.