About Jiandong Pei
I am a SAP BTP and Enterprise AI architect focused on boundary judgment: whether extensions, Clean Core architectures, workflows, and agents are structurally safe to evolve.
My credibility comes from builder-side SAP platform experience and years of seeing where locally correct systems fail after go-live, rollout, security hardening, or lifecycle change.
SAP builder-side background
- Former SAP engineer with 13+ years inside SAP.
- Worked across SAP Build Code / Joule early integration and AI-assisted extension generation context.
- Experience with CAP / LCAP, SaaS enablement, XSUAA, AppRouter, Work Zone, HDI, multitenancy, and S/4HANA extension architecture.
- BTP security, identity chain debugging, service broker, HANA XSA, streaming analytics, and Cloud Foundry / XSA experience.
- Cross-product architecture troubleshooting where local correctness did not produce global architectural validity.
- SAP Labs China MD Award and public SAP ecosystem evidence available through LinkedIn Featured items.
Public / Verifiable Signals
These are the kinds of external signals that support the builder-side and architecture judgment claims. Some artifacts are currently easiest to inspect through LinkedIn Featured items.
SAP recognition
- SAP Labs China MD Award.
- Builder-side SAP product and platform experience across Build Code / Joule-era work.
SAP ecosystem artifacts
- SAP Community and public writing related to SAP BTP, CAP, Clean Core, extensions, and architecture boundaries.
- SAP Devtoberfest / SAP Learning Journey or related SAP ecosystem materials where publicly featured.
Current public work
- Boundary Model essays published on this site.
- LinkedIn Featured artifacts, award images, and public evidence.
Why the Boundary Model exists
SAP BTP projects often appear correct when tested locally. The real failure appears when the system has to operate through governed entry paths, multiple tenants, identity propagation, S/4HANA integration, data ownership, security hardening, and versioned lifecycle change.
The Boundary Model is my diagnostic framework for deciding whether those contracts still hold.
Areas of judgment
SAP BTP architecture
CAP / LCAP, XSUAA, AppRouter, Work Zone, HDI, multitenancy, SaaS enablement, S/4HANA extensions, Clean Core, identity, integration, and lifecycle boundaries.
Enterprise AI architecture
SAP Build Code / Joule context, agent responsibility, workflow handoff, execution safety, authorization, context, RAG/tool boundaries, and contract-bound generation.
Independent verdict work
Strategic Boundary Verdict, Full Boundary Audit, Agent-Extension Responsibility Review, and recurring Architecture Verdict Authority for high-risk decisions.
Current work
I provide independent architecture judgment for SAP BTP extension landscapes and enterprise AI initiatives where teams need to decide what belongs where before execution, rollout, or lifecycle change becomes expensive.
- I classify boundary, jurisdiction, and responsibility failures.
- I issue fixed-scope written reviews and verdicts.
- I help teams identify whether the current architecture deserves to proceed, needs redesign, or needs a narrower implementation fix.
- I write and publish openly on SAP BTP, Clean Core, S/4HANA extensibility, AI agents, workflows, CAP, multitenancy, and long-term architecture boundaries.
Boundaries of the work
- I am not SAP official support.
- I do not speak for SAP.
- I do not sell implementation staffing.
- I do not claim every BTP or AI issue is architectural.
- I do not replace customer or vendor execution responsibility.