Get card
Download
kb-resolver@1.0.0.yamlClone
npx -y darkprint clone kb-resolver@1.0.0There is no repository and no history behind a card. Download hands you the document as it stands, and Clone fetches the same document by name.
Retrieve the k nearest knowledge-base articles for the routed request and return the best match as Markdown, with its article id and last-reviewed date in the front matter.
used in 1 blueprint
Specification
120 words · handed to the agentBuild a retrieval query out of the routed request on query, its label plus the body of the message it carries, and pull the four nearest knowledge-base articles for it. Throw away every hit that scores below 0.35, then emit the single best of what survives on article, verbatim, with its article id and its last-reviewed date in the front matter. Do not paraphrase, merge, translate or summarise the article: the node that reads it quotes it, so any edit you make is an edit to a quotation. If nothing clears 0.35, emit nothing at all rather than the least-bad article in the index, an empty result is the correct answer here and the run is built to survive it.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| query | json | required | The routed request, whose label and body become the retrieval query. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| article | markdown | The winning article verbatim, so the composer quotes it rather than paraphrasing. |
Dependencies
1The upstream nodes this card expects to receive from. Whenever a blueprint pins this card, each name is checked against a real edge in that graph. A name without a link is not a published card; it refers to a node inside some graph.
Card values
16 declaredWho the node is. The id is the key the DOT pins.
- id
- kb-resolver
- name
- KB Resolver
- type
- tool
- phases
- none declared
What it does, and the prose the agent is handed when the graph runs.
- action28 words
- Retrieve the k nearest knowledge-base articles for the routed request and return the best match as Markdown, with its article id and last-reviewed date in the front matter.
- spec120 words
- Build a retrieval query out of the routed request on
query, its label plus the body of the message it carries, and pull the four nearest knowledge-base articles for it. Throw away every hit that scores below 0.35, then emit the single best of what survives onarticle, verbatim, with its article id and its last-reviewed date in the front matter. Do not paraphrase, merge, translate or summarise the article: the node that reads it quotes it, so any edit you make is an edit to a quotation. If nothing clears 0.35, emit nothing at all rather than the least-bad article in the index, an empty result is the correct answer here and the run is built to survive it.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- skills/kb-resolver.md
- tools
- Vector store
- mcp
- qdrant
- params
- k: 4, min_score: 0.35
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- query : json
- outputs
- article : markdown
- dependencies
- intent-router
- cannot
- no type is refused
- will_not
- edit the article it returns
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes40 words
- Read-only against the knowledge base, and it returns nothing at all below
min_scorerather than handing the composer the least-bad article in the index.vector-storeretrieves what the factory itself embedded, which is why no external-access marker is inferred here.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- kb-resolver@1.0.0currentsha256:e17b150feb881d14b1b3f6fa2efb90d8b74fd4bdbdcd82da6a656f86863b77fa
pinned byFrontline Triage
autogen/frontline-triage
A digest is a fingerprint (SHA-256) of the card's content, computed without the author and provenance fields. The same card from two people gets the same digest; any edit gets a new one.
First published version, so there is nothing to compare yet. Versions are never edited in place: the next change arrives as a new version, and the differences between the two documents are listed here.
Community notes (0)
No notes yet.
Nobody has posted about this node card yet.
Sign in to post a note.