iiRecord
Agentic AI Atlas · ADR Decision Log — Architecture Decision Records in git
knowledge-fabric-impl:adr-decision-loga5c.ai
II.
KnowledgeFabricImpl JSON

knowledge-fabric-impl:adr-decision-log

Structured · live

ADR Decision Log — Architecture Decision Records in git json

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

File · agent-stack/knowledge-fabric-impls/git-markdown-knowledge.yamlCluster · agent-stack
Record JSON
{
  "id": "knowledge-fabric-impl:adr-decision-log",
  "_kind": "KnowledgeFabricImpl",
  "_file": "agent-stack/knowledge-fabric-impls/git-markdown-knowledge.yaml",
  "_cluster": "agent-stack",
  "attributes": {
    "displayName": "ADR Decision Log — Architecture Decision Records in git",
    "description": "Architecture Decision Records (ADRs) in git using the MADR format or\nsimilar conventions. Each decision is a numbered markdown file tracking\ncontext, decision drivers, considered options, the decision outcome, and\nconsequences. ADRs create a searchable, append-only decision log that\nexplains why the system is the way it is. Tools like adr-tools, log4brains,\nand adr-manager help maintain the log.\n",
    "knowledgeFileFormats": [
      "markdown"
    ],
    "retrievalStrategy": "file-hierarchy",
    "knowledgePersistence": "git-versioned",
    "knowledgeScopes": [
      "project"
    ],
    "autoExtractionSupport": false,
    "notes": "ADRs are the gold standard for capturing architectural decisions. They\nanswer the \"why\" question that code and tests cannot. The MADR template\n(Markdown Any Decision Record) provides a structured format. ADRs are\ntypically stored in docs/adr/ or docs/decisions/ and numbered sequentially.\nThey are immutable once accepted — superseded decisions reference their\nreplacements rather than being edited.\n"
  },
  "outgoingEdges": [
    {
      "from": "knowledge-fabric-impl:adr-decision-log",
      "to": "layer:12-knowledge-fabric",
      "kind": "realizes",
      "attributes": {}
    }
  ],
  "incomingEdges": []
}