Thoughts on this? I'm currently using it for duckdb-sql src blocks but got the idea of making it into an expandable registry for org source blocks

name: org-babble
description: programatic access to babel src blocks through elisp

The idea is to:
- Import named source blocks from org files into a registry either by name or the entire file
- Execute blocks programmatically with parameters from Elisp
- Generate Elisp functions automatically from blocks
- Semi-literate programming (disle -> define src blocks and use elisp to program their deployment.

It started by me wanting to have proper syntax highlight in elisp scripts/functions that used some non-elisp code execution, like shell commands or sql execution from commandline, initialy I got it working with sql blocks but then I realized this could be used for any src block, so now I'm working on making it a general framework.

It's currently working with my other package ob-duckdb and can use it like this:

;; 1. Write blocks in org file (queries.org)
;; #+NAME: get-users
;; #+HEADER: :var country="US"
;; #+begin_src duckdb-sql ...

;; 2. Import
(org-babble-import "queries.org")

;; 3. Execute
(org-babble-execute "get-users" :country "JP")

;; Or generate functions
(org-babble-import-from "queries.org" :as :functions :prefix "db-")
(db-get-users :country "JP")