Project delivery risk and change coordination
The status report looks fine. Do milestones, budgets and changes tell a different story?
Explore case and packageBuild · Builders
Use the coding agent you know to build context the enterprise owns.
DataFocus doesn’t need to be the only AI entry point. Builders and coding agents shape the business definitions, owners approve them, and every other entry point shares the same definitions and rules.
Explore the building workflow with synthetic data. For your own instance, use the tools and permissions available in that version.
S2 · A sketch of the flow, not a transcript
The agent does the organizing. People make the calls.
- Coding AgentInspect sources
CRM customers · ERP orders · MES production tasks · contract documents
- Coding AgentPropose a draft
4 object types · 3 relationships · 1 definition to confirm
- Coding AgentStop and ask
Does “delivery complete” mean production finished, goods shipped or customer acceptance? It changes the risk result, so I won’t decide it for you.
- Coding AgentDiff and tests
Source writes 0 · access unchanged
+ Customer → Order + Order → ProductionTask + Order → ContractDoc
- OwnerWait for approval
Publishing needs someone with authority. The agent can’t approve its own change.
- Business agentHand to a business agent
Once published, another agent runs S1 on the same definitions.
Delivery sequence
From one demo to a delivery someone else can take over.
- 01Walk through S2See the whole flow once, from an empty ontology to use by a business agent
- 02Prepare an environmentPrepare an OT Flash or OT Heavy instance, record its version, and choose synthetic or authorized data sources
- 03Connect a clientConfigure per client version, mode and organization rules
- 04Check the real tool scopeRead the instance’s tool catalog and confirm parameters and access scopes
- 05Confirm business definitionsStop and ask the owner about unclear definitions
- 06Draft and testTypes, references, access and business checks all pass
- 07Publish after approvalThe approver is not the agent that drafted
- 08Accept with S1Another business agent completes the task on the same definitions
- 09Reuse for the next clientExport reusable definitions and mappings, then bind sources in the target project
- 10Deliver under partner rulesFollow the agreed delivery scope, license and service terms
Permission domains
Writing the ontology is not editing the ERP.
The three domains are authorized separately, and modelling rights are distinct from business read rights.
Business reads
Query orders, read contracts, search rules
Verify the real interface and scopeBuilding and changing context
Objects, relationships, source mappings, rules, document versions
Use the tools exposed by your instance within current permissionsExternal business actions
ERP edits, payments, outbound email, deleting source data
This experience does not connect external business writesMaterial for agents
Let coding agents work against the real interface.
Prepare these materials for each project so coding agents work from the instance’s tool catalog, business rules and permissions. Tool names and parameters must match the version you use.
- Real tool schemas and versions
- Environment checks and configuration examples
- Change preview and dry-run
- Expected facts and negative cases
- Errors and how to fix them
- Rollback and version compatibility
- Handover checklist
S4