{
  "object_name": "Integration Map",
  "object_slug": "integration-map",
  "version": "1.0",
  "last_reviewed": "2026-06-24",
  "owner": "LPM / Lapemo",
  "object_type": "LPM Knowledge Object",
  "primary_lpm_layers": [
    "Platform Structure",
    "Information Ecology",
    "Governance Architecture",
    "AI Amplification"
  ],
  "connected_lpm_layers": [
    "Ownership Map",
    "Decision Architecture",
    "Communication Architecture",
    "Source-of-Truth Map",
    "Data Lineage Map",
    "Workflow Inventory"
  ],
  "purpose": "Map how systems, data, workflows, controls, and AI tools connect across the enterprise so dependencies, owners, failure paths, and control boundaries are visible.",
  "intended_audience": [
    "Executives",
    "Transformation Leaders",
    "Enterprise Architects",
    "Integration Owners",
    "Platform Owners",
    "Data Leaders",
    "AI Governance Teams",
    "Risk and Compliance",
    "Product and Operations Leaders"
  ],
  "required_fields": [
    {
      "name": "Integration ID",
      "definition": "Unique identifier for the integration, connector, automation, file transfer, API, event, RPA bot, data pipeline, or manual handoff",
      "required": "Yes"
    },
    {
      "name": "Integration name",
      "definition": "Human-readable name used by business and technical teams",
      "required": "Yes"
    },
    {
      "name": "Integration type",
      "definition": "API, webhook, event stream, ETL/ELT, file transfer, database replication, RPA, workflow automation, native connector, manual handoff, or AI tool action",
      "required": "Yes"
    },
    {
      "name": "Business purpose",
      "definition": "The business capability, workflow, decision, report, control, or AI use case supported by the integration",
      "required": "Yes"
    },
    {
      "name": "Source system",
      "definition": "Platform, data product, team, vendor, document, or human process sending the data or work item",
      "required": "Yes"
    },
    {
      "name": "Target system",
      "definition": "Platform, workflow, dashboard, AI tool, data store, control system, or team receiving the data or work item",
      "required": "Yes"
    },
    {
      "name": "Source owner",
      "definition": "Accountable owner for the source system, source data, or source workflow",
      "required": "Yes"
    },
    {
      "name": "Target owner",
      "definition": "Accountable owner for the receiving system, receiving process, or downstream use",
      "required": "Yes"
    },
    {
      "name": "Data owner / steward",
      "definition": "Owner of definitions, quality, freshness, and permitted usage for critical data moved through the integration",
      "required": "Required when data moves"
    },
    {
      "name": "Workflow owner",
      "definition": "Owner of the business process or operating workflow affected by the integration",
      "required": "Required when workflow-critical"
    },
    {
      "name": "Control owner",
      "definition": "Owner of access, audit, retention, approval, segregation, exception, or compliance rule",
      "required": "Required when controlled"
    },
    {
      "name": "Critical objects moved",
      "definition": "Records, metrics, decisions, documents, tickets, approvals, model inputs, outputs, prompts, or evidence objects moved across the integration",
      "required": "Yes"
    },
    {
      "name": "Trigger",
      "definition": "Schedule, event, user action, AI action, approval, status change, file drop, API call, or manual request that starts the integration",
      "required": "Yes"
    },
    {
      "name": "Frequency / latency",
      "definition": "Real-time, near-real-time, hourly, daily, weekly, monthly, ad hoc, batch, or manual",
      "required": "Yes"
    },
    {
      "name": "Transformation logic",
      "definition": "Mapping, enrichment, filtering, aggregation, validation, normalization, scoring, or prompt/model processing applied during movement",
      "required": "Yes"
    },
    {
      "name": "Validation checks",
      "definition": "Completeness, schema, reconciliation, quality, access, approval, exception, and error-handling checks",
      "required": "Yes"
    },
    {
      "name": "Failure path",
      "definition": "How failures are detected, routed, escalated, retried, recovered, and evidenced",
      "required": "Yes"
    },
    {
      "name": "Observability signal",
      "definition": "Logs, SLA, freshness monitor, queue depth, error rate, reconciliation report, alert, or manual check",
      "required": "Yes"
    },
    {
      "name": "AI usage boundary",
      "definition": "Whether AI can read, summarize, classify, recommend, trigger, update, approve, or act through this integration",
      "required": "Yes"
    },
    {
      "name": "Human review rule",
      "definition": "When a human must review AI-triggered movement, exceptions, data updates, or downstream actions",
      "required": "Required when material"
    },
    {
      "name": "Risk tier",
      "definition": "Low, moderate, high, critical, regulated, customer-impacting, financial-impacting, or AI-actioning",
      "required": "Yes"
    },
    {
      "name": "Evidence link",
      "definition": "Log, ticket, control record, policy, runbook, data lineage reference, source-of-truth record, or decision log link",
      "required": "Yes"
    },
    {
      "name": "Lifecycle state",
      "definition": "Discover, pilot, active, monitored, governed, constrained, duplicate, replace, retire, or exception",
      "required": "Yes"
    },
    {
      "name": "Review date",
      "definition": "Next review of purpose, ownership, data movement, controls, AI boundary, and failure path",
      "required": "Yes"
    },
    {
      "name": "Version",
      "definition": "Object version, owner, last reviewed date, and change history",
      "required": "Yes"
    }
  ],
  "integration_types": [
    {
      "type": "API / service call",
      "definition": "Synchronous system-to-system request and response",
      "example": "CRM calls pricing service",
      "common_risk": "Timeouts, version drift, missing owner, weak auth"
    },
    {
      "type": "Webhook / event trigger",
      "definition": "System pushes event when something changes",
      "example": "Contract signed triggers onboarding workflow",
      "common_risk": "Silent failures, duplicate events, no retry path"
    },
    {
      "type": "Event stream",
      "definition": "Continuous publish/subscribe movement across systems",
      "example": "Kafka events feed data products and alerts",
      "common_risk": "Schema changes, consumer sprawl, weak lineage"
    },
    {
      "type": "ETL / ELT pipeline",
      "definition": "Batch or scheduled data extraction, transformation, and loading",
      "example": "ERP data into warehouse and BI model",
      "common_risk": "Stale data, transformation opacity, dashboard trust gaps"
    },
    {
      "type": "File transfer",
      "definition": "CSV, flat file, secure transfer, export/import, or vendor feed",
      "example": "Daily HR file to identity system",
      "common_risk": "Manual errors, late files, no validation evidence"
    },
    {
      "type": "Database replication",
      "definition": "Data copied or synchronized between stores",
      "example": "Operational DB to analytics replica",
      "common_risk": "Latency, schema drift, ambiguous source of truth"
    },
    {
      "type": "RPA / bot",
      "definition": "Automation interacts with a UI when no API exists",
      "example": "Bot moves cases between legacy systems",
      "common_risk": "Brittle selectors, hidden credentials, weak audit trail"
    },
    {
      "type": "Workflow automation",
      "definition": "Rules engine or orchestration tool moves work across systems",
      "example": "ServiceNow to Jira to Teams notification",
      "common_risk": "No process owner, no exception routing"
    },
    {
      "type": "Native connector",
      "definition": "Vendor-provided connector between platforms",
      "example": "Salesforce to Slack notification",
      "common_risk": "Limited transparency, permission creep"
    },
    {
      "type": "Manual handoff",
      "definition": "Human moves data or work through chat, email, spreadsheet, meeting, or upload",
      "example": "Analyst emails weekly report",
      "common_risk": "Invisible dependency, stale evidence, AI hallucination risk"
    },
    {
      "type": "AI tool action",
      "definition": "AI retrieves, transforms, summarizes, classifies, updates, or triggers work across systems",
      "example": "Agent updates CRM from meeting notes",
      "common_risk": "No decision rights, source ambiguity, uncontrolled action"
    }
  ],
  "map_stages": [
    {
      "stage": "1. Identify",
      "what_happens": "Catalog the integration, type, business purpose, source, target, trigger, and lifecycle state.",
      "evidence": "App inventory, architecture diagram, workflow inventory, data catalog",
      "key_fields": "Integration ID, type, source, target",
      "common_risk": "Hidden or undocumented connection"
    },
    {
      "stage": "2. Own",
      "what_happens": "Name source owner, target owner, data owner, workflow owner, technical owner, and control owner.",
      "evidence": "Ownership map, platform map, RACI, support model",
      "key_fields": "Owners and review cadence",
      "common_risk": "Ownerless integration or unclear accountability"
    },
    {
      "stage": "3. Trace",
      "what_happens": "Map critical objects, transformation logic, upstream dependencies, downstream consumers, and lineage.",
      "evidence": "Data lineage, source-of-truth map, pipeline config, runbook",
      "key_fields": "Objects moved, mappings, lineage",
      "common_risk": "Decision or AI output cannot be traced"
    },
    {
      "stage": "4. Control",
      "what_happens": "Attach access, security, approval, retention, privacy, audit, reconciliation, and exception rules.",
      "evidence": "GRC records, IAM policy, audit logs, control evidence",
      "key_fields": "Controls and validation checks",
      "common_risk": "Data moves without approval or evidence"
    },
    {
      "stage": "5. Monitor",
      "what_happens": "Define observability, failure detection, SLA, freshness, reconciliation, alerts, and support path.",
      "evidence": "Logs, SLA reports, monitoring, tickets, alerts",
      "key_fields": "Health signal and failure path",
      "common_risk": "Silent failure or brittle handoff"
    },
    {
      "stage": "6. AI-bound",
      "what_happens": "Define what AI can retrieve, summarize, transform, trigger, update, approve, or act on through the integration.",
      "evidence": "AI policy, model registry, permission model, agent logs",
      "key_fields": "AI boundary and human review rule",
      "common_risk": "AI action without authority or audit"
    },
    {
      "stage": "7. Optimize",
      "what_happens": "Decide whether to standardize, govern, automate, consolidate, replace, retire, or accept as an exception.",
      "evidence": "Roadmap, architecture review, risk register, value case",
      "key_fields": "Lifecycle decision and next action",
      "common_risk": "Integration sprawl and automation debt"
    }
  ],
  "integration_archetypes": [
    {
      "archetype": "Operational integration",
      "definition": "Moves work between systems during execution",
      "examples": "Case to ticket, lead to opportunity, order to fulfillment",
      "governance_requirement": "Requires workflow owner, failure path, SLA, and escalation rule"
    },
    {
      "archetype": "Data integration",
      "definition": "Moves data for reporting, analytics, models, or downstream systems",
      "examples": "ERP to warehouse, CRM to lakehouse, HRIS to BI",
      "governance_requirement": "Requires data owner, lineage, transformation logic, freshness, and reconciliation"
    },
    {
      "archetype": "Control integration",
      "definition": "Feeds or enforces access, approvals, risk, policy, audit, or compliance evidence",
      "examples": "IAM provisioning, GRC evidence feed, policy exception",
      "governance_requirement": "Requires control owner, audit trail, evidence, and exception handling"
    },
    {
      "archetype": "Experience integration",
      "definition": "Connects customer, employee, partner, or vendor experiences across tools",
      "examples": "Support ticket to customer portal, HR request to knowledge base",
      "governance_requirement": "Requires experience owner, privacy review, quality checks, and communication rule"
    },
    {
      "archetype": "Knowledge integration",
      "definition": "Moves documents, policies, decisions, templates, playbooks, or knowledge objects",
      "examples": "Confluence to AI knowledge base, SharePoint to search index",
      "governance_requirement": "Requires freshness, source-of-truth, versioning, and AI retrieval boundary"
    },
    {
      "archetype": "AI integration",
      "definition": "Allows AI tools or agents to retrieve, summarize, recommend, update, or act through connected systems",
      "examples": "Copilot reads CRM, agent updates Jira, RAG over policy docs",
      "governance_requirement": "Requires permission boundary, source lineage, human review, logging, and kill switch"
    },
    {
      "archetype": "Shadow integration",
      "definition": "Unapproved or unmanaged movement of data or work",
      "examples": "Manual CSV exports, spreadsheet uploads, personal automations",
      "governance_requirement": "Requires risk triage, unmet-need analysis, and migration plan"
    }
  ],
  "company_versions": {
    "500_plus": [
      {
        "dimension": "Design intent",
        "recommended_pattern": "Create practical visibility into the integrations that keep the company running before tool sprawl and AI pilots create hidden risk."
      },
      {
        "dimension": "Minimum scope",
        "recommended_pattern": "Map the top 25 to 50 integrations across revenue, delivery, finance, people, data, knowledge, and active AI workflows."
      },
      {
        "dimension": "Operating pattern",
        "recommended_pattern": "Monthly review of critical integrations, manual handoffs, owner gaps, and AI-connected workflows."
      },
      {
        "dimension": "AI focus",
        "recommended_pattern": "Do not let AI tools act through integrations until the source, target, owner, review rule, and audit trail are clear."
      },
      {
        "dimension": "Governance need",
        "recommended_pattern": "Name owners, define failure paths, document manual handoffs, and establish source-of-truth relationships."
      },
      {
        "dimension": "Red flags",
        "recommended_pattern": "Spreadsheet uploads, founder/operator-held logic, no support owner, daily CSV exports, AI connected to local files, and no failure alerts."
      }
    ],
    "5000_plus": [
      {
        "dimension": "Design intent",
        "recommended_pattern": "Move from scattered connector knowledge to domain-level integration governance across platforms, data products, controls, and AI use cases."
      },
      {
        "dimension": "Minimum scope",
        "recommended_pattern": "Map Tier 1 integrations, critical data pipelines, workflow automations, cross-functional handoffs, and AI-connected systems."
      },
      {
        "dimension": "Operating pattern",
        "recommended_pattern": "Quarterly integration governance by business domain with architecture, platform, data, risk, and transformation owners."
      },
      {
        "dimension": "AI focus",
        "recommended_pattern": "Classify integrations by AI usage boundary: retrieve, summarize, recommend, trigger, update, approve, act, or blocked."
      },
      {
        "dimension": "Governance need",
        "recommended_pattern": "Connect integration records to platform maps, data lineage maps, source-of-truth maps, decision logs, and control evidence."
      },
      {
        "dimension": "Red flags",
        "recommended_pattern": "Duplicate connectors, brittle automations, inconsistent customer or employee data, weak pipeline ownership, and unmanaged vendor integrations."
      }
    ],
    "10000_plus": [
      {
        "dimension": "Design intent",
        "recommended_pattern": "Create enterprise integration control across business units, shared services, regulated data, external partners, AI agents, and control systems."
      },
      {
        "dimension": "Minimum scope",
        "recommended_pattern": "Map critical enterprise integrations, regulated data flows, external data sharing, high-risk automation, model inputs, agent tool-use paths, and control evidence feeds."
      },
      {
        "dimension": "Operating pattern",
        "recommended_pattern": "Enterprise integration council, domain integration owners, automated dependency discovery, control evidence packs, and architecture exception governance."
      },
      {
        "dimension": "AI focus",
        "recommended_pattern": "AI agents require integration-specific permission boundaries, model risk tiering, source lineage, human review, tool-use logs, and kill-switch rules."
      },
      {
        "dimension": "Governance need",
        "recommended_pattern": "Tie integration changes to architecture, security, privacy, procurement, GRC, data governance, model risk, and executive decision rights."
      },
      {
        "dimension": "Red flags",
        "recommended_pattern": "Silent API dependency, federated integration sprawl, unmanaged event consumers, vendor black boxes, external data leakage, and AI actions without approval authority."
      }
    ]
  },
  "scoring_logic": [
    {
      "dimension": "Ownership clarity",
      "score_range": "0-5",
      "good_state": "Source, target, data, workflow, technical, and control owners are named for critical integrations."
    },
    {
      "dimension": "Purpose clarity",
      "score_range": "0-5",
      "good_state": "The business purpose, supported workflow, decision, data object, or control is explicit."
    },
    {
      "dimension": "Lineage clarity",
      "score_range": "0-5",
      "good_state": "Source, target, transformation logic, downstream consumers, and evidence links are traceable."
    },
    {
      "dimension": "Reliability visibility",
      "score_range": "0-5",
      "good_state": "Failure detection, SLA, retry, monitoring, reconciliation, and support path are defined."
    },
    {
      "dimension": "Governance strength",
      "score_range": "0-5",
      "good_state": "Access, approvals, privacy, retention, audit, exceptions, and controls are attached."
    },
    {
      "dimension": "AI boundary clarity",
      "score_range": "0-5",
      "good_state": "AI retrieval, trigger, update, approval, and action permissions are explicit and reviewed."
    },
    {
      "dimension": "Manual handoff exposure",
      "score_range": "0-5",
      "good_state": "Manual exports, uploads, spreadsheets, emails, and chat-based movement are visible and governed."
    },
    {
      "dimension": "Lifecycle discipline",
      "score_range": "0-5",
      "good_state": "Integrations are actively governed as discover, pilot, active, monitored, governed, replace, retire, or exception."
    }
  ],
  "readiness_formula": "Average the eight dimension scores. 0-1.9 Fragmented, 2.0-3.4 Mapped, 3.5-4.4 Governed, 4.5-5.0 AI-ready.",
  "ai_prompts": [
    "Given this integration inventory, classify each connection by integration type, risk tier, lifecycle state, source-of-truth relationship, and AI usage boundary.",
    "Identify owner gaps, brittle handoffs, duplicate connectors, undocumented manual integrations, stale data paths, weak failure handling, and ungoverned AI actions.",
    "Score each integration from 0 to 5 across ownership clarity, purpose clarity, lineage clarity, reliability visibility, governance strength, AI boundary clarity, manual handoff exposure, and lifecycle discipline.",
    "Generate an integration dependency map showing source systems, target systems, critical objects moved, transformation logic, downstream consumers, controls, AI consumers, and failure paths.",
    "Recommend whether each integration should be documented, monitored, governed harder, automated, replaced, consolidated, retired, or accepted as an exception.",
    "Create a Lapemo ingestion plan that converts this integration map into integration objects, platform objects, data lineage objects, control objects, workflow objects, evidence objects, and AI boundary rules."
  ],
  "validation_rules": [
    "Every critical integration must have a source owner, target owner, and technical owner.",
    "Every integration moving critical data must identify the data owner, source-of-truth relationship, transformation logic, freshness expectation, and validation checks.",
    "Every workflow-critical integration must have a workflow owner, failure path, escalation path, and recovery rule.",
    "Every integration used by AI must have an approved AI usage boundary, human review rule, source lineage, and audit trail.",
    "No AI agent should trigger, update, approve, or act through an integration unless decision rights and control rules are defined.",
    "Manual handoffs must be mapped and scored instead of ignored because they often represent the highest automation and AI risk.",
    "A connection cannot be classified as governed if failure detection, owner notification, evidence, and review cadence are missing.",
    "Status must never be encoded only by color; use labels such as active, monitored, governed, constrained, duplicate, replace, retire, exception, blocked, or disputed."
  ],
  "lapemo_mapping": [
    {
      "lapemo_object": "Knowledge object",
      "fields_or_entities": "Integration Map",
      "use": "Canonical reusable artifact for system dependency control and AI-safe connectivity."
    },
    {
      "lapemo_object": "Integration object",
      "fields_or_entities": "Integration ID, type, source, target, trigger, lifecycle, risk tier",
      "use": "Creates the enterprise integration inventory and dependency layer."
    },
    {
      "lapemo_object": "Platform object",
      "fields_or_entities": "Source system, target system, upstream and downstream dependencies",
      "use": "Connects integrations to platforms and systems of record."
    },
    {
      "lapemo_object": "Ownership object",
      "fields_or_entities": "Source owner, target owner, data owner, workflow owner, technical owner, control owner",
      "use": "Connects every connection to accountable humans."
    },
    {
      "lapemo_object": "Data lineage object",
      "fields_or_entities": "Critical objects moved, transformation logic, freshness, quality checks, downstream consumers",
      "use": "Shows how data flows into decisions, dashboards, and AI."
    },
    {
      "lapemo_object": "Workflow object",
      "fields_or_entities": "Trigger, process path, handoffs, decision points, exception routing",
      "use": "Links integrations to recurring work and automation candidates."
    },
    {
      "lapemo_object": "Governance object",
      "fields_or_entities": "Access, approvals, retention, privacy, audit, exception, evidence link",
      "use": "Connects integrations to controls and auditability."
    },
    {
      "lapemo_object": "AI object",
      "fields_or_entities": "AI usage boundary, permissions, human review rule, agent logs, kill switch",
      "use": "Defines what AI can safely do through connected systems."
    }
  ],
  "render_targets": [
    "DOCX template",
    "PDF guide",
    "Website Markdown",
    "JSON skill schema",
    "Interactive form",
    "Lapemo onboarding workflow",
    "Integration dependency graph",
    "Data lineage map",
    "Platform control dashboard",
    "AI boundary review"
  ],
  "automation_policy": {
    "auto_update": false,
    "recommended_mode": "Flag missing owners, brittle integrations, undocumented manual handoffs, stale data movement, weak failure paths, duplicate connectors, ungoverned AI access, and high-risk dependency changes for human approval.",
    "human_approval_required_for": [
      "AI usage boundary changes",
      "critical integration changes",
      "source-of-truth relationship changes",
      "data transformation changes",
      "owner changes",
      "external data sharing",
      "control requirement changes",
      "integration retirement"
    ]
  }
}