AI-native ecology · Solution Blueprint

From digital office to executable Agentic Office

AI-Native ecology
AI across every scenarioSolution

AI Agent and business digital employee solutions for Weaver e-cology 9 / 10 (E9 / E10), connecting workflows, forms, organizational permissions and knowledge bases. Public demonstrations explain the approach; capabilities require validation against versions, permissions and project configuration.

One ecology entry point Nine business scenarios Composable specialist AgentsWrite operations are always controlled
AI-native Definition

Native—not another chat box

AI is built into ecology’s business context, permissions, and execution flows. It can move from understanding to action, then bring the results back to business pages.

Solution north star

Every business page is understood, every business action is controllable, and every business outcome is provable.

Understand PeopleIdentity, Roles, and PermissionsUnderstand ContextPages, Processes, and Business ObjectsThinkBreak Down, Plan, and Select ToolsActFill Forms, Search, Collaborate, and ExecuteProvide ProofStatus, Reference Numbers, and Result Readback

Context-Native

Understand the current user, page, form, workflow step, and business object—without making users repeat what the system already knows.

Permission-Native

Inherit ecology identities, organizations, roles, and data permissions. What AI can see and do has clear boundaries.

Action-Native

Queries can run automatically; drafts can be previewed; submissions require confirmation. High-risk actions go through dedicated approval and human review gates.

Evidence-Native

Prove outcomes with business IDs, field values, workflow statuses, and execution logs—not API responses or on-screen messages.

Copilot: Assist the current userAgent: Complete a taskAgent Team: Coordinate an end-to-end workflowHuman Gate: Protect critical actions
Scenario Panorama

Nine scenarios, one shared AI foundation

Start by tiering scenarios by value and risk, then integrate them one at a time. Each scenario defines its user entry point, executable actions, human gates, and evidence of business success.

01

Process Collaboration

From “Finding a Process” to “Getting Things Done”

  • Intent Recognition and Process Recommendations
  • Form Generation and Document Validation
  • Step Tracking and Exception Explanations
02

HR Services

An On-the-Go Service Desk for the Entire Employee Journey

  • Onboarding, Transfers, and Offboarding
  • Policy Q&A and Draft Certificates
  • Recruiting and Interview Support
Success EvidenceEmployee Status / Process ID / Human Review
03

Financial Management

A Controlled Loop from Receipts to Accounting

  • Expense Report Drafts and Compliance Checks
  • Budget Tracking and Expense Allocation
  • Reconciliation Exception Explanations
Success EvidenceDocument ID / Budget Status / Exception List
04

Procurement & Supply Chain

End-to-End Flow from Requests and Bids to Fulfillment

  • Purchase Request Creation
  • Supplier Document Comparison
  • Delivery and Exception Tracking
Success EvidencePurchase Order Number / Approval Status / Fulfillment Evidence
05

Contracts & Legal

Bringing Risk Alerts into Business Operations

  • Contract Summaries and Clause Comparison
  • Risk Identification and Suggested Revisions
  • Support for Signing and Archiving Processes
Success EvidenceVersion / Risk Items / Approval and Archiving Records
06

Project Operations

Keep Plans, Tasks, and Risks Aligned

  • Project Initiation and Plan Breakdown
  • Weekly Report Summaries and Risk Identification
  • Cross-Department Task Coordination
Success EvidenceProject ID / Milestone / Task Status
07

Administrative Services

Access Frequently Used Services in One Sentence

  • Meeting and Visitor Services
  • Transportation, Travel, and Asset Coordination
  • Campus Request Tracking
Success EvidenceBooking Number / Task Confirmation / Service Status
08

Knowledge Collaboration

Answers Grounded in Policies and Source Text

  • Enterprise Knowledge Q&A
  • Policy Differences and Impact Analysis
  • Meeting Minutes and Action Item Extraction
Success EvidenceSource Citation / Version Date / Confidence Boundaries
09

Business Analytics

From Numbers to Insights and Action

  • Metric Q&A and Definitions
  • Anomaly Attribution and Drill-Down
  • Action Recommendations and Task Tracking
Success EvidenceMetric Definitions / Data As of / Closed-Loop Actions
Native Architecture

AI works within ecology, not around it

ecology remains responsible for identities, permissions, workflows, and business objects. BoltFusion handles Agent orchestration, tool execution, evidence aggregation, and runtime governance.

ONE AI ENTRYecology AI-Native Entry Point

The entry point carries business context from the page and routes each scenario to a specialized Agent. Users stay in the familiar portal, forms, and task lists.

Page AgentWorkflow AgentKnowledge AgentComposite Agent
01Unified Entry Point

ecology portal, workflow pages, mobile, messages

02Context Layer

People, Positions, Permissions, Pages, Forms, Workflows, Organization

03Agent Layer

Page Agent, Scenario Agent, Composite Agent

04Runtime Layer

Agent API, Work, Monitor, and Policy Gateway

05Connectivity Layer

ecology capabilities, enterprise systems, external services

06Evidence Layer

runId, requestId, nodes, fields, and logs

BoltFusion Agent RuntimeOBSERVABLE
Agent APIBusiness Entry · 8786Create and query the same run
WorkInternal Execution · 8787Policies · Tools · Browser
MonitorObservation & Diagnostics · 8788Status · Logs · Replay
Identity InheritanceLeast PrivilegeIdempotent RetriesManual confirmation
ecology is the source of business truthAgent API is the business entry pointMonitor is for observation and diagnostics onlySpecialized Agent source code is not copied into this solution repository
bf.derived-agent.api.v1

