Search across Architecture IntelligenceTry engineering explorations, SAP Clean Core, evidence, integration or AI governance.
Publications

Architecture thinking with stable provenance.

Research papers, website-native publications and LinkedIn articles are listed once each, with their source of record and boundaries available on demand.

Research portfolio: 3 current framework papers across ACLA, EAF and MCR. Historical MCR R1.9 remains lineage under the current MCR paper.

Publication archive

Find by title or topic.

32 publications shown

03 publications

Research papers and preprints

Current ACLA, EAF and MCR papers, with methods and limits at the source of record.

Research preprint

From Agent Intent to Verifiable Mission Outcomes: Mission Capability Runtime 4.0

Studies authority-bounded enterprise-agent execution and evidence-backed mission outcomes in a synthetic Class A research setting.

Read paper →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: Zenodo · Original source: Zenodo

Studies authority-bounded enterprise-agent execution and evidence-backed mission outcomes in a synthetic Class A research setting.

MCREnterprise AIMission CapabilityResearchBounded synthetic researchPreprint

Public-review preprint, not peer reviewed or production proof. Historical MCR R1.9 is separate lineage with unresolved live CREATE commit state. The unchanged reviewer suite was 38/40 with raw runner exit 1; later reconciliation reached 40/40 without rewriting that result. Live integration, SAP business outcomes and generalized exactly-once execution are not established.

DOI: 10.5281/zenodo.23696240Research repositoryVersioned releaseHistorical lineage
Research preprint

Enterprise Agent Framework (EAF): Minimum Authoritative Working Sets and Closed-Loop Outcome Assurance for Enterprise AI Agents

Studies minimum authoritative working sets and closed-loop outcome assurance for enterprise AI agents.

Read paper →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: Zenodo · Original source: Zenodo

Studies minimum authoritative working sets and closed-loop outcome assurance for enterprise AI agents.

EAFEnterprise AIAgent GovernanceResearchBounded researchPreprint

Public research preprint and reproducibility artifact, not journal or conference peer review. Negative and null findings remain preserved; Integrated assurance safety remains not established.

DOI: 10.5281/zenodo.22193673Research repositoryVersioned release
Research artifact

From Persistent Memory to Mission Working Sets: An Authority-Aware Context Lifecycle Architecture for Agentic AI

Presents an authority-aware context lifecycle and mission working-set architecture with public reproducibility evidence.

Read paper →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: Zenodo · Original source: Zenodo

Presents an authority-aware context lifecycle and mission working-set architecture with public reproducibility evidence.

ACLAContext EngineeringEnterprise AIResearchBounded researchResearch artifact

Version 1.1.0 preserves a held-out 28/29 result and a falsified strongest-authority assumption. It does not establish independent human validation. The earlier DOI is historical v1.0.0 lineage, not the preferred current citation.

DOI: 10.5281/zenodo.22155728Research repositoryVersioned releaseHistorical lineage
14 publications

Architecture publications

Website-native and longer-form architecture writing.

LinkedIn article

From MCP Tools to a SAP Full-Stack Engineering Pipeline

Connects MCP tooling into a broader SAP full-stack engineering pipeline spanning ADT, Fiori, UI5 and governed delivery controls.

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Connects MCP tooling into a broader SAP full-stack engineering pipeline spanning ADT, Fiori, UI5 and governed delivery controls.

MCPSAP Full-Stack EngineeringFioriPublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

Engineering Token Governance for Agentic AI in SAP Development

Frames token, context and tool governance as engineering controls for agentic AI applied to SAP development work.

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Frames token, context and tool governance as engineering controls for agentic AI applied to SAP development work.

Agentic AISAP DevelopmentToken GovernancePublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

The Evolving SAP Development Architect: From SAP Automation to AI Engineering

Frames the SAP development architect role as moving beyond automation scripts into evidence-aware AI engineering, with stronger…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Frames the SAP development architect role as moving beyond automation scripts into evidence-aware AI engineering, with stronger attention to governance, execution boundaries, validation and accountable architecture decisions.

SAP ArchitectureAI EngineeringSAP AutomationEnterprise AIArchitecture GovernancePublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

ABAP4CLayer – Architecture Option 1 : 25 Hands-on Lessons from AI-Assisted SAP Code Generation and Automation

