Update: I am currently working on adding document database features: automatically indexing structural documents by paths, supporting edn, json and markdown values. This feature is only available for Datalog DB, with an additional data type :db.type/idoc , "idoc" means "indexed document". Two new built-in query functions idoc-get to get a value by path, and idoc-match to search documents by path expression.
Sounds cool!
It is now released in 0.10.4, give it a try!
Is it principally a matter of ergonomics - for example, convenience of storing and retrieving ordered lists - or does it also unlock some efficiencies?
It is more of a new capability: automatically indexing structured document by paths, so it unlocks a lot of functionalities. The main benefit of document databases is their flexibility, i.e. no need to define a schema, just drop in your documents, the DB breaks them down and indexes the pieces for you, so you can update/retrieve/search the values easily. No schema migration to worry about.
The implementation of document DB of course requires some new indices, mainly inverted index of path -> doc id.
idoc index complements full text and vector index, to allow one to store and retrieve content in new way.