iiRecord
Agentic AI Atlas · infra-diagnostic
lib-process:shared--infra-diagnostica5c.ai
II.
LibraryProcess JSON

lib-process:shared--infra-diagnostic

Structured · live

infra-diagnostic json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · generated-library/processes.yamlCluster · generated-library
Record JSON
{
  "id": "lib-process:shared--infra-diagnostic",
  "_kind": "LibraryProcess",
  "_file": "generated-library/processes.yaml",
  "_cluster": "generated-library",
  "attributes": {
    "displayName": "infra-diagnostic",
    "description": "Shell-first infrastructure diagnostic and remediation template.\nAlways uses shell tasks for process management — never agent tasks for kill/rebuild.\nMandates CWD check for any running Next.js server in the very first diagnostic phase.\nStructure: 5 phases\n  Phase 1: Shell env snapshot (ps aux, /tmp state, PG socket, server CWD check)\n  Phase 2: Breakpoint — human reviews diagnostics before remediation begins\n  Phase 3: Agent-led root cause investigation (reads logs, Prisma schema, env snapshot)\n  Phase 4: Shell-based remediation (from correct /tmp/trip-planner-dev directory)\n  Phase 5: Breakpoint — confirm environment is healthy\nCritical rule: Server MUST run from /tmp/trip-planner-dev, NOT from project root.\nMissing this check in fix-db-v1 and fix-db-v2 caused 2 unnecessary extra runs.",
    "libraryPath": "library/contrib/rogelsm/infra-diagnostic.js",
    "usesAgents": [
      "remediate"
    ]
  },
  "outgoingEdges": [
    {
      "from": "lib-process:shared--infra-diagnostic",
      "to": "domain:software-engineering",
      "kind": "lib_applies_to_domain",
      "attributes": {
        "weight": 1
      }
    },
    {
      "from": "lib-process:shared--infra-diagnostic",
      "to": "workflow:bug-triage",
      "kind": "lib_implements_workflow",
      "attributes": {
        "weight": 1
      }
    }
  ],
  "incomingEdges": []
}