Half-baked: JSON-to-hyperdb mapping

Does there already exist a deterministic 1-to-1 mapping between a JSON document and a key/value store like hyperdb? What I mean is taking one (possibly very large) JSON object and splitting it so each "atom" (integer, boolean, string, etc) ends up as a single Value in the database. Eg:

{
  "a": ["red", "blue"],
  "num": 1234,
}

mapping to something like:

/a[]/[0 -> '"red"'
/a[]/1 -> '"blue"'
/num -> '1234'

This could make for a nice high-level API to hyperdb, where applications just get a JSON-like object (whatever that maps to in their native language, eg nested dicts in python). I'm not proposing the opposite (hyperdb-to-JSON), though that might also be a desirable feature, and is trivial in the case of either a single flat JSON object (with full hyperdb paths as keys) or via nested Objects, one per path.

No files, tests, or entry points are named. Start by reviewing hyperdb's existing API and clarify the deterministic JSON-to-key/value mapping and API scope; done would require an agreed design and implementation criteria.