iiRecord
Agentic AI Atlas · GAP-L2-P0-pathdescriptor-undeclared-but-referenced
page:process-gaps-GAP-L2-P0-pathdescriptor-undeclared-but-referenceda5c.ai
II.
Page JSON

page:process-gaps-GAP-L2-P0-pathdescriptor-undeclared-but-referenced

Structured · live

GAP-L2-P0-pathdescriptor-undeclared-but-referenced json

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

File · wiki/process/gaps/GAP-L2-P0-pathdescriptor-undeclared-but-referenced.mdCluster · wiki
Record JSON
{
  "id": "page:process-gaps-GAP-L2-P0-pathdescriptor-undeclared-but-referenced",
  "_kind": "Page",
  "_file": "wiki/process/gaps/GAP-L2-P0-pathdescriptor-undeclared-but-referenced.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "GAP-L2-P0-pathdescriptor-undeclared-but-referenced",
    "displayName": "GAP-L2-P0-pathdescriptor-undeclared-but-referenced",
    "slug": "process/gaps/GAP-L2-P0-pathdescriptor-undeclared-but-referenced",
    "articlePath": "wiki/process/gaps/GAP-L2-P0-pathdescriptor-undeclared-but-referenced.md",
    "article": "# GAP-L2-P0-pathdescriptor-undeclared-but-referenced\n\n| Field | Value |\n|---|---|\n| id | gap:pathdescriptor-undeclared-but-referenced |\n| title | PathDescriptor referenced 6+ times in coverage-checklist but missing from ontology-schema.yaml and 02-node-kinds/ |\n| level | 2 |\n| priority | P0 |\n| discoveredAt | 2026-04-28T00:00:00Z |\n| source | C:/work/v6/graph/coverage-checklist.md vs schema/ontology-schema.yaml |\n| status | open |\n| owner | tbd |\n\n## Current state\n`coverage-checklist.md` references `PathDescriptor` in at least 4 rows (\"Run dir layout PathDescriptor per file\", \"PathDescriptor for `~/.a5c/`\", \"Layout version\", others). It is **NOT** present in `schema/ontology-schema.yaml` `nodeKinds:` list (verified by grep). It is **NOT** in `02-node-kinds/README.md` cluster table. The repo agent-catalog DOES define `PathDescriptor`. So the v6 schema cites a NodeKind that does not exist.\n\n## Desired state\nAdd `PathDescriptor` NodeKind in v6 ontology-schema.yaml, lift the repo definition, and document in `02-node-kinds/catalog-meta.md` (or new file). All coverage-checklist rows resolve to a real schema element.\n\n## Evidence\n- C:/work/v6/graph/schema/ontology-schema.yaml (no PathDescriptor)\n- C:/work/v6/graph/coverage-checklist.md (multiple PathDescriptor mentions)\n- packages/agent-catalog/graph/schema/ontology-schema.yaml lines 221-229\n\n## Propagation status\n- Level 1: open (also a Level 1 gap — see GAP-L1-P2-repo-graph-cisurface-packagesurface.md)\n- Level 2: open\n\n## Propagation chain\n- Level 2: add NodeKind + node-kind .md spec, fix invariant V-12.5 (markdown↔YAML parity).\n\n## Notes\nThis is the single largest internal-consistency violation: schema is supposed to be self-consistent; coverage-checklist proves it isn't.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:process-gaps",
      "to": "page:process-gaps-GAP-L2-P0-pathdescriptor-undeclared-but-referenced",
      "kind": "contains_page"
    }
  ]
}