transaction.edn

                        
;; I would suggest that we use either 'datopia' or 'datopia.db' as the namespace
;; for the schemas, rather than 'db'.  For users, I suspect 'db' will seem arbitrary 
;; and incongruous (as it does to me, in this context).

#:datopia {:attribute  :datopia.ednt/balance
           :schema     #:db {:cardinality :db.cardinality/one
                             :valueType   :db.type/bigdec}
           :invariant  <inline query graph as map of keyword -> query,
                        or maybe just inline query, initially.  having
                        'def' etc. within a tx is super weird to me.
                        just comments and literals>}

if invariant is a map of kw -> query, we need a convention of what the keyword is for the final query returning true or nil/false.

{:balance-check [:find ...]
 :datopia.db/invariant [:find ?match . :within balance-check :where (= ... )] }

You could also determine it w/ a topological sort of the queries.

True...

In my vector of [$key query] pairs example I was thinking of running all inside (future) and have deref do the ordering as required, last query result in the list being the invariant return value.

Thinking more about it, should not be a map of :keyword to query, but symbol or $symbol to match the :within or :in statement in the query.