II.
OpenQuestion JSON
Structured · liveopen-question:a5c-implementation-source-file-pinning
Pin a5c implementation evidence to source files json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "open-question:a5c-implementation-source-file-pinning",
"_kind": "OpenQuestion",
"_file": "catalog-meta/open-questions/source-pinning-questions-2026-05.yaml",
"_cluster": "catalog-meta",
"attributes": {
"displayName": "Pin a5c implementation evidence to source files",
"description": "Source-level a5c implementation facts should be pinned to exact repository\nfiles for core loop policy, runtime tool-host behavior, platform plugin\nregistry behavior, and UI primitives so attribute-level claims can cite\nstable source-file evidence instead of broad repository evidence.\n",
"owner": "@a5c-ai/catalog-stewards",
"affectedEntities": [
"agent-core-impl:a5c.core@current",
"agent-runtime-impl:a5c.runtime@current",
"agent-platform-impl:a5c.platform@current",
"agent-ui-impl:a5c.ui@current"
],
"status": "open",
"raisedAt": "2026-05-04T00:00:00Z"
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "gap:source-file-pinning-for-agent-implementations",
"to": "open-question:a5c-implementation-source-file-pinning",
"kind": "raised_question",
"attributes": {}
}
]
}