Rei Chat conversational interface

A conversational demo surface where Core performs the reasoning and a language model articulates the result.

Rei Chat is a conversational demonstration of Core. Core carries state forward, forms and revises structure, and produces a structured result; a separate language model renders that result as prose for the user.

The familiar interface makes the architecture easy to experience without making language the reasoning substrate.

The language boundary

Language in

Human interaction

A question, correction, or goal enters through the conversational boundary

→

Reasoning substrate

Core

The continuing instance revises state when warranted and returns a structured result

→

Language out

Replaceable translator

A selected language model articulates the result as conversational prose

The arrows describe language boundaries, not sequential modules inside Core. The language model receives and articulates a current Core result; it does not own the accumulated state that produced it.

Core-side state changes remain available to later interactions independently of the generated wording. The translator is replaceable and is not required for Core’s machine-readable output.

Responsibility at the boundary

Observable behavior	Primary source
What evidence, constraints, relationships, or hypotheses matter	Core
What persists or changes across use, new evidence, and correction	Core
The selected structured result and confidence	Core
Wording, tone, formatting, and conversational fluency	Language model

Smooth prose does not prove that the underlying state is correct. Awkward prose does not prove that the structured result is wrong. Encoding omissions and prose embellishment belong to the language boundary, so the surfaces have to be evaluated separately.

Language output

For example, an illustrative structured result might look like:

{
  "decision": "hold",
  "confidence": "provisional",
  "support": ["constraint_a", "event_7"],
  "conflict": "event_9"
}

Articulation A

Hold for now. The current constraints support that decision, though one later event remains unresolved.

Articulation B

The provisional action is HOLD. Supporting state is stronger than the conflicting observation.

The structured packet is the same. Wording, emphasis, and omissions can differ. Changing the output model does not make that model the owner of Core’s accumulated state.

Demo scope

Rei Chat made an unfamiliar architecture usable through a familiar interface. It lets people observe:

• continuity across interactions;
• correction and revision of earlier assumptions;
• durable constraints alongside fading weak preferences;
• the separation between Core’s structured result and its language rendering.

Language generation adds latency, tokens, and translation variance that the direct structured path does not require.

Rei Chat is not a clean measurement of Core alone. Visible responses also contain encoding and articulation effects, so rigorous evaluation separates Core-side state and structured output from the generated prose.

Interfaces

Build with the Rei Chat API

Make conversational calls, manage Units, or integrate the Rei Chat SDK.

Explore Adapt-1

Start with machine-readable results when application code should consume Core without a prose step.