Captures hands-on lessons from ABAP4CLayer experimentation, separating generated code, transport reachability, runtime…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Captures hands-on lessons from ABAP4CLayer experimentation, separating generated code, transport reachability, runtime validation, evidence receipts and human-controlled execution boundaries.

ABAP4CLayerSAP AutomationAI-Assisted EngineeringABAP CloudExecution ControlsPublic safe evidence

Public LinkedIn article; the original source remains the destination.

Architecture comparison publication

Two ABAP4C Cloud Deployment Pipelines: Same SAP Outcome, Different Execution Architecture

A comparison of two ABAP4C Cloud Deployment Pipeline architectures: Standard ADT MCP and Capella Governed Bridge.

Read →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: Architected by Prasad™ · Original source: Architected by Prasad™

A comparison of two ABAP4C Cloud Deployment Pipeline architectures: Standard ADT MCP and Capella Governed Bridge.

ABAP4CABAP CloudEclipse ADTMCPCapellaArchitecture Comparison

Architecture-level comparison with bounded evidence claims

LinkedIn article

ABAP4C – Architecture Option 1

Introduces the first ABAP4C architecture option as a standards-led route through coding-agent orchestration, Eclipse ADT MCP…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Introduces the first ABAP4C architecture option as a standards-led route through coding-agent orchestration, Eclipse ADT MCP tooling and SAP ADT execution while preserving proof boundaries.

ABAP4CABAP CloudADT MCPSAP ArchitectureEvidence-Led DeliveryPublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

From Requirement to an Active SAP CDS View: What I Learned by Connecting Cline, Eclipse ADT and SAP ADT MCP

Documents a bounded SAP engineering experiment that connected Cline, Eclipse ADT and SAP ADT MCP from a requirement toward an…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Documents a bounded SAP engineering experiment that connected Cline, Eclipse ADT and SAP ADT MCP from a requirement toward an active CDS view, emphasizing evidence, constraints and validation limits.

SAP CDSClineEclipse ADTSAP ADT MCPABAP CloudPublic safe evidence

Public LinkedIn article; the original source remains the destination.

Architecture publication

I Didn’t Set Out to Build a Website. I Built an AI-Assisted Architecture Lab.

What began as a personal website evolved into a living architecture lab spanning AI-assisted engineering, GitHub governance,…

Read →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: Architected by Prasad™ · Original source: LinkedIn

Original: 2026-07-10 · Website: 2026-07-11

What began as a personal website evolved into a living architecture lab spanning AI-assisted engineering, GitHub governance, Cloudflare deployment, automated validation, security, portability, and human-controlled production decisions.

Enterprise ArchitectureAI-Assisted EngineeringSAPCloud ArchitectureGitHub GovernanceCloudflareArchitecture Governance

Independent professional publication

Watch related video
Architecture publication

How Do You Know Your AI Tester Is Actually Testing? — Designing the SAP Testing MCP Server

This publication presents an SAP Testing MCP Server built around a technology-specific Adapter Framework and a Seeded-Defect…

Read →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: Architected by Prasad™ · Original source: Architected by Prasad™

This publication presents an SAP Testing MCP Server built around a technology-specific Adapter Framework and a Seeded-Defect Discrimination Framework to create a measurable, evidence-driven quality gate.

SAPMCPSAP TestingAI-assisted TestingTest AutomationSoftware QualityAdapter FrameworkSeeded-Defect Testing

Independent professional publication

LinkedIn article

Beyond the Prompt: Building a Governed AI Operating Layer for SAP

Explores why SAP AI needs an operating layer for controlled evidence, explainable reasoning, role separation, telemetry and…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Explores why SAP AI needs an operating layer for controlled evidence, explainable reasoning, role separation, telemetry and accountable execution rather than prompt engineering alone.

SAP AIGovernanceAgent operating model

Public LinkedIn article; full-text republication is not included.

Watch related video
LinkedIn article

AI Vs SAP Part 4: Vibe Coding in SAP — An Architect’s Technical POC View

Assesses vibe coding for SAP through a practical architecture POC, including where rapid generation helps and where SAP context,…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Assesses vibe coding for SAP through a practical architecture POC, including where rapid generation helps and where SAP context, validation and engineering controls remain essential.

Vibe codingSAP architecturePOC

Public LinkedIn article; full-text republication is not included.

Open supporting postWatch related video
LinkedIn article

AI Vs SAP – Part 3: The “Eureka” Moment — Making an ABAP Trial System Consumable by a Custom SAP AI Agent

