Collections a part of the tree answers from when a request names none
On an organization, team, project or key, the narrowest winning: llmgw ctl kb default, POST /api/v1/kb/defaults, and the console's Knowledge screen. A request's own X-Llmgw-Knowledge overrides it and none turns it off. A default never refuses a request: a collection the caller cannot read is left out, and a failed search answers without passages. Removing a collection takes it out of every default. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
54ba04c52a
commit
0093cc3d45
16 files changed
+552
-12
No files matched your search
@@ -0,0 +1,12 @@
|
||||
-- The collections a part of the tree answers from when a request names
|
||||
-- none (BACKLOG F3): on an organization, team, project or key, the narrowest
|
||||
-- one that has any winning. PostgreSQL only, as the collections are.
|
||||
CREATE TABLE kb_defaults (
|
||||
scope TEXT NOT NULL,
|
||||
scope_id TEXT NOT NULL,
|
||||
-- Collection IDs, comma separated, in the order given.
|
||||
collections TEXT NOT NULL,
|
||||
added_at BIGINT NOT NULL,
|
||||
added_by TEXT NOT NULL DEFAULT '',
|
||||
PRIMARY KEY (scope, scope_id)
|
||||
);
|
||||
Reference in new issue
Block a user