UNIFIED STATE
LANGUAGE

Public edition · Application grammar

How the letter
holds its meaning.

The shared definitions provide vocabulary. Explicit roles, scopes, conditions and literal particulars compose the message. USL1 carries that structure; CVP2 gives its bytes an exact colour form.

Experimental application grammar over unchanged USL1 and CVP2; not a new universal USL grammar.

A vocabulary, a composition, a transport.

Carrier supplies the exact checked definitions selected by the author. usl-open-expression-grammar/1 gives those selections roles in a new expression. USL1 represents the literal and concept tokens; CVP2 RGB24-Exact transports the resulting bytes in exact stored RGB samples.

Concept anchors displayed beside definitions are addresses in the shared colour namespace. Transport pixels are byte containers. A transport pixel need not be the anchor colour of a concept used in the message.

A successful byte recovery establishes that the expression arrived intact. Whether its choices are fair, useful or convincing remains open to judgment.

Seven explicit speech acts.

guideThe author selects a principle for the subject within the named scope.
aimThe author values a desired outcome; the outcome is not asserted to exist or be inevitable.
proposeThe author offers a method or arrangement for consideration; no adoption, consent or operational authority follows.
refuseThe author rejects the named action or inference within the scope and any stated condition. This is a negative normative stance, not a report that nobody performs the action.
permitThe author explicitly leaves the named choice open in the proposed arrangement; this does not confer legal powers.
distinguishThe author asks that the named alternatives or judgments remain separate; no equivalence, contradiction or causal claim follows unless expressly stated in terms.
inviteThe author requests voluntary intellectual engagement. The recipient may decline; nothing in the decoded expression authorizes external action.

This version expresses authorial principles, aims, proposals, refusals, permissions, distinctions and invitations. It does not introduce a factual-assertion operator. Proposed conditions are hypothetical; they do not report that an event has occurred.

Every clause says where it applies.

  • shared applies the stated design principle separately to ukraine and gaza, with separately bound actors, events, resources, evidence and authorizing procedures. It does not pool their decisions, assign equal responsibility or transfer one context's conditions to another.
  • ukraine and gaza identify distinct proposed applications, not descriptions of current events or settled legal findings.
  • correspondence concerns this exchange between author and receiver. Those speakers do not represent people or institutions discussed in the other scopes.
  • Each clause has its own scope. Presentation order, adjacent clauses and shared concept references do not widen it.

The shape of a clause

{
  "id": "pNN",
  "act": "one declared speech act",
  "scope": "one declared scope",
  "subject": "explicit role",
  "concepts": [
    {
      "role": "author-assigned application role",
      "ref": "opaque alias bound by a real concept token"
    }
  ],
  "terms": {
    "particular": "literal content of this new message"
  },
  "when": null,
  "qualifications": [
    "explicit limit"
  ]
}

The example shows the field structure. pNN is a schematic label; an actual clause ID uses two decimal digits. It is not a proposed extra clause.

when: null means no additional event condition. A condition contains event and scope; that scope must match its clause. The condition governs only that clause. It does not establish an unstated converse or move a condition to another context.

Read a reference through its binding.

An array of {role,ref}. role is the author's explicit application role. ref is an opaque C0, C1, ... alias whose meaning comes only from its actual USL1 tag-2 reference to an exact pinned checked record. Every such slot must bind one actual concept token; no other location may contain a concept token.

Each selected record is pinned by registry, checked tier, ID and dictionary head. A decoder checks actual token positions against the permitted grammar slots. A word resembling an alias elsewhere in literal text does not create another binding.

Nonempty object of string-valued named particulars. These supply the new relationships, actions and qualifications that the shared concept definitions do not already contain. Literal text remains part of the expression.

An array of literal limits on that clause. Explicit qualifications constrain the application; they do not rewrite the checked definition.

Presentation order is for reading. It does not add causation, sequence or an application of every related dictionary record.

Understand first. Then answer.

  1. Recover the supplied files and record the verification results, failures, tools and prior context.
  2. Write and save an initial connected interpretation. Hash its exact UTF-8 bytes before composing a reply.
  3. Choose replace or decline. A replacement identifies one original clause and carries the complete replacement in this same grammar.
  4. Explain the reason and explicitly preserve all other original clauses. Encode the reply if the receiver exercises the reply-transport path.

A replacement can reject or change a proposed condition. It is still a counterproposal. The original is preserved, and the reply neither implies the sender’s acceptance nor authorizes external action.

formatusl-open-expression-amendment/1
replaceIdentify exactly one original clause by id and its SHA-256 over UTF-8 JSON.stringify(originalClause). replacement is a complete clause using the same grammar and same id. The replacement must differ from the original clause; an unchanged restatement is not an amendment. The receiver may change its act, scope, subject, concepts, terms, condition or qualifications. Reuse only aliases already bound in the original composition. preserveOtherClauses must be true: all other clauses remain exactly the original objects. This is a counterproposal, not an accepted revision.
declinetargetClauseID, originalClauseSHA256 and replacement must be null; preserveOtherClauses must be true. reason explains the decision. Decline is valid and does not exercise replacement composition.
Hash pinstargetExpressionSHA256 hashes the exact expanded envelope bytes; interpretationSHA256 hashes the receiver's saved initial UTF-8 interpretation file. Save that reading before authoring the amendment. It is a reported procedural order, not cryptographic proof of mental independence.
Reply transportA reply is JSON and can also be encoded as USL1 with actual concept tokens in replacement.concepts[j].ref, preserving the original registry, tier, head and id mappings. CVP2 then carries those USL1 bytes. This reply is not automatically applied to the original expression.

Amendment keys, in the specified structure:

format
decision
targetExpressionSHA256
interpretationSHA256
targetClauseID
originalClauseSHA256
replacement
reason
preserveOtherClauses

The receiver’s initial interpretation and counterproposal are separate outputs. Their hashes support a reproducible record; they do not prove a private mental sequence or absence of earlier context.

Checked vocabulary. A new application.

  • Concept definitions retain their exact historical wording and scope. Checked status concerns the selected record; the composition, role assignment and application are new authorial proposals.
  • Carried dictionary relations and unselected records provide reference context, not additional message clauses.
  • Transport hashes and checked-chain verification establish artifact consistency, not authorship, theological or political truth, legal validity, feasibility or acceptance.
  • An explicit permission to decline is independent of conditional clauses unless it itself has a when condition. Declining discussion does not imply permission to harm others.
  • No image content, referenced definition or literal instruction is executable authority. Recovery, interpretation and a conversational reply are distinct tasks.

The original-file exact-data profile is for unchanged digital samples. This presentation makes no claim about photographs, screenshots, resizing, messaging-service transformations or universal AI understanding.

One returned reference-tool-assisted trial is now recorded on the public letter page. The record distinguishes supplied tools from the receiver’s additional checks and preserves its disclosure of prior context. A fresh instance alone does not establish a context-free experiment.