← Cognitive DatabaseCONTENT HISTORY

Update to Cognitive Database

Snapshot Nov 18, 2026 · 06:17 UTC · version 0.1.7

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Inspect and manage CognitiveDB Catalogs, Schemas, Tables, and other supported Catalog-contained data assets, including metadata lifecycles and non-CTAS SQL DDL with exact targets, confirmed mutations, and read-back verification.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 267
    },
    {
      "relative_path": "references/catalog-lifecycle.md",
      "size_in_bytes": 1261
    },
    {
      "relative_path": "references/schema-ddl.md",
      "size_in_bytes": 3004
    }
  ],
  "name": "cognitivedb-manage-data-assets",
  "skill_md_contents": "---\nname: cognitivedb-manage-data-assets\ndescription: >-\n  Inspect and manage CognitiveDB Catalogs, Schemas, Tables, and other supported\n  Catalog-contained data assets, including metadata lifecycles and non-CTAS SQL\n  DDL with exact targets, confirmed mutations, and read-back verification.\nmetadata:\n  version: \"dev-1.18.2-codex.1\"\n---\n\n# Manage CognitiveDB Data Assets\n\nNever invent IDs, fields, cascade behavior, ownership, or workspace context.\nTreat the live SQL DDL Tool description and input schema as authoritative for\nsupported statement classes, syntax, and validation.\n\n## Boundaries\n\n- Own Catalog/Schema lifecycle and metadata plus live-supported SQL DDL for\n  Catalog-contained data assets, except CTAS. Route CTAS to\n  `cognitivedb-write-data` for its combined table-creation and data-write impact.\n- Route ownership and permissions to `cognitivedb-administer-access`, Computes to `cognitivedb-manage-computes`, and SQL files elsewhere.\n- Prefer dedicated MCP tools. Never use browser or HTTP.\n\n## Core Instructions\n\n- Bind the current Space and resolve one exact Catalog, Schema, or data asset.\n  Stop on zero, multiple, inconsistent, or cross-Space matches.\n- Identify the signed-in user from `cognitivedb_user_current_get` when identity matters;\n  this profile read needs no Space and does not establish roles or capabilities.\n  The current Space's creator identifies that resource's creator, not the user.\n- For creation-history claims, require an explicit creator field or authoritative\n  creation audit for each object. Load `cognitivedb-administer-access` for audit\n  evidence when needed; if it cannot establish the creator, report unknown.\n  Current ownership neither proves nor disproves\n  who created it, including after ownership transfer. Check Catalogs and Schemas\n  independently; do not infer a Schema's creator from its parent Catalog.\n  If creator evidence is unavailable, mark creation history unknown. An ownership\n  inventory may be offered only as a clearly labeled alternative, not as the\n  answer to which objects the user created.\n- Use metadata search only to find assets by keyword. To browse the Catalog\n  hierarchy, use the Catalog, Schema, and Table list tools; do not treat search\n  results as a complete tree.\n- When the user has not chosen a target for a new Table, prefer a suitable\n  Catalog whose live owner matches the current user. Otherwise disclose the\n  recommended Catalog's owner or that ownership is unverified. Visibility and\n  effective capabilities do not establish ownership.\n- For `CREATE TABLE` without `AS SELECT` or table-schema design, load\n  `cognitivedb-gpu-workload-guidance` before presenting the DDL and follow its\n  compatibility guidance.\n- Before a Catalog mutation read [Catalog lifecycle\n  details](references/catalog-lifecycle.md). Reject duplicate creation, submit\n  only requested update fields, and reject empty updates.\n- Before every Catalog, Schema, or data-asset mutation, including creation,\n  resolve the exact operation first. For inline DDL, prepare the statement and\n  Compute before asking; target selection alone is not execution approval.\n  Present one approval question binding the target and change, including\n  visible dependencies, cascade behavior, and impact when applicable. Present\n  that question directly through the host's available interaction mechanism, and do not call\n  the mutation until the user explicitly approves it. The original request, an\n  execution announcement, or Tool confirmation metadata is not approval; a\n  runtime-provided confirmation remains an additional gate. Stop when unknown\n  cascade behavior materially changes the risk. Reuse an existing explicit\n  approval for that pending operation with identical statement, target, Compute, and impact\n  within the current task; do not ask a second generic approval before the exact\n  DDL approval. Preserve any additional live runtime confirmation.\n- Before Catalog deletion, inspect the dedicated impact result for contained\n  objects, grants, affected grantees, and current-Space visibility. Include that\n  evidence in confirmation and do not substitute generic discovery.\n- Use dedicated lifecycle tools when available. For Schema SQL, read [Schema\n  lifecycle SQL](references/schema-ddl.md). Execute SQL DDL only when its class\n  is explicitly supported by the live tool description.\n- For an inline DDL mutation, show and confirm one exact statement and execute\n  it once unchanged. Do not manually decompose an explicitly requested\n  multi-statement initialization or migration when the task's SQL preparation\n  workflow or an owning specialization supplies a complete deterministic SQL\n  artifact and validation summary. In\n  that case, load `cognitivedb-manage-sql-files` and hand off the unchanged\n  artifact for snapshot-bound asynchronous execution. Use inline DDL when no\n  such reviewed artifact workflow is available; never create a SQL File merely\n  to hide statements or reduce confirmation. After an eligible artifact handoff,\n  stop the inline workflow; resume it only if the SQL File owner rejects a\n  specific statement as unsupported.\n- Bind inline SQL DDL execution to one exact runnable Compute. Reuse an exact\n  user-selected Compute or a still-runnable session-approved Compute without\n  reopening the choice. Load `cognitivedb-manage-computes` when the user has not\n  selected a Compute, CPU/GPU or specification guidance is required, multiple\n  runnable candidates create a material choice, the selected Compute is\n  incompatible or not runnable, or any lifecycle action is required. Treat\n  Suspended with Auto Resume as runnable only when the live DDL contract supports\n  automatic resume. Bind the DDL confirmation to the selected Compute; SQL\n  approval is not Compute approval.\n  Treat the result as authoritative for authorization and validation. Never\n  treat ownership, grants, or asset capabilities such as `edit_remote` as SQL\n  DDL authorization unless the live DDL Tool contract defines that preflight.\n  Preserve and manage only its exact execution reference. Read status once per turn. For a requested\n  cancellation, present the exact execution, target, completed-statement impact, and\n  partial-change risk; present the confirmation directly, cancel once after\n  approval, and read status once. Only `CANCELED` confirms cancellation. Never\n  resubmit an unknown execution.\n- Verify each mutation from the exact target's live metadata or absence. Do not\n  use Query History to recover a dedicated Catalog-tool mutation, claim hidden\n  dependencies, or retry an uncertain result without exact state evidence.\n\n## Allowed MCP Tools\n\n- `cognitivedb_catalog_create`\n- `cognitivedb_catalog_delete`\n- `cognitivedb_catalog_delete_impact_check`\n- `cognitivedb_catalog_list`\n- `cognitivedb_catalog_metadata_search`\n- `cognitivedb_catalog_schemas`\n- `cognitivedb_catalog_table_columns`\n- `cognitivedb_catalog_tables`\n- `cognitivedb_catalog_update`\n- `cognitivedb_compute_describe`\n- `cognitivedb_compute_list`\n- `cognitivedb_query_history_list`\n- `cognitivedb_query_history_show`\n- `cognitivedb_space_current_get`\n- `cognitivedb_space_list`\n- `cognitivedb_sql_ddl_execute`\n- `cognitivedb_sql_execution_cancel`\n- `cognitivedb_sql_execution_results_get`\n- `cognitivedb_sql_execution_status_get`\n- `cognitivedb_user_current_get`\n"
}

SHA-256 of public snapshot: 64bb3eb87d163f88e09f8232e9919441ed75a099ec28e0ebb525f5e2d56d0526