The Integration Surface Map

Every knowledge integration adds a surface — a connection point between the knowledge system and a destination tool. That surface has a maintenance cost, a failure mode, and a freshness characteristic. Most organizations build integration surfaces opportunistically, without tracking the total surface they are maintaining. The integration surface map is the prerequisite for managing that total — and for making deliberate decisions about which new surfaces to add.

1. Inventory the Current Surface List every integration between the knowledge system and external tools: the tool, the integration pattern (push/pull/hybrid), the integration architecture (API-first/embedded), the freshness window, the owner, and the last validation date. This inventory is the integration surface map. Most organizations have more integrations than they can account for — the map makes the surface visible.
2. Surface Cost Assessment For each integration surface, assess the maintenance cost: how many hours per month are spent maintaining this integration? What is the failure rate? What is the impact of an integration failure on the downstream tool and its users? High-cost, high-failure surfaces are candidates for architectural redesign. Low-cost, low-failure surfaces are candidates to leave alone.
3. Surface Rationalization After mapping and assessing, rationalize the surface. Integrate the high-cost surfaces into an API abstraction layer. Deprecate integrations that serve tools no longer in active use. Consolidate duplicate integrations that serve the same tool through different mechanisms. The goal is a surface that is as small as necessary and no larger.

# Knowledge Integration Surface Map
Last Updated: [Date] | Owner: [Name]

## Active Integrations

| Tool | Pattern | Architecture | Freshness SLA | Owner | Last Validated | Failure Rate |
|------|---------|--------------|---------------|-------|----------------|--------------|
| Salesforce CRM | Pull | API-first | On-demand | [Name] | [Date] | 0.1% |
| Slack (bot) | Push + Pull | Embedded | Push: 15min, Pull: real-time | [Name] | [Date] | 0.5% |
| Zendesk | Pull | API-first | On-demand | [Name] | [Date] | 0.2% |
| Confluence | Push | API-first | 30 min | [Name] | [Date] | 1.2% |

## Surface Health

**Total surfaces:** [N]
**Surfaces with owner:** [N] / [total]
**Surfaces validated in last 30 days:** [N] / [total]
**High failure rate (>1%):** [list]

## Rationalization Backlog
- [ ] Migrate [embedded integration] to API-first (owner: [name], target: [date])
- [ ] Deprecate [unused tool] integration (last active: [date])
- [ ] Consolidate [duplicate integrations] under abstraction layer

## Next Review: [Date]