Solution Blueprint · 2026

One request, coordinated systems

AI-native
Intelligent travelSolution

Powered by the BoltFusion agent runtime, this solution connects travel requests, bookings, pre-trip services, expense claims, and reconciliation. Key write operations require human confirmation, and every result is traceable and can be read back.

One enterprise entry point Two key confirmations End-to-end status verificationThird-party capabilities are simulated
Executive Brief

Turn multi-system business travel into one controlled workflow

The solution first unifies the entry point and runtime contract, then gradually replaces connectors with live integrations. The demo uses no customer data and does not present simulated results as production capabilities.

Solution north star

Employees only need to express their intent and confirm key actions; the system handles lookup, data entry, execution, tracking, and verification.

SExpress needsQRead contextFGenerate business dataRExecute controlled actions✓Read back results

One entry point

Start a unified conversation through the enterprise portal, workflow page, or mobile app—no need to understand the systems behind it.

One contract

Create runs, poll status, and read business results using the standard BoltFusion Agent API paths.

Two Connection Types

Internal systems use production adapters; ticketing, hotels, weather, and other services are demonstrated first with replaceable mock adapters.

Three Guardrails

Authentication, permissions, and human confirmation jointly protect real writes. Monitor is for observation and diagnostics only.

Read-only discovery by defaultExplicit authorization before writesHTTP 202 does not mean successVerify acceptance by reading back the business result
Journey Map

Five stages, one continuous business context

Each stage can be integrated independently or share the same run, trace, and business identity. Resume from interruption points and route exceptions to a human.

0102030405
01

Travel Request

Say it once. The request is created automatically.

  • Recognizes destinations and dates from natural language
  • Reads employee details and travel policies
  • Generates workflow fields and submits for approval
BoltFusion + Workflow Platform
02

Smart Booking

Recommend first, confirm before booking

  • Searches flights and hotels in parallel
  • Ranks by policy, distance, and preferences
  • Books after your confirmation
Simulated flight and hotel services
03

Pre-Trip Services

Proactive alerts for important changes

  • Weather and itinerary reminders
  • Coordinates access control, meal cards, and parking
  • Records change events in the activity log
Internal systems + simulated services
04

Expense Reconciliation

Automated receipt collection

  • Combines orders, invoices, and itineraries
  • Checks amounts against expense limits
  • Creates an expense report draft for review
Financial system + simulated receipt verification
05

Reconciliation Loop

Searchable results, traceable exceptions

  • Intelligently matches supplier invoices
  • Routes exceptions for manual review
  • Builds an operational evidence trail and analytics dimensions
Financial system + Agent Monitor
Human actionExpress needs+Confirm booking+Approve expense claim
System actionRemaining steps proceed automatically according to policySolution objective; does not represent existing production data
Runtime Architecture

One runtime, with clear boundaries between business execution and observation

External calls enter only through the Agent API; Work stays internal; Monitor provides pages, logs, records, and diagnostics.

Experience Layer
Enterprise AI PortalChat / Page Agent
E9 / E10 Workflow PageForms / Tasks / Business Context
Mobile Entry PointMessages / Confirmations / Reminders
Controlled Request
BoltFusion Agent Runtime
Travel Orchestration AgentSolution Role
Agent APIBusiness Entry · 8786POST /api/agents/{agentKey}/runs
WorkInternal Execution · 8787Policies · Tools · Browser Tasks
MonitorObservation & Diagnostics · 8788Records · Logs · Replay
Identity & PermissionsIdempotency & RetriesHuman Confirmation GateResult Evidence
Connector Calls
Systems & Services Layer
Enterprise SystemWorkflow / Finance / Organization / Campus
Third-Party SimulationTicketing / Hotels / Weather / Invoices
Data & KnowledgePolicies / Profiles / Rules / Analytics
Business Requests: Agent APIInternal Execution: WorkObservation & Diagnostics: MonitorThird Parties: Simulation Provider
bf.derived-agent.api.v1

Interfaces follow the BoltFusion runtime contract

Run creation and status queries go through the business entry point. Monitor does not accept business write requests and is not the final authority on success.

1

Create a run

POST …/agent-api/api/agents/{agentKey}/runs

Include a stable idempotency key and business input. An immediate response means only that the request was accepted.

2

Poll the same run

GET …/agent-api/api/agents/{agentKey}/runs/{runId}

Handle statuses such as queued, running, waiting_input, succeeded, and failed.

3

Determine success from business evidence

succeeded + requestId + workerStage

