← Aivana Database EngineerCONTENT HISTORY

Update to Aivana Database Engineer

Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "production-readiness-check",
  "description": "Check whether CodexDB Agent is safe to run in production with live database connections, signing, audit replay, drivers, and complete skill metadata.",
  "included_files": [],
  "skill_md_contents": "---\nname: production-readiness-check\ndescription: Check whether CodexDB Agent is safe to run in production with live database connections, signing, audit replay, drivers, and complete skill metadata.\n---\n\n# Production Readiness Check\n\nUse this skill before enabling CodexDB Agent against production SQL Server or PostgreSQL.\n\nRun:\n\n```bash\nnode runtime/runTool.js production_readiness_check '{\"environment\":\"production\",\"engine\":\"postgres\"}'\n```\n\nThe tool returns:\n\n- `ready`: true only when no production blockers remain.\n- `blockingIssues`: hard deployment blockers.\n- `warnings`: non-blocking operational risks.\n- `checks`: individual readiness checks for manifests, skill docs, live mode, drivers, migration signing, and audit replay.\n\nProduction should set:\n\n- `CODEXDB_REQUIRE_LIVE_CONNECTION=true`\n- `CODEXDB_MIGRATION_SIGNING_KEY`\n- engine-specific connection variables such as `CODEXDB_POSTGRES_CONNECTION_STRING` or `CODEXDB_SQLSERVER_SERVER`.\n"
}

SHA-256: 7180ddd0c7ebeb186db27a467ece996c40a5b55bb245a951ae083d37ee3140f0