PQL: Replace artifact protocols with targeted CLI/metadata checks #19
Conversation
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
This reverts commit 4debfe0.
🚀 PromptQL Build CompleteBuild Version: Description: PR #19: PQL: Replace artifact protocols with targeted CLI/metadata checks |
|
No description provided. |
✅ PromptQL Build AppliedBuild Version: |
robertjdominguez
added a commit
that referenced
this pull request
Aug 10, 2025
## Description - Replaced overly complex artifact-checking protocols with targeted CLI and metadata validation while maintaining accuracy requirements Previously, the DocsBot had a paranoid verification system that required checking every existing artifact before answering any question, creating unnecessary friction: ````yaml path=pql/globals/metadata/promptql-config.hml mode=EXCERPT ### Step 1: Check Existing Context First (MANDATORY) Before fetching new documentation: 1. **ALWAYS check if any existing artifacts contain information relevant to the user's question** 2. **ALWAYS examine the actual content of existing artifacts, not just their titles or descriptions** **VIOLATION CHECK: If you provide specific technical details (commands, syntax, flags, etc.) without first checking existing artifacts, you are violating this instruction and will be terminated.** ```` Now the system uses focused validation that targets the two most critical areas where accuracy matters - CLI commands and metadata objects: ````yaml path=pql/globals/metadata/promptql-config.hml mode=EXCERPT ## CLI Command Validation Before providing any CLI command information to users, ALWAYS validate the command exists by checking the documentation: 1. **Check command existence**: Query `app.docs_bot_doc_content` for pages with URLs matching the pattern: `https://promptql.io/docs/reference/cli/commands/ddn_[command]_[subcommand]` ## Metadata Object Validation Before discussing metadata objects, ALWAYS validate they exist and have examples: 1. **Check object existence**: Query `app.docs_bot_doc_content` for pages with URLs matching: `https://promptql.io/docs/reference/metadata-reference/[object-name]` ```` The changes eliminate the bureaucratic artifact management overhead while maintaining precision where it counts. Instead of forcing the bot to examine every piece of existing context before answering simple questions, it now applies targeted validation to CLI commands and metadata objects - the areas where hallucination would actually break user workflows. This keeps responses accurate without the performance penalty of mandatory artifact checking.
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.
Description
Previously, the DocsBot had a paranoid verification system that required checking every existing artifact before answering any question, creating unnecessary friction:
Now the system uses focused validation that targets the two most critical areas where accuracy matters - CLI commands and metadata objects:
The changes eliminate the bureaucratic artifact management overhead while maintaining precision where it counts. Instead of forcing the bot to examine every piece of existing context before answering simple questions, it now applies targeted validation to CLI commands and metadata objects - the areas where hallucination would actually break user workflows. This keeps responses accurate without the performance penalty of mandatory artifact checking.