protocol — m0de

m0de is a protocol layer for showing the reading structure of supplied text before the supplied text is treated as fact.

The protocol binds how a supplied text surface is read. It does not establish the supplied text as fact and does not attest the origin of pasted text.

The protocol does not establish supplied text as fact.

It does not attest the origin of pasted text.

It does not turn generated text into authority.

01

source packet

Input is bound as a source packet. Pasted text remains pasted_answer / user_supplied / pasted / not_model_attested.

A label, platform name, instruction slot, or adapter-use claim does not attest source origin.

02

question frame

The question is read before mode closure. If the claim, event, object, referent, source, coordinate frame, or context is missing, that boundary remains visible.

03

reading frame and mode boundary

Modes are local reading contracts. A mode is not domain authority, and a lexicon anchor is reading language, not proof.

04

closure and residue

Closure describes the reading state. Residue remains visible when differentiation, evidence, referent, source, measurement, or scope is missing.

05

word-reading and referent boundary

Words enter as written forms first. The same written form may enter different reading frames; the selected read-as relation is not written into the form and is not proof authority.

06

described-happening boundary

Generated text may be read as describing a happening, state, source, subject, or proof. That read-as relation does not establish what it describes.

07

projection boundary

Reading groups compact the surface. reading_group_hash is auxiliary and replayable; it does not enter canonical ui_binding_surface_hash.

Projection does not change closure or release state.

08

receipt and capsule

Receipts and capsules bind hashes, release state, verifier inputs, and replay surfaces. Reproduction means the reading corridor reproduced.

It does not establish supplied text as fact.

09

external evidence

External replay evidence can show reproduction of replay. It is evidence, not proof authority.

10

proof corridor

Runtime, receipt, capsule, packet, projection evidence, returned evidence, and public wording must preserve the same proof event.

The corridor verifies reproducibility of the reading surface, not answer authority.

same-event boundary

The protocol checks that the source packet, question hash, answer hash, canonical surface hash, projection hashes, closure state, release state, and residue state remain tied to the same reading event where those fields are present.

non-authority boundary

This page is a public protocol boundary surface. It is not a verifier, not receipt or capsule authority, and not a runtime rule. It does not change source lanes, closure, receipts, capsules, replay, release acceptance, canonical surface integrity, projection hash, or proof corridor.

word-reading boundary

Read-as relation and not-written-in boundary.

response-regime boundary

Regime, basis, validity, and stop boundary.

protocol diagnostics

Bounded public diagnostics, not answer verification.

reading corridor, not answer authority