Teaching a conversational engine, with the evidence visible

In a recorded local browser example, the user tells Ackren: “Mara is a composer.” The next statement supplies a rule: “Every composer is a person.” Asked “Is Mara a person?”, the prototype replies: “Mara is a person.” Its displayed explanation links the answer to the supplied statement and rule.

The browser record also showed the selected proof, inference checks and word-generation trace. This is synthetic teaching data from a development example. It demonstrates the recorded exchange, not independent conversational competence or a verified fact about a real person.

Sources: Recorded prototype example and development checks

The latest development record describes a non-neural local path that composes replies and explanations from explicit meaning and language records. It supports bounded teaching, inference and correction. The record also describes tentative relational proposals and review of changed interpretations. Those capabilities remain constrained by the implemented language and reasoning rules.

A subsequent targeted repair addressed greeting-prefixed identity questions and remembered names written in lowercase. This is a concrete usability improvement, but a fix for a selected question form is not evidence of unrestricted language coverage.

Sources: Recorded prototype example and development checks

The prototype’s initial structural progress set recorded 46 passing turns out of 47. A broader exposed regression recorded 28 out of 39. These sets differ in construction, scope and exposure; the fractions must not be compared as if they measured an improvement or decline on one benchmark.

The development record leaves relevant follow-up questions, broad-topic conversation and independent release qualification open. Passing engineering checks is valuable evidence about specified behaviour. It does not replace independent human evaluation.

Sources: Recorded prototype example and development checks

Our interest is in whether a person can teach, inspect and correct a system without losing the trail from a statement to a later answer. The example makes that question concrete. The next useful demonstration would include a correction, an ambiguous statement and an unsupported request, with the complete record available for each.

We regard this as a research update with a testable direction. We are not presenting symbolic conversation as a new invention, claiming an advantage over language models, or treating a local candidate as a released service.

Sources: Recorded prototype example and development checks