Jiandong Pei
SAP BTP & Enterprise AI Architect
Former SAP Build Code / Joule builder-side engineer. I help teams judge whether SAP BTP extensions, Clean Core architectures, and enterprise AI agents are structurally safe to evolve.
My work focuses on identity, tenant, data, integration, runtime, lifecycle, and execution boundaries - the places where enterprise systems usually fail after they appear to work.
When Architecture Looks Correct - Until It Has to Evolve
Postman works, Work Zone fails
The direct call succeeds, but the governed entry path exposes identity, routing, or integration assumptions.
One tenant works, the next tenant breaks
The first rollout hides a missing tenant model. The next tenant exposes the real architecture.
S/4 data becomes shadow truth
Data copied into HDI looks useful until ownership, write authority, and lifecycle drift from the system of record.
Clean Core is approved, responsibility is not
RISE and Clean Core set direction, but extension responsibility, identity, and lifecycle remain unsettled.
An agent can execute, but safety is unproven
A successful AI demo does not prove truth, context, authorization, execution, and accountability boundaries.
The system runs, but cannot move from N to N+1
Operations survive through expert intervention, not through a reconstructible lifecycle model.
Boundary Model
The Boundary Model is a diagnostic framework for judging whether an SAP BTP extension or enterprise AI agent is structurally safe to evolve.
Identity Boundary
Judge the contract that must hold after local success, production rollout, tenant variation, security hardening, and future change.
Tenant Boundary
Judge the contract that must hold after local success, production rollout, tenant variation, security hardening, and future change.
Data Boundary
Judge the contract that must hold after local success, production rollout, tenant variation, security hardening, and future change.
Integration Boundary
Judge the contract that must hold after local success, production rollout, tenant variation, security hardening, and future change.
Runtime Boundary
Judge the contract that must hold after local success, production rollout, tenant variation, security hardening, and future change.
Lifecycle Boundary
Judge the contract that must hold after local success, production rollout, tenant variation, security hardening, and future change.
Execution Boundary
Judge the contract that must hold after local success, production rollout, tenant variation, security hardening, and future change.
Services
Strategic Boundary Verdict
For decisions where implementation keeps moving but architecture cannot converge. Produces a focused verdict on P1 structural risk and direction.
See service ->Full Boundary Audit
For complex SAP BTP landscapes that must survive tenant, identity, data, integration, runtime, and lifecycle evolution.
See service ->Agent-Extension Responsibility Review
For SAP Joule, enterprise agents, workflows, and extension responsibility ambiguity before AI execution becomes ungovernable.
See service ->Built from SAP Builder-Side Experience
The Boundary Model comes from real platform engineering exposure, not generic advisory language.
SAP platform and extension work
Former SAP engineer with 13+ years inside SAP, including SAP Build Code / Joule-era platform work, CAP / LCAP, SaaS enablement, XSUAA, AppRouter, Work Zone, multitenancy, and S/4HANA extension architecture.
Security, lifecycle, and service broker depth
Experience across BTP security, HANA XSA service broker, streaming analytics, lifecycle issues, integration boundaries, and cross-product architecture troubleshooting.
Architecture judgment across teams
This capability can support a program externally through fixed-scope verdicts, or internally where architecture, platform, or AI teams need long-term SAP BTP boundary judgment.
Read by Case, Boundary, or Situation
The article library is organized around the situations where local success stops proving architectural validity.
Send a one-page architecture summary
The first useful step is not a meeting. It is a clear description of the decision that cannot converge.