Documents a practical integration breakthrough that made ABAP Trial RAP and OData capabilities consumable by custom AI agents…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Documents a practical integration breakthrough that made ABAP Trial RAP and OData capabilities consumable by custom AI agents while preserving a controlled SAP boundary.

ABAP CloudAI agentsIntegration

Public LinkedIn article; full-text republication is not included.

Open supporting postWatch related video
LinkedIn article

AI vs SAP – Part 2: AI Understands What Happened. SAP Experts Understand Why.

Compares AI-generated technical interpretation with the process, configuration and operational context SAP experts use to explain…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Compares AI-generated technical interpretation with the process, configuration and operational context SAP experts use to explain why an issue occurred.

SAP expertiseAI reasoningRCA

Public LinkedIn article; full-text republication is not included.

Watch related video
LinkedIn article

After Months of Testing Every Major AI Against Real SAP Work — 8 Honest Observations

Summarises practical observations from testing major AI models against real SAP architecture, development and diagnostic…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Summarises practical observations from testing major AI models against real SAP architecture, development and diagnostic scenarios, including the limits of generic reasoning.

SAPAI modelsField observations

Public LinkedIn article; full-text republication is not included.

Watch related video
13 publications

CAPELLA series

The published Agentic Full-Stack Engineering Platform for SAP series.

LinkedIn article

Part 13/16 - CAPELLA AFEP :- Grounding Before Reasoning

Examines why SAP reasoning in an agentic engineering platform must be grounded in target-bound, provenance-aware evidence before…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Examines why SAP reasoning in an agentic engineering platform must be grounded in target-bound, provenance-aware evidence before mutation or authorization decisions are made.

CAPELLA AFEPSAP GroundingEnterprise AIPublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

Part 12/16 - CAPELLA AFEP :- Observability

Frames observability as the ability to reconstruct why CAPELLA believes what it believes across requests, approvals, executions,…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Frames observability as the ability to reconstruct why CAPELLA believes what it believes across requests, approvals, executions, SAP evidence and operator-facing states.

CAPELLA AFEPObservabilityEvidencePublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

Part 11/16 - CAPELLA AFEP :- Execution Is Not Proof

Separates successful execution from proof of final SAP outcome, emphasizing independent readback, deployment evidence and runtime…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Separates successful execution from proof of final SAP outcome, emphasizing independent readback, deployment evidence and runtime validation boundaries.

CAPELLA AFEPSAP EvidenceExecutionPublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

Part 10/16 - CAPELLA AFEP :- Blocked by Design

Explains why a stopped CAPELLA execution can be a correct architectural control only when authority, SAP engagement, retry safety…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Explains why a stopped CAPELLA execution can be a correct architectural control only when authority, SAP engagement, retry safety and unknown outcomes remain explicit.

CAPELLA AFEPBlocked by DesignSAP GovernancePublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

Part 09/16 - CAPELLA AFEP :- Human Approval Is Part of Architecture

Shows human approval as a bounded engineering authorization over frozen CAPELLA content rather than a generic human-in-the-loop…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Shows human approval as a bounded engineering authorization over frozen CAPELLA content rather than a generic human-in-the-loop gesture.

CAPELLA AFEPHuman ApprovalAI GovernancePublic safe evidence

Public LinkedIn article; the original source remains the destination.

Open supporting post
LinkedIn article

Part 08/16 - CAPELLA AFEP :- Where n8n Fits

Positions n8n as workflow coordination around CAPELLA rather than the engineering authority for SAP mutations or approval…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Positions n8n as workflow coordination around CAPELLA rather than the engineering authority for SAP mutations or approval decisions.

CAPELLA AFEPn8nWorkflow GovernancePublic safe evidence

Public LinkedIn article; the original source remains the destination.

Open supporting post
LinkedIn article

Part 07/16 - CAPELLA AFEP :- MCP Gives Capabilities, Not Authority

Explains why MCP exposes SAP engineering capability but does not itself grant permission, execution authority or proof of SAP…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Explains why MCP exposes SAP engineering capability but does not itself grant permission, execution authority or proof of SAP state change.

CAPELLA AFEPMCPSAP AuthorityPublic safe evidence

Public LinkedIn article; the original source remains the destination.

Open supporting post
LinkedIn article

Part 06/16 - CAPELLA AFEP :- Authority Matters More Than Agent Intelligence

Explains why AI capability, permission and execution authority must remain separate in SAP engineering, using CAPELLA AFEP to…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Explains why AI capability, permission and execution authority must remain separate in SAP engineering, using CAPELLA AFEP to show bounded authorization, SAP-side authority and read-only evidence limits.

CAPELLA AFEPSAP AuthorityAI AgentsPublic safe evidence

Public LinkedIn article; the original source remains the destination.

Open supporting post
LinkedIn article

Part 05/16 - CAPELLA AFEP :- Generation Is Not Activation, Deployment, or Execution

Explains why AI generation is not equivalent to SAP activation, deployment or execution, and why enterprise delivery needs…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Explains why AI generation is not equivalent to SAP activation, deployment or execution, and why enterprise delivery needs governed lifecycle evidence.

CAPELLA AFEPSAP EngineeringExecution EvidencePublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

Part 04/16 - CAPELLA AFEP :- AI Can Understand Intent. Enterprise Systems Still Need a Contract.

Positions ERCC as the governed contract between AI-understood intent and enterprise-safe SAP engineering execution.

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Positions ERCC as the governed contract between AI-understood intent and enterprise-safe SAP engineering execution.

CAPELLA AFEPERCCSAP ArchitecturePublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

Part 03/16 - CAPELLA AFEP :- Why I Put a Compiler Between AI and SAP

Describes the role of a semantic compiler in separating AI intent from deterministic SAP qualification and delivery controls.

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Describes the role of a semantic compiler in separating AI intent from deterministic SAP qualification and delivery controls.

CAPELLA AFEPSemantic CompilerSAP QualificationPublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

CAPELLA AFEP — Part 02/16 Inside the CAPELLA Engineering UX

Explains the CAPELLA engineering UX model through visible state, source authority, evidence and operator decision points.

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Explains the CAPELLA engineering UX model through visible state, source authority, evidence and operator decision points.

CAPELLA AFEPEngineering UXEvidencePublic safe evidence

Public LinkedIn article; the original source remains the destination.

LinkedIn article

CAPELLA AFEP | PART 01/16 - From AI Intent to SAP RAP Engineering

Introduces CAPELLA AFEP as a governed path from AI intent to SAP RAP engineering with explicit source authority and evidence…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

Introduces CAPELLA AFEP as a governed path from AI intent to SAP RAP engineering with explicit source authority and evidence boundaries.

CAPELLA AFEPSAP RAPAgentic AIPublic safe evidence

Public LinkedIn article; the original source remains the destination.

02 publications

Other external publications

Short-form field observations and public posts.

LinkedIn post

I Started by Building SAP Custom AI Agents. I Ended Up Designing an Operating Layer.

A hands-on reflection on moving from individual SAP AI use cases toward a governed operating layer with evidence control,…

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

A hands-on reflection on moving from individual SAP AI use cases toward a governed operating layer with evidence control, explainability, role separation, traceability and human authority.

SAP AIEnterprise AIAgentic AIAgent governance

Public LinkedIn post; the original source remains the destination.

Watch related video
LinkedIn post

From Information Retrieval to Decision-Ready Evidence — The SAP Evidence Enrichment Layer

An architecture field observation exploring the layer between enterprise retrieval and LLM reasoning.

Read external →
Evidence & provenance →

Publication status: Published

By Prasad Deshpande · Source of record: LinkedIn · Original source: LinkedIn

An architecture field observation exploring the layer between enterprise retrieval and LLM reasoning. It examines how SAP evidence can be evaluated for freshness, completeness, object-version consistency, dependency coverage, authority and contradiction before being admitted into AI reasoning. Runtime figures in the original observation are local framework measurements, not complete end-to-end SAP agent latency.

SAP AIEnterprise AIEvidence EnrichmentMCPRAGLLMSAP ArchitectureAI GovernanceGrounding

Public LinkedIn field observation; the original source remains the destination.

How publications are governed →
Publication and research operating modelControlled creation, review, validation, source-of-record publication and distribution.
01Website-native draft
02Author review
03Quality validation
04Approved publication
05Website source of record
06LinkedIn introduction
Approved answers and grounded AI

Ask the Architecture Lab

Ask a non-confidential question. Approved knowledge answers work directly; optional language enhancement uses approved website context only.

Open the assistant to load approved knowledge.

Suggested for this page

Select a suggested question or ask your own.

Boundary: Responses use approved public website content only, remain advisory and never access live SAP systems or private environments.