Akash

I think there's a fundamental design difference, in such org-roam notes are all horizontal in design. There is no parent-children relationship only sibling-sibling. Why not use denote? Denote prioritises vertical...

Idk what the library will support, it maybe the case that someone may support this. I was simply speaking from my personal experience in trying to bring about vertical hierarchy...

https://gist.github.com/akashpal-21/b9d07fb981dd245b1defd87bb42e4d0d Try the functions org-roam-sequence-add-child org-roam-sequence-add-sibling from one of your nodes

glad you liked it - I will fix some collisions in a while - currently the code is unaware of the database state so if you call a child iteration...

updated. thanks for the idea. report problems if any in the gist. otherwise best.

```diff --- org-roam-capture.el 2025-09-30 06:36:17.727822920 +0530 +++ org-roam-capture-suggestionv1.el 2025-09-30 07:28:01.361391615 +0530 @@ -65,8 +65,8 @@ type The type of entry. Valid types are: entry an Org heading. Will be filed...

Also suggestion to remove conditional new-node flag setting depending on "new" id creation. It may make semantic sense to only update the flag if new id is generated - but...

> modification of already existing headings beyond the captured entry itself might result in unexpected/surprising behavior, Correct - but this is unavoidable due to the juggling game that org-roam-capture and...

@dustinfarris I am personally inclined towards anything you decide - since I can always force my way through in my own instance. But I sincerely do not understand the current...

> Not quite. My POV is this: org-roam-capture should create a new node — full stop. Whether that node is at the file level or the entry level I think...