Context-Native
Understand the current user, page, form, workflow step, and business object—without making users repeat what the system already knows.
From digital office to executable Agentic Office
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.
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.
Understand the current user, page, form, workflow step, and business object—without making users repeat what the system already knows.
Inherit ecology identities, organizations, roles, and data permissions. What AI can see and do has clear boundaries.
Queries can run automatically; drafts can be previewed; submissions require confirmation. High-risk actions go through dedicated approval and human review gates.
Prove outcomes with business IDs, field values, workflow statuses, and execution logs—not API responses or on-screen messages.
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.
From “Finding a Process” to “Getting Things Done”
An On-the-Go Service Desk for the Entire Employee Journey
A Controlled Loop from Receipts to Accounting
End-to-End Flow from Requests and Bids to Fulfillment
Bringing Risk Alerts into Business Operations
Keep Plans, Tasks, and Risks Aligned
Access Frequently Used Services in One Sentence
Answers Grounded in Policies and Source Text
From Numbers to Insights and Action
ecology remains responsible for identities, permissions, workflows, and business objects. BoltFusion handles Agent orchestration, tool execution, evidence aggregation, and runtime governance.
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.
ecology portal, workflow pages, mobile, messages
People, Positions, Permissions, Pages, Forms, Workflows, Organization
Page Agent, Scenario Agent, Composite Agent
Agent API, Work, Monitor, and Policy Gateway
ecology capabilities, enterprise systems, external services
runId, requestId, nodes, fields, and logs
Create and query the same runPolicies · Tools · BrowserStatus · Logs · ReplayScenarios vary; runtime standards stay consistent. Business requests enter through the Agent API, Work stays internal, and Monitor does not accept business write requests.
discover → draft → confirm → executeBy default, start with read-only discovery or drafts. Authorization requirements increase as actions get closer to affecting real business operations.
POST /runs → GET /runs/{runId}A stable idempotency key, business context, action mode, and human confirmation record travel with the run.
succeeded + businessId + workerStageUse 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.
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"
}
}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.
Unified Semantics · Unified Authentication
Unified Policies · Unified Evidence
Check leave balances and calendar availability, generate a leave request form, and submit it after confirmation. Then retrieve the current workflow step.
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.
Validate at least one real role-based path per scenario category, covering inputs, outputs, human approval gates, and result readback.
Populate, save, submit, approve, and change permissions each have their own policies, confirmations, and audit evidence.
Link each runId to its business ID, fields, nodes, and logs so failures can be located, retried, or handed off to a human.
Changes to versions, prompts, tools, knowledge, and permissions are covered by regression tests and operational metrics.
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.
Business objects, role permissions, action levels, success evidence
Deliverable: Scenario Map + Permission MatrixForm Filling, Knowledge Q&A, Onboarding Coordination
Deliverable: Runnable Closed Loop + Business ReadbackReuse Agent Runtime, tool contracts, and governance gates
Deliverable: Scenario Packages + Connector ListEvaluation, replay, cost, performance, permissions, and version governance
Deliverable: Operations Dashboard + Iteration MechanismThis 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.