Skip to main content
Layer researchSystems of record

Core systems of record

By Murali SidLinkedInPublished

Status: complete (published 2026-08-19). Scope finalized at Batch C kickoff with maintainer POV; see findings.md and sources.md.

Scope inventory (v0)

  • Estate: ERP, CRM, HRIS, ITSM, finance, procurement, billing/CPQ; the authority boundary (business authority stays with the system of record)
  • Embedded agents: per-suite agent SKUs and ecosystems (Agentforce, Joule, Copilot in Dynamics, Oracle and Workday agents), their pricing and metering, data-gravity implications
  • External agents: acting through governed APIs, write-access and approval-gate patterns, multi-suite orchestration when one task spans SAP, Salesforce, and ServiceNow
  • Readiness: API maturity per suite, extension and low-code platforms meeting agents, master data quality as a precondition

Challenged-default candidates

Embedded suite agents vs independent agents through APIs; per-suite agent ecosystems vs one cross-suite platform. Each track proposes its final list at kickoff.

Files

findings.md and sources.md carry this track's research. The scoping brief and the vendor map were archived on 2026-08-23 (see archive/, decision D038).

Cite this page

Written by Murali Sid, Founder and AI Systems Architect, last updated 18 September 2026. Licensed CC BY-SA 4.0, so quote it freely with attribution.

Murali Sid (2026). Core systems of record. Agentic Architecture Skills. https://www.agenticarchitectureskills.com/library/layers/r04-systems-of-record

Machine-readable version of this page: /library/layers/r04-systems-of-record.md

On this page