Architecture Intake Template

Use this template

Keep it factual and compressed. The goal is not to prove your team is right. The goal is to make the architecture legible enough to assess whether a fixed-scope verdict format applies.

Landscape

List the relevant S/4 systems, BTP runtimes, entry surfaces, identity chain, and tenant model. Only include what materially shapes runtime truth.

Business action or extension scenario

Describe what the user, assistant, agent, workflow, extension, or core system is expected to do.

Current symptom

State what works, what fails, where it fails, and which tenant, path, user group, workflow state, or agent behavior exposes the difference.

Timeline

Include go-live date, relevant rollout or hardening milestones, and the moment the divergence became visible.

Decision that cannot converge

Describe the decision itself, the competing interpretations, and the business consequence of delay. This is usually more important than the incident chronology.

Known constraints

Add only the constraints that materially bound the verdict: release windows, compliance posture, clean core restrictions, contractual boundaries, or pre-committed rollout obligations.

What not to include

Do not attach every log, ticket, or meeting note. Do not turn the intake into a defense brief. The first pass is for classification, not exhaustive evidence handling.

Copyable template

Subject: SAP BTP Boundary Review Request - [Company / Situation]

1. Landscape:
2. Business action or extension scenario:
3. Current symptom:
4. Systems involved:
5. Identity / tenant / data / integration / lifecycle surfaces involved:
6. Timeline:
7. Teams or stakeholders involved:
8. Decision that cannot converge:
9. Desired next step: