Skeptical or not, the notation itself is coming... a CHAIN! with a TEXT! in the first slot, and a BLANK! in the second.
If JSON loading makes maps instead of bindable objects, we could pick the fields.
deserialized: load-json %whatever.json
value: deserialized."some spaced field"
save-json %output.json compose/deep ["another spaced field": {x: (value), y: 10}]
I'm reticent (e.g. completely unwilling) to allow spaced terms to be bindable in the language. But in a dialect --like a JSON serialization dialect--do what you need to. This can make bridging the gap easier.
If you want to suggest lookup and execution in your dialect...you'd just have to put a terminal dot on it to fetch it, a leading slash on it to run it:
"just a string"
/"some function"
"some value".
But this means you'd be creating mutable series instances, copying that string everywhere, unless strings were immutable and interned. The evaluator isn't going to go that direction.