II.
KnowledgeFabricImpl JSON
Structured · liveknowledge-fabric-impl:confluence-fabric
Confluence as Enterprise Knowledge Fabric json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "knowledge-fabric-impl:confluence-fabric",
"_kind": "KnowledgeFabricImpl",
"_file": "agent-stack/knowledge-fabric-impls/saas-knowledge-fabrics.yaml",
"_cluster": "agent-stack",
"attributes": {
"displayName": "Confluence as Enterprise Knowledge Fabric",
"description": "Confluence as an enterprise knowledge fabric. Spaces, pages, labels,\nand macros organize knowledge with Atlassian's permission model for\naccess control. REST API and Forge apps enable programmatic access.\nConfluence's strength is enterprise adoption — it is often the system\nof record for technical documentation, runbooks, postmortems, and\narchitectural decisions in large organizations. As a knowledge fabric,\nConfluence provides the human-maintained knowledge layer that agents\ncan query via API or RAG pipeline.\n",
"knowledgeFileFormats": [
"confluence-storage-format",
"markdown (export)"
],
"retrievalStrategy": "api-query",
"knowledgePersistence": "cloud-saas",
"knowledgeScopes": [
"organization",
"enterprise"
],
"autoExtractionSupport": false,
"notes": "Confluence's main knowledge fabric advantage is ubiquity — it is already\nthe knowledge system in most enterprises. The challenge is knowledge\nquality — Confluence wikis often become graveyards of outdated pages.\nEffective knowledge fabric use requires active curation, page ownership,\nand staleness detection. Many enterprise RAG systems use Confluence as\na primary connector for exactly this reason.\n"
},
"outgoingEdges": [
{
"from": "knowledge-fabric-impl:confluence-fabric",
"to": "layer:12-knowledge-fabric",
"kind": "realizes",
"attributes": {}
},
{
"from": "knowledge-fabric-impl:confluence-fabric",
"to": "tool:confluence",
"kind": "integrates_with",
"attributes": {}
}
],
"incomingEdges": []
}