Integrations Inventory and Attributes - Provenance and Audit attributes for the Integrations Inventory
Integrations Inventory and Attributes
Chapter 26. Provenance and Audit attributes for the Integrations Inventory
Provenance and Audit attributes capture metadata about the integration record itself — how it was created, when it was last updated, and the reliability of its content.
| Attribute Name | Maturity | Description and Notes |
|---|---|---|
| Record Created Date | Walk | Description — The date on which this integration record was first created in the inventory. Benefit(s) — Supports audit and compliance reporting. Source — Manual. Examples — 2024-03-15, 2023-11-01 |
| Record Created By | Walk | Description — The name or role of the individual who created this integration record. Benefit(s) — Provides accountability for record creation and enables follow-up when record quality is questioned. Source — Manual. Examples — Jane Smith (Integration Architect), AI Agent (Claude, 2026-05-15) |
| Last Updated Date | Walk | Description — The date on which any attribute of this integration record was last modified. Benefit(s) — Enables identification of stale records not reviewed within the expected reconciliation cadence. Source — Manual. Examples — 2026-05-15, 2025-09-30 |
| Data Source | Walk | Description — The origin of the data in this integration record — how it was initially discovered and documented. Benefit(s) — Enables data quality assessment. Records sourced from automated discovery are treated differently from manually documented records. Source — Manual. Examples — Integration platform export (MuleSoft), Manual discovery workshop (2024-Q2), Network traffic analysis, AI-assisted discovery (Claude, 2026-05-15) Notes — When AI-generated, document: “AI Agent (Claude, 2026-05-15) — validated by [name].” |
| AI-Generated | Walk | Description — Indicates whether this record was initially generated by an AI agent rather than manually authored. Benefit(s) — Maintains transparency about record provenance. Enables targeted validation of AI-generated records before they are considered authoritative. Source — Manual. Examples — Yes (validated), Yes (pending validation), No |
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers