Does normalisation include the suppression of all unnecessary whitespaces? It does not matter if the underlying storage uses a compact form, not easily readable by a human, given that the wiki editor could as well expand it with proper indendation for easier editing, and recompact it after.

As well, will we be able to insert comments in JSON-like objects, or will there be a way to separate the canonicalized and compacted form of the object separately from its source, to preserve some comments (which which syntax: like HTML/XMS with <!-- ... -->, C/C++/Java/JS with /* ... */ or // ... \n, SQL with -- ... \n, Lua with --[[ ... ]], sh/ksh/bash with # ... \n, Pascal with (* ... *), or others)/
May be that JSON form could be just stored in a cache, while the actual pages could use one of several other languages, the conversion being performed by a "Parser function", a new kind of Function, jsut like there are Renderers; and as there will bne a REPL, it will certainly not use that JSON syntax, but could as well use a Ture-like or Python-like syntax.

In my opinion, canonicalisation of the input can be made with a function as well. And to improve the speed of the function evaluator, you'll need to support a cache of results, so this cache should be pritable as well to store the canonicalized version of objects: there's no requirement for objects to use exclusively the JSON-like format with cryptic keys ands there are certainly better ways to represent it in a much simpler structure (e.g. we don't need many implicit or required keys such as Z1K1)

As well, the JSON data is also fully representable as a list of RDF triples (whose processing at large scale is very efficient and can be easily distributed and parallelized; for RDF, you would just need to create "reference" objects)