← Cognitive DatabaseCONTENT HISTORY
WHAT CHANGED
Update to Cognitive Database
Snapshot Nov 18, 2026 · 06:17 UTC · version 0.1.7
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Cognitive Database and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Guide CognitiveDB table design, ingestion mapping, and SQL construction for GPU-compatible execution and avoid known unsupported constructs while keeping internal execution-routing behavior out of user-facing responses. Use when the user requests GPU execution, GPU-oriented design, or GPU compatibility review.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 288
},
{
"relative_path": "references/gpu-execution-support.md",
"size_in_bytes": 3312
}
],
"name": "cognitivedb-gpu-workload-guidance",
"skill_md_contents": "---\nname: cognitivedb-gpu-workload-guidance\ndescription: >-\n Guide CognitiveDB table design, ingestion mapping, and SQL construction for\n GPU-compatible execution and avoid known unsupported constructs while keeping\n internal execution-routing behavior out of user-facing responses. Use when the\n user requests GPU execution, GPU-oriented design, or GPU compatibility review.\nmetadata:\n version: \"dev-1.5.0\"\n---\n\n# CognitiveDB GPU Workload Guidance\n\nGuide GPU-compatible design and SQL without owning Catalog, ingestion, Compute,\nor SQL mutations.\n\n## Boundaries\n\n- Provide GPU compatibility guidance only. Route read-only SQL to\n `cognitivedb-data-analysis`, Compute operations to\n `cognitivedb-manage-computes`, CTAS to `cognitivedb-write-data`, other DDL to\n `cognitivedb-manage-data-assets`, cloud files or external database tables to\n `cognitivedb-manage-ingestion`, or local files to\n `cognitivedb-load-local-files`.\n- Route CPU/GPU Compute selection, specification choice, and resource lifecycle\n operations to `cognitivedb-manage-computes`.\n- Do not expose internal execution routing, recovery behavior, strict execution\n modes, or related evidence in user-facing responses.\n- Do not promise GPU-native execution from Compute selection alone.\n- Never enable strict execution modes or change session configuration unless an\n owning live Tool explicitly supports it and the user requests it.\n\n## Core Instructions\n\n- Read [GPU execution support](references/gpu-execution-support.md) when table\n types, ingestion mappings, SQL operators, or functions affect the request.\n- For table design, distinguish the user's execution intent:\n - When GPU-native execution is required, identify incompatible or partially\n supported column types before presenting the schema. Do not claim\n compatibility when the required later operations are unknown.\n - When GPU execution is preferred, recommend GPU-native types where business\n semantics are preserved.\n - When execution intent is unspecified, do not require a CPU/GPU choice.\n Do not add unsolicited GPU compatibility commentary.\n- Treat GPU compatibility as a property of later queries and operations, not of\n `CREATE TABLE` execution itself.\n- For ingestion, preserve GPU-native destination types and flag mappings that\n introduce unsupported types, lossy casts, or runtime parsing.\n- Before query execution, use known GPU-native limitations to construct a\n compatible statement when semantics can be preserved.\n- Suggest a GPU-compatible rewrite only when it preserves the requested result.\n Otherwise retain the original semantics without exposing internal routing.\n- Keep execution-path evidence internal. Report the requested result, supported\n compatibility conclusion, or actionable query limitation.\n- For performance comparisons, keep the execution path, data, query semantics,\n Compute, cache state, concurrency, and measurement boundary comparable. Do\n not attribute a timing change to GPU execution unless structured evidence\n verifies comparable routing; do not expose that routing evidence.\n"
}SHA-256 of public snapshot: 20a8cc909ce2fb96d5c180a85a29dd48b9ed3ab605efad60298e2ba0c9756444