← 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": "Resolve the connection and Space in each conversation for CognitiveDB operations that require Space context.",
"included_files": [],
"name": "cognitivedb-discipline",
"skill_md_contents": "---\nname: cognitivedb-discipline\ndescription: >-\n Resolve the connection and Space in each conversation for CognitiveDB operations\n that require Space context.\nmetadata:\n version: \"dev-1.0.1-chatgpt.1\"\n---\n\n# CognitiveDB Discipline\n\nKeep the selected connection, Space ID, Space name, and organization in the\nconversation context. Resume the user's task once the target is resolved.\n\n## Core Instructions\n\nFor an own-profile or Space-list-only request, use `cognitivedb_user_current_get`\nor `cognitivedb_space_list` through the intended connection without selecting a\nSpace. Apply the following Space-selection rules only to dependent operations\nwhose live Tool contract requires Space context.\n\n1. For a Space-scoped task, honor an explicit user target; otherwise reuse this\n conversation's selected Space. When unresolved, call `cognitivedb_space_list`\n through the intended connection.\n Use the returned `project_id` as `space_id`.\n\n2. When user selection is needed, present the candidates through GenUI.\n Highlight each Space's organization alongside its name; group candidates by\n organization when useful. Bind each selection to the actual Space ID and send\n that ID in the next user message. Match the reply to the current connection's\n candidates before continuing. Require selection even for a single candidate.\n A list-only request finishes with the list.\n\n3. Use the selected Space for dependent operations. Resolve again when the user\n changes the target or connection, then resolve Catalogs, Computes, and other\n resources within that Space.\n\n4. Supply an explicit `space_id` and connection whenever assigning Space-related\n work to a child conversation or Agent. The parent conversation resolves the\n target and manages the children. Children use the supplied target; if missing,\n request it from the parent.\n\n5. After each Space-related task, report the Space name, Space ID, and organization.\n"
}SHA-256 of public snapshot: 0aed140d3fd1cd5d871b6611a7eb293f091ef69431c4c9d283931ec37a6bec65