feat: query layer additions (spec 11)#37
Merged
Conversation
…and DSL extensions (spec 11) NodeFilter gains valid_at and metadata_match fields so agents can query facts true at a specific time and filter by metadata key-value pairs. The query DSL now parses valid_at:, expires_before:, and meta.key:value syntax. HybridSearch excludes temporally invalid nodes when valid_at is set on the query. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
NodeFilter::valid_at(DateTime)— filter nodes by temporal validity window (valid_from/valid_until)NodeFilter::with_metadata(key, Value)— filter by metadata key-value pairs with AND semanticsvalid_at:,expires_before:, andmeta.key:valuesyntaxHybridQuery.valid_atexcludes temporally invalid nodes from vector+graph resultscount_nodesfast-path updated to fall back correctly when new filters are setTest plan
valid_atexcludes nodes withvalid_untilin the pastvalid_atexcludes nodes withvalid_fromin the futurevalid_atincludes nodes without temporal fields (evergreen)with_metadatafilters by single key-value pairwith_metadatacalls combine with AND semanticsvalid_at:7d,expires_before:30d,meta.entity_type:companymeta.:value(empty key) rejected with parse error🤖 Generated with Claude Code