One Governable Contract for Every Scenario

Scenarios vary; runtime standards stay consistent. Business requests enter through the Agent API, Work stays internal, and Monitor does not accept business write requests.

1

Identify the Action Level

discover → draft → confirm → execute

By default, start with read-only discovery or drafts. Authorization requirements increase as actions get closer to affecting real business operations.

2

Create and Track the Same Run

POST /runs → GET /runs/{runId}

A stable idempotency key, business context, action mode, and human confirmation record travel with the run.

3

Validate Against Business Outcomes

succeeded + businessId + workerStage

Use fields, workflow steps, permission changes, and execution logs to distinguish “accepted” from “business completed.”

Governance Baseline: Authorize form filling, saving, submitting, approving, and permission changes separately. A page toast, HTTP 200/202, or queued status alone does not prove success.

DEMO
POST /api/boltfusion/interface/agentProxy/agent-api
  /api/agents/{agentKey}/runs

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

{
  "schemaVersion": "bf.derived-agent.api.v1",
  "input": {
    "intent": "employee_onboarding",
    "prompt": "Arrange onboarding for a new R&D employee",
    "actionMode": "confirmed_execute",
    "ecologyContext": {
      "surface": "portal",
      "organization": "R&D Department One",
      "permissionChangeAllowed": false
    }
  },
  "trace": true,
  "metadata": {
    "clientRequestId": "ecology-onboard-demo-20260729-001",
    "providerMode": "simulated"
  }
}
Request accepted. Continue polling the same runId
Business Entry/agentProxy/agent-apiMonitoring Entry/agentProxy/agent-monitorAction Modediscover / draft / confirmed_executeIdempotencyX-Idempotency-Key
Capability Ecosystem

Turn ecology capabilities into business tools Agents can call

First standardize internal capabilities as semantic tools, then connect to external enterprise systems. Scenario Agents on top remain independent of page details and vendor implementations.

ecology Core CapabilitiesNATIVE
Workflow EngineWorkflows, nodes, forms, comments
Organizational PermissionsPeople, departments, positions, roles
Portal MessagesEntry points, to-dos, reminders, acknowledgments
Document KnowledgePolicies, attachments, knowledge, versions
Business ModelingPages, entities, fields, rules
Data AnalyticsMetrics, reports, dashboards, definitions
BoltFusionAgent Capability Hub

Unified Semantics · Unified Authentication
Unified Policies · Unified Evidence

Enterprise and External SystemsADAPTER
ERP / FinanceBudgets, vouchers, settlements, and master data
HR / RecruitingCandidate, employee, and talent data
CRM / CustomersCustomers, opportunities, services, and contracts
SRM / Supply ChainSuppliers, procurement, and fulfillment
Campus / IoTAccess control, meeting rooms, vehicles, and assets
External AI ServicesModels, OCR, search, and specialized capabilities
Scenario Agent Understand intent → Select tools → Orchestrate actions → Summarize results↔Capability Adapter ecology native | configured connector | simulated provider
Cross-scenario Demo

Ten representative scenarios show how AI takes over business execution

01 / 10 · Workflow Processing
RUN / ECOLOGY-WORKFLOW-0729
AI ONLINEReq
▶

AI Leave Request Processing

Check leave balances and calendar availability, generate a leave request form, and submit it after confirmation. Then retrieve the current workflow step.

Enter a workflow request
Acceptance System

“Full-scenario coverage” is validated against a matrix, not a slogan

Prove the entry point, context, actions, permissions, exceptions, and business outcomes for each scenario. Systems not connected and actions not authorized remain clearly marked as pending.

01Scenario Coverage

One universal chat boxNine scenario categories, each individually validated

Validate at least one real role-based path per scenario category, covering inputs, outputs, human approval gates, and result readback.

02Write Safety

If it can be called, it can be executedClear authorization by action level

Populate, save, submit, approve, and change permissions each have their own policies, confirmations, and audit evidence.

03Success Evidence

Check only HTTP and promptsRead back from the actual business interface

Link each runId to its business ID, fields, nodes, and logs so failures can be located, retried, or handed off to a human.

04Continuous Governance

Once deployed, it works foreverModels and rules can be evaluated

Changes to versions, prompts, tools, knowledge, and permissions are covered by regression tests and operational metrics.

100%

Human approval gates for critical write operationsSafety Thresholds

0

External requests connect directly to WorkArchitectural Guardrails

1:1

Business actions linked to evidenceTraceability Goals

Recoverable

Resume from checkpoints after interruptionsResilience requirements

Delivery Roadmap

Start with three high-value scenarios,
then scale to AI across the business.

First map business processes and permissions, then establish the first closed loops with form filling, knowledge Q&A, and onboarding coordination. Next, expand to nine scenario categories using the same contract.

P0

Map Scenarios and Boundaries

Business objects, role permissions, action levels, success evidence

Deliverable: Scenario Map + Permission Matrix
P1

Three-Scenario Pilot

Form Filling, Knowledge Q&A, Onboarding Coordination

Deliverable: Runnable Closed Loop + Business Readback
P2

Expand to Nine Scenarios

Reuse Agent Runtime, tool contracts, and governance gates

Deliverable: Scenario Packages + Connector List
P3

Operations and Evolution

Evaluation, replay, cost, performance, permissions, and version governance

Deliverable: Operations Dashboard + Iteration Mechanism
BoltFusion × ecologyBring AI into every business operation

This solution is a sanitized demo. Sample people, organizations, IDs, tasks, system responses, and performance metrics are illustrative only. Actual capabilities depend on live integrations, permission grants, and business acceptance.