From Checker to IoV Invocation

The initial checker was a tool with a protocol trace. The next step was to make it an invocation inside The Internet of Value: a named capability that could be resolved, versioned, governed, and executed through an accountable service.

The canonical trace already existed in the protocol registry:

~WellbecomingProtocol

~~Emotion

~~~Cortisol

The application could not simply call itself ~CortisolChecker without creating a grammar collision. Leading tilde depth represents canonical protocol hierarchy. A one-tilde application would falsely appear to be a Level 1 protocol. The resulting registered-expression grammar uses enclosing delimiters instead:

~Cortisol Checker~

The enclosed name is a resolvable expression. ~~~Cortisol remains the canonical protocol facet. The two forms carry different meanings.

In the current Phase 1 system, Word Wallet Web is the deployed caller. It applies origin, rate, request, and consent boundaries before forwarding the minimum analysis input through short-lived service authentication. The checker performs deterministic analysis and no persistence. The Foundation route provides the public experience. The canonical Spec defines the protocol and registered-expression contracts.

This arrangement changed the meaning of “run the checker.” A visitor is no longer calling an isolated scoring page. They are invoking a versioned expression through an operating service that resolves what it is, where it maps, what policies apply, and which execution service is accountable for the result.

That is the first concrete bridge from a language experiment to The Internet of Value protocol stack.