A page toast, HTTP 200/202, or visibility in Monitor alone is not proof of success.

Write Boundary: Actions such as bookings, submissions, and authorizations pass through a policy gate. Demos use a simulated provider by default and do not call real third parties.

DEMO
POST /api/boltfusion/interface/agentProxy/agent-api
  /api/agents/agent.ecology.e9.workflow.request.create/runs

X-Idempotency-Key: travel-demo-20260729-001
Content-Type: application/json; charset=utf-8

{
  "input": {
    "workflowName": "Travel request",
    "prompt": "Visit a regional center for a three-day project visit",
    "formFields": { "destination": "A regional center" }
  },
  "trace": true,
  "metadata": {
    "clientRequestId": "travel-demo-20260729-001",
    "providerMode": "simulated"
  }
}
Accepted asynchronously; wait for the runId status to advance
Business Entry/agentProxy/agent-apiMonitoring Entry/agentProxy/agent-monitorAuthenticationBearer Token / X-BoltFusion-Agent-TokenIdempotencyX-Idempotency-Key
Connector Ecosystem

Connect enterprise systems for production; simulate third parties first, then replace them

Connectors isolate vendor differences, so upper-level orchestration stays vendor-agnostic. Switching from Mock to a live service preserves the same business semantics.

Internal SystemsPRIVATE
E9 / E10 workflowRequests, approvals, and reimbursements
Organization and peopleIdentity, departments, and job levels
Finance and budgetsStandards, accounts, and reconciliation
Access control and campusVisitors, access, and parking
Message centerTasks, reminders, and acknowledgments
Data platformProfiles, preferences, and analytics
BoltFusionConnector Hub

Unified Authentication · Semantic Mapping
Policy Checks · Runtime Evidence

Third-Party ServicesSIMULATED
Aggregated ticketing serviceFlight / high-speed rail search and booking
Hotel booking servicePolicy-compliant hotel recommendations
Weather serviceForecasts and risk alerts
E-invoicing serviceVerification, duplicate checks, and consolidation
Map distance serviceFactory / hotel commute estimates
Supplier invoicesOrder and invoice matching
Unified Call Semantics travel.search → travel.quote → approval.confirm → travel.book↔Adapter Pattern providerMode: "simulated" | "production"
Conversation Demo

See how employees interact with an AI assistant

Does not connect to live business systems
RUN / TRAVEL-DEMO-0729
AI ONLINEA
▶

Start with a sentence

After you press play, the employee and AI clarify the request, options, and confirmation together.

The demo environment cannot send real requests
Acceptance Metrics

How to Evaluate This Solution

Define the checks and pass criteria first. After launch, use data from real workflows to see whether efficiency improves.

01Entry Point Switch

Back-and-Forth Across Multiple SystemsA Single Conversation Entry Point

Users no longer need to find each system manually, while clear boundaries remain in the backend.

02Write Controls

Automatic Means SubmittedConfirmation for Critical Actions

Search and analysis can be automated; bookings, submissions, and permission changes must pass policy checks.

03Success Criteria

API Response OnlyBusiness Result Readback

Each run is associated with a runId, traceId, requestId, and workerStage.

04Service Provider Replacement

Upper Layers Bound to VendorAdapters Are Replaceable

Mock and production implementations share a semantic contract, so switching does not change upper-level orchestration.

100%

Critical Write Operations Are AuditableAcceptance Criteria

0

Direct Connection from External Systems to WorkArchitectural Guardrails

1:1

Link business requests to evidenceTraceable goals

Graceful degradation

Escalate to a human when a third party is unavailableResilience requirements

Delivery Roadmap

From demo-ready to integration-ready,
then to acceptance-ready.

Freeze business semantics and interface contracts first, then connect enterprise systems. Use third-party mock adapters throughout integration testing, replacing them one by one once providers and authorizations are confirmed.

P0

Contract Confirmation

Process scope, fields, identities, permissions, success criteria

Deliverables: interface inventory + acceptance matrix
P1

Scenario Integration

Agent API, workflow platform, organizational finance, third-party mocks

Deliverables: runnable end-to-end flow + Monitor evidence
P2

Production Replacement

Production adapters for ticketing, hotels, weather, invoices, and more

Deliverables: integration test report + degradation plan
P3

UAT & Operations

Real-role validation, performance baselines, exception replay, metrics governance

Deliverables: business sign-off + operations dashboard
BoltFusionBring Agents into real business operations

This solution is a sanitized demo. People, locations, IDs, orders, provider responses, and reported outcomes shown on this page are generic examples or simulated data.