This feels like something that has been discussed multiple times since I joined this forum in 2019, but right now I’m not sure if this is a feature request, or has otherwise been addressed, but it seems like a valid need still so I’m posting it up now…if this needs to be merged somewhere I will count on the team to handle that!
I wanted to request the ability to simple create a “non-defined” entity that would get queued up for assignment to a db later on. I have come across this need time and again while using Fibery these 6 years, and with the proliferation ongoing of .md file-based tools and more “flow” when creating these days to serve AI better, it occurred to me that maybe this is something that could come to Fibery as well. Basically just the ability to fire up an entity in flow with no need to figure out where it goes while doing that.
Use cases would be if you have a product idea and can’t figure out if it should be a project at first, or a feature, or an formal idea (which might need attributes you haven’t figured out at time of creating the item) say if you have these three types in db’s.
I have also thought about situations when you might want to “enhance” a part of your software (for those tracking development in Fibery) and not really sure if that’s quite on the level of a new feature or not…
Non tech needs might be around tracking service providers, which I do in Fibery - so for example I have various parts of AI tools now proliferating that I’m trying to keep track of, and lately it occurred to me I’d like to track the models of the AI, in addition to the AI providers themselves - this might require a whole new db…but if I’m writing in a Fibery entity in flow and decide I want to represent “Opus 4.7” in Fibery and I don’t have worked out yet where I’m going to handle the versions of Claude - then I’d like to just fire it up as an entity, and come back later to analyze.
This would go hand in hand with an actual db that would deal with these “orphan” entities, call it say the “queue,” and you could come in later and assign these out once you have some time to analyze - or even use AI to group them.
Another reason I am bringing this up is the similar feature that is in the bigger AI-centric tools that are in Fibery’s space (networked thought, graph of info, etc.) like Notion, and Tana which is about to reinvent itself, or standbys like RoamResearch and Obsidian where you just use a hash or other keyboard shortcut to tell the system you want to represent something permanently, and just keep writing away and you can later organize that piece. In fact one way I talk about this is to think like you are “writing in wikipedia,” so anything that is “something” should be represented permanently so you can keep track of how it’s referred to as the knowledge base builds up in Fibery and pick up all kinds of insights for your org moving forward - all the more that we have various AI now to help make sense of this!
Finally, this could help flow in Fibery currently and minimize need for conversions of entity to something else which can sometimes be messy with stuff like losing comments, history, references etc although there are some good improvements around that lately - sorry don’t have the specifics handy but many of you who follow the updates more closely than me will have those memorized.
One response that might seem logical here is to create a “queue” db and just make sure people post to that if they aren’t sure where the “orphan” goes, but I think there is a certain elegance in the other tools that allow you to simple create “something” by typing it and telling the tool of record to “remember I want this permanent” that using an existing db for this need would not really accomplish.
Hopefully this is useful and I look forward to feedback and ideally some insight on how the team thinks about this type of issue - I would for one certainly like to see Fibery continue down the road of continuing to build networked-thought or linked entity features because what we already have really separates Fibery from the other tools already!