Conversation
The turn loop's query phase (Manifold.Turn.query/4) is one pass: one generation yields up to three goals, run once, blind to each other's results. That rules out anything needing a result to phrase the next goal (multi-hop lookups, self-correction on an unknown predicate, adaptive stopping). docs/design/multi-pass-query.md proposes a bounded reason -> act -> observe loop confined to the query phase only -- gate/extract/assert/ check and the sealed loop's ordering rules are untouched, the wire protocol needs no version bump, and the control flow is designed as a pure, effects-injected module so the round bookkeeping is unit testable per CLAUDE.md's tiering rule, with an integration test covering the one thing a pure test cannot: a goal that depends on the real binding a prior round got back from swipl. Not implemented yet -- this is the design for review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The turn loop's query phase (Manifold.Turn.query/4) is one pass: one
generation yields up to three goals, run once, blind to each other's
results. That rules out anything needing a result to phrase the next
goal (multi-hop lookups, self-correction on an unknown predicate,
adaptive stopping).
docs/design/multi-pass-query.md proposes a bounded reason -> act ->
observe loop confined to the query phase only -- gate/extract/assert/
check and the sealed loop's ordering rules are untouched, the wire
protocol needs no version bump, and the control flow is designed as a
pure, effects-injected module so the round bookkeeping is unit
testable per CLAUDE.md's tiering rule, with an integration test
covering the one thing a pure test cannot: a goal that depends on the
real binding a prior round got back from swipl.
Not implemented yet -- this is the design for review.