design(dn-scoped-context-queries): the question compiles to a scope — onboarding as a database query (draft) - #5
Open
ascalva wants to merge 2 commits into
Open
Conversation
… onboarding as a database query (draft) Synthesizes the 2026-07-28 scoped-context-queries brainstorm (the warrant) plus the jurisdiction capsule (the-distributed-ecosystem 05:07Z) and the epistemic capsules (synchronic-diachronic-dreamer 05:34Z+) into one draft note: - the third onboarding regime: brief (push, retired) → traversal (pull, manual) → query (pull through the system's own retrieval); serves fresh agents and fresh nodes at two trust tiers (NN-11 intact) - the mapping decision: the three bounds are readings of the ratified (Σ,E,T,A) lattice — the authority bound is a Σ-refinement reading (status predicates as refinement elements; castle ⊂ interpreted), NOT a new axis and NOT the lattice's A; jurisdiction is a plan annotation per the enforcement-tier precedent - true-database semantics: deterministic, replayable (answer-drift as an instrument), loud on absence; similarity demoted to one operator; verified seams (core/kernel/stores/sourceset.py, core/ingest/index.py:131, LanceDB + DuckDB stores, palace.py usage line with no query verb) - the authority axis's three duties defined here, once: trust tier, jurisdiction, epistemic status; siblings dn-prediction-castles and dn-distributed-ecosystem cite, never re-define - read_scope as write_scope's dual (view definition; grant-select); the lessons loop as typed exhaust; the palace query + /context wiring deliverable specified, not built Status draft; ratification is the owner's alone.
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
1 participant
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.
Summary
Drafts
docs/design-notes/scoped-context-queries.md(dn-scoped-context-queries, status draft) from the owner's 2026-07-28 brainstorm thread: the third onboarding regime — brief (push, retired) → traversal (pull, manual) → query (pull through the system's own retrieval) — where a natural question compiles to (semantic, temporal, authority) bounds with true-database semantics (deterministic, replayable, loud on absence; similarity demoted to one operator). The load-bearing decision: the authority bound is a Σ-refinement reading of the ratifieddn-capability-scopelattice (status predicates as refinement elements; the castle realm ⊂interpreted), not a new axis and not the lattice's A — which stays holder-authority, pinned at the query-agent signature(READ, 0, NONE); jurisdiction (host-side skeleton vs core-side payload) is an annotation on the compiled plan per the enforcement-tier precedent. The note owns the authority axis's three-duty definition (trust tier / jurisdiction / epistemic status) for the sibling drafts dn-prediction-castles and dn-distributed-ecosystem to cite, defines read_scope as write_scope's dual (a view definition; grant-select), types the lessons loop as exhaust, and SPECIFIES the wiring deliverable (palace queryverb +/contextskill — gated off is fine, absent is not) without building anything. Code seams verified against the branch (core/kernel/stores/sourceset.py,core/ingest/index.py:131,scripts/palace.py:44— noqueryverb). No status flips anywhere; ratification is the owner's alone.Suggested reading order
docs/brainstorms/scoped-context-queries.md— the warrant (owner seeds + capsule)🤖 Generated with Claude Code
https://claude.ai/code/session_01GTYQT2QsWskJW4HmgobyrV