II.
Gap JSON
Structured · livegap:source-file-pinning-for-agent-implementations
Pin implementation claims to exact source files json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "gap:source-file-pinning-for-agent-implementations",
"_kind": "Gap",
"_file": "catalog-meta/gaps/source-pinning-gaps-2026-05.yaml",
"_cluster": "catalog-meta",
"attributes": {
"title": "Pin implementation claims to exact source files",
"level": 2,
"priority": "P2",
"discoveredAt": "2026-05-04T00:00:00Z",
"source": "Some implementation claims are currently backed by broad repository or\npublic documentation evidence rather than exact source-file evidence.\n",
"currentState": "A5C and Codex implementation records have graph-local and public-document\nevidence, but some runtime/core/platform internals are not pinned to exact\nstable source-file URLs.\n",
"desiredState": "Exact source-file EvidenceSource records exist for command-reference,\ncore-loop, runtime dispatch, platform registry, UI primitive, stop-detection,\ntool-dispatch, and Responses event-handling claims where those details are\nasserted by implementation-specific graph nodes.\n",
"propagationStatus": {
"agent-stack": "not-started",
"evidence-sources": "not-started",
"claims": "not-started"
},
"status": "open",
"markdownRef": "catalog-meta/open-questions/source-pinning-questions-2026-05.yaml",
"owner": "@a5c-ai/catalog-stewards"
},
"outgoingEdges": [
{
"from": "gap:source-file-pinning-for-agent-implementations",
"to": "open-question:a5c-public-command-reference-source-pinning",
"kind": "raised_question",
"attributes": {}
},
{
"from": "gap:source-file-pinning-for-agent-implementations",
"to": "open-question:a5c-implementation-source-file-pinning",
"kind": "raised_question",
"attributes": {}
},
{
"from": "gap:source-file-pinning-for-agent-implementations",
"to": "open-question:codex-runtime-source-file-pinning",
"kind": "raised_question",
"attributes": {}
}
],
"incomingEdges": []
}