Description
The guiding idea here was that we needed to stop trying to discern propositional identity and relevance one proposition at a time, and instead use the power of the models to work in bigger chunks, themes and arguments rather than sentences. To do that, the DoxasticLayer starts from an explicit commitment store, a list of what the system should treat as its priors (the system’s, not the model’s anymore). Code groups that store into families of related commitments, which we called “towers”, and the model is then asked how a given input bears on each tower. This did help alleviate the difficulties of the more granular approach, since questions about the identity of propositions largely fell away, and moving the store outside the model gave us a clear, explicit and inspectable account of the priors belonging to the system. Nevertheless, we ran into a similar problem when it came to reading strength and degree of relevance back out of those judgments; even once we had verdicts on how an input bears on a tower, we had the same trouble judging the bearing and strength of those verdicts against the store in order to update it. A detour into the models’ own probabilities said why. Models read the direction of evidence reliably and its strength badly, and credences are in any case relative to priors, which a model’s weights are not.
The work is paused. It began in September 2026 and its latest entry is from 27 October.
Method
A card of commitments. The store starts from an explicit card of what the system treats as its priors. Incoming text can occasion revising a commitment but never overwrite it, updating is kept separate from responding, and model judgment is channelled into typed, auditable tasks.
Towers. Code groups the store into families of related commitments, called towers, and a model is asked how a given input bears on each tower. The step that decides what an input bears on went through staged versions, ending in a hybrid: a model reads, a trained classifier decides yes-or-no questions, and code assembles the structure.
Rulings and replay. It was built as a supervised build, with workers on separate parts and a growing book of my binding rulings, and a hand-written toy engine kept byte-for-byte as a replay target.
A frozen test. The judge that decides where a new statement attaches was tuned on a development battery, then tested on a held-out battery under a pre-registration frozen first: three new cases in new domains and 216 statements, with keys a blind audit agreed with on 92% of statements before adjudication.