Research agenda

Questions worth testing, not slogans worth repeating.

Each theme separates the problem, architecture position, evidence or hypothesis, status and next intended output.

01
Under research

Governed SAP AI agents

AI-generated explanations can appear credible without sufficient SAP evidence or control.

Why it matters
Enterprise decisions need traceable evidence, policy boundaries and accountable review.
Next output
Publish a reusable trust and execution reference model.
Open theme
02
Under research

Agent execution traceability

Users cannot trust an agent when they cannot see what it is doing, waiting for or failing on.

Why it matters
Live trace improves diagnosis, governance and user confidence.
Next output
Define a vendor-neutral trace schema.
Open theme
03
Under development

Prompt drift and traceability

Prompts change over time while outputs and decisions are compared as if the instruction remained stable.

Why it matters
Uncontrolled drift weakens reproducibility and auditability.
Next output
Create a prompt-governance control model.
Open theme
04
Under research

Performance architecture and thin loading

Enterprise applications often load heavy optional capabilities before they are needed.

Why it matters
Slow startup and repeated calls reduce trust and operational usability.
Next output
Publish a thin-loading and telemetry pattern catalogue.
Open theme
05
Under research

MCP and ABAP Cloud wrappers

Cloud and on-premise SAP evidence must be exposed safely to agent tools without bypassing platform controls.

Why it matters
Stable tools and wrappers reduce coupling between AI systems and SAP implementations.
Next output
Document a secure wrapper and tool-registration blueprint.
Open theme
06
Under research

Responsible autonomy

Autonomous write-back can outpace evidence, policy and organisational accountability.

Why it matters
Enterprise AI must preserve segregation of duties and human ownership.
Next output
Define autonomy levels and promotion gates.
Open theme
07
Under development

LLM orchestration, RAG and vector databases

Enterprise AI designs can add retrieval and orchestration layers before proving that approved evidence, access boundaries and operational value justify them.

Why it matters
Architecture must separate useful grounding from unnecessary complexity, cost and data exposure.
Next output
Publish a decision framework for when deterministic search, RAG or vector retrieval is appropriate.
Open theme
08
Under development

Telemetry beyond LLM calls

Agent observability is often reduced to token and model latency while user, UI, API, database, connector and policy failures remain invisible.

Why it matters
Operational reliability requires a complete transaction trace from login to logout and from user intent to evidence and outcome.
Next output
Define a lightweight cross-layer telemetry schema and release comparison model.
Open theme
09
Under research

Human-in-the-loop operating controls

A generic approval button does not define who is accountable, what evidence is reviewed or how a decision is reversed.

Why it matters
Enterprise control requires clear decision rights, segregation of duties, evidence and rollback.
Next output
Publish reusable control patterns for advisory, approval and controlled-action agents.
Open theme
10
Under research

Enterprise agent control planes

Independent agents can fragment identity, policy, evidence, model configuration, release control and operations.

Why it matters
Enterprise adoption needs consistent governance without forcing every capability into one monolith.
Next output
Publish the boundary between agent workplace, execution plane and engineering control plane.
Open theme