Some random ideas that have popped up are sort of coalescing. Into what, I'm not sure yet. But I fell down a rabbit hole, and this article represents my climb back up. As such, I wouldn't consider this a proper, professional think piece. Just some notes, thoughts and scratchings that I decided to share.

OBTF

@Ellane W has been documenting her experiments with OBTF (One Big Text File) (link). She links off to others who are doing this, and it's something I've seen before and not paid too much attention to. But now I'm seriously considering it.

One thing she's doing that stuck out to me, is following bullet-journaling principals and marking each entry with a single letter followed by a period (e.g. N. for note, T. for task, E. for event...). She chose letters rather than symbols so they could be quickly and easily entered on a phone without too much hunting. Double-tapping space will enter the period for her. Plus it's simple to search write queries for.

Subtext

Entirely separate to that whole thing, I stumbled across Subtext, which bills itself as "markup for note taking". The general idea is to treat each line as its own block with a "sigil" at the start indicating the block's purpose (e.g. # for heading, - for list item, > for quote). It bears a resemblance to markdown, except for that focus on blocks, and a complete lack of formatting (it's an index card, not a page).

It also supports linking, through simple URLs (or surrounding unusual URLS in <>), as well as shorthand "slashlinks" to local files. The intention is for links to be transcluded. This allows things like tables to be included by linking to a CSV file. Or if you really need presentation formatting, you can link to a markdown file or PDF or something.

ELF

Subtext is conceptually similar to Ted Nelson's idea of an ELF (Evolutionary List File). An ELF has three elements:
- Entries: A discrete unit of information designated by the user. Text (long or short), symbols, pictures, anything. I could see these as "files" as they exist today. Remember, Ted was living in the 60s and 70s and imagining the future of computers at this point.
- Lists: An ordered set of entries as designated by the user. An entry can exist in any number of lists. #MOC s?
- Links: A connector, designated by the user, between two entries in different lists. An entry in one list may be linked to only one entry in another list. Of course, entries in lists can be linked to from multiple places
I think of Notion. Every Notion "document" is actually a list of blocks that can be of different types. Blocks can be linked to specifically.
Backlinks are a big thing, too. Seeing everything that links to the entry you're looking at is important. Of course, Ted is all about that transclusion, too. So this is where the "slashlinks" of Subtext come into it. A Subtext file is a list of entries. There is one entry per line - mostly plain-text, with specified "sigils" to indicate different types of meanings, or URLs/slashlinks, which can transclude files as different kinds of entries. As a plain-text file, it can't really block-reference entries in other list files, so it doesn't quite fit the ELF 100%, but it's close.

Putting it all together

Can we use the Subtext and ELF principals in OBTF? Subtext "sigils" are basically just the bullet types Ellaine was using for her bullet-journal-style approach to the OBTF. Also keep in mind that the OBTF isn't the entire knowledge base - it's just an inbox; a staging area; a replacement for your daily notes; an ever-evolving #MOC of your day-to-day life.
It's a highly personal thing. You could make a note in your OBTF, then later refactor it out into its own note file (I would leave the OBTF entry as-is and just link it to the new note). You can quick-capture tasks, which you keep track of through other means (by Dataview queries in Obsidian, or moving them over to a task management app as part of a daily process). It's all up to you.

I think I'm inspired to start my own OBTF experiment. I've been off-and-on looking for a new journaling practice since I fell off that bandwagon many years ago, but nothing has quite stuck. Maybe I could try some form of interstitial journaling, along with capturing tasks, ideas, meeting notes, etc in a OBTF list, using bullet journaling principals for each entry. As I intend to keep this file in Obsidian, I intend to use markdown-compatible "sigils" from Subtext (e.g. # for heading, - for list item, > for quote), as well as others like - [ ] for tasks.
There are some plugins/styles for rendering different kinds of "task statuses", too. I could render - [i] as a lightbulb (💡) for example. Simple to search for and query, as well. A bit cumbersome to type on mobile, but I could put in some work to customize the toolbar in obsidian mobile...

Alternately, I could just keep things like "ideas" as basic text blocks with a hashtag (e.g. #idea) at the end of the line if it's something I'll want to search for later. It might resemble a more free-form journal that way.

As I stated at the start, this was a collection of ideas I needed to braindump and decided to share. So I don't really have a proper conclusion for you.