express, The Human Lane

Syntax

express = "express" "to" party ":" string ;

Semantics

express is the only construct in Osmol that admits free prose. Everything else in the language is typed literals a machine can reason about; here, and only here, a double-quoted string is legal (Lexical Structure).

The spec's example, §4.6:

express to mom: "Saw a fox on the way home and thought of you."

An expression crosses the mesh verbatim, provenance-stamped, and immune to every transform and every attention rule. No membrane rule may coarsen it, no summarizer may compress it, and no classifier may silence it. It may be queued by the receiver's quiet hours, but never summarized or silenced. This is Axiom V: the human lane is verbatim. Two diagnostics guard it structurally: a membrane or attention rule whose selector matches an express is error[O-004], and the transform simply has no grammar to apply.

Every expression carries a mandatory authorship provenance class:

  • human: the default. A person composed these words.
  • assisted: a machine helped; a person directed and owns it.
  • autonomous: unrepresentable. An express authored by an autonomous process is error[O-005]: machines may not counterfeit the human lane. This is not a policy setting; the provenance class has no legal spelling.

Why it exists

A fair objection to a mesh that resolves logistics without human messages is what the Fifty-Year Letter's objections chapter calls the death of texture: if agents write to agents, do humans stop hearing each other? Osmol's answer is architectural, not aspirational. Laws IV and V of the letter split the lanes (machines exchange state, humans exchange meaning), and the system must protect unstructured, inefficient, warm communication on purpose. Efficiency is for machines; presence is for people.

So the human lane is deliberately inefficient by design (Osmosis protocol spec, §9): no summarization, no batching, full fidelity. The stated design objective is that traffic in every other lane falls while traffic in this lane rises in warmth per unit. The fox line above is the canonical specimen: it carries no fact, closes no gap, and answers no deadline. It exists because its exact wording is the point, and the grammar guarantees that the wording survives.

The provenance requirement answers the darker failure mode the letter names: the automation of intimacy. A birthday message ghost-written by a model must not be able to masquerade as a human act. In Osmol, it grammatically cannot.

In v0.1

The reference interpreter delivers expressions first in settle(), before any flow is evaluated: the human lane outranks the pressure engine in the event order itself. Each delivery prints verbatim with its provenance:

  human-lane  maya -> raj  (verbatim, provenance=human): "Saw a fox on the way home and thought of you."

You can see this live in The Dinner Mesh: dinner.osmol contains

express to raj: "Saw a fox on the way home and thought of you."

and its line is the first event of every settlement trace. Note the v0.1 pragmas: quiet hours are stored but not enforced (no wall clock is simulated), and provenance is always human because the interpreter has no autonomous authors to refuse.

The future: authorship as a cryptographic claim

In the full protocol (engineering dissertation, Chapter 5), the provenance label stops being metadata. Every delta is signed over payload, provenance chain, authorship class, and nonce, with keys held in device secure hardware. So "a human wrote this" becomes a cryptographic claim, and to forge it means to forge a signature. O-005 is the compile-time face of that guarantee; the signature is its runtime body.