OK, lets play with out stolen bjson symbol set

We get for free the set of [string,double,int,int64,binary...] all of which can be enforced upon keywords. So, right away, g machine wants to reserve some words, one word, table. G knws able and attributes of tabkle stare a define graph of those bjson types.
table$sqlite_master // this is has to work,
There has to be a least one built in entry into g internal attributes, and those include sqlite. This also means clients can always go back to ugly TE and get what they want explicitly.

Here is some unbinaried json:

{
"firstName": "John",
"lastName" : "Smith",
"address" :
{
"streetAddress": "21 2nd Street",
"city" : "New York",
"state" : "NY",
"postalCode" : "10021"
}

Looks a lot like TE huh! firstName is predfined as an attribute I think, so it is like this:
firstName$John. Dunno that much about TE yet. The parser can be alterd to handle this easy. Put it straight into nested form, using forward pointers and run it straight into query, against another graph.