pynmms.rdf.dialogue¶
pynmms.rdf.dialogue
¶
The Elenchus loop over a knowledge graph (PLAN.md step 6).
Allen's Elenchus protocol (AIAA4KE 2026) keeps a dialectical state
<[C : D], T, I>: a position of commitments C and denials D, the
open tensions T, sequents Γ |~ Δ with Γ ⊆ C and Δ ⊆ D that
the opponent claims incoherent, and the material implications I from
tensions the respondent accepted. The respondent proposes a positum and
resolves tensions as they arise, by retracting a commitment or denial, by
refining one, or by contesting the claim; the opponent detects tensions,
keeps the record, and probes.
Here the position is a :class:~pynmms.rdf.position.Position over a
store as background, and the opponent is computed from the regime, the
material entries, and the position's denials, so every tension it raises
is one the base licenses and its refutations are exact. That inverts the
paper's oracle: accepting a computed tension endorses what the base
already says, and contesting one is the move that revises the base, a
proposed exception to the responsible entry. A tension may also be
proposed from outside (:meth:Dialogue.propose_tension), an LLM oracle
or a colleague; accepting it adds the sequent to the base as a material
implication, contesting it drops it.
A positum cannot be withdrawn. The dialogue is in aporia when the
position is out of bounds and no open tension can be resolved: every
tension's own atoms lie in the positum and none has a rescue left.
State persists as JSON (:meth:Dialogue.save); commitments that held are
written to the store by :meth:Dialogue.commit_to_store.
ComputedOpponent
¶
Tensions and probes read off the base: exact, never spurious.
Source code in src/pynmms/rdf/dialogue.py
Dialogue
¶
The dialectical state and the moves of the Elenchus loop.
Source code in src/pynmms/rdf/dialogue.py
155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 | |
accept(tension_id, *, retract=(), refine=None)
¶
Endorse a tension: resolve it by retraction or refinement; it joins I.
An external tension becomes a material implication of the base itself (an exact entry), so it is raised from the base from now on.
Source code in src/pynmms/rdf/dialogue.py
commit_to_store()
¶
contest(tension_id, *, exception=(), apply=True)
¶
Reject a tension. With exception, propose it as a defeater of the responsible entry, and apply it to a ground or pattern entry of the base.
Source code in src/pynmms/rdf/dialogue.py
play(script)
¶
Run a move script with predictions: one move per line, # comments.
Moves: commit <atoms>, deny <atoms>, withdraw <atoms>,
accept N [retract <atoms> | refine <old> => <new>], contest N
[unless <atoms>] (N the 1-based index into the open tensions in
the order raised), propose <atoms> |~ <atoms>; questions
status? ## coherent, tensions? ## 1, probes? ## 2,
commits? <atoms> ## True, precludes? <atoms> ## False.
Source code in src/pynmms/rdf/dialogue.py
propose_tension(gamma, delta, *, source='external')
¶
An opponent outside the base (an oracle, a colleague) proposes a tension.
Source code in src/pynmms/rdf/dialogue.py
status()
¶
coherent, tensions open, or aporia.
Source code in src/pynmms/rdf/dialogue.py
Outcome
dataclass
¶
The result of :meth:Dialogue.play: predictions checked against answers.
Source code in src/pynmms/rdf/dialogue.py
Proposal
dataclass
¶
Tension
dataclass
¶
A sequent Γ |~ Δ over the position's own atoms the opponent claims incoherent.
Source code in src/pynmms/rdf/dialogue.py
Turn
dataclass
¶
One move of the dialogue and what the opponent found afterwards.