01
One workspace for process work
Describe the task or choose a specialist role. Prepare authorized materials and business context, then
review findings, source references and deliverables in the workspace. Keep work records and previous
conversations available within the user’s permitted scope.
02
FlowBuddy Core: shared process AI capabilities
Core brings together business AI capabilities, knowledge, rules and authorization context. Digital
teammates use these capabilities to organize role-specific work. Existing business pages can also use
them in context, with system coverage and deployment scope confirmed for each project.
03
Support design, execution and analysis
For EBPA, assist with document parsing, process drafts and standards checks. For BPA, support
navigation, form preparation and preliminary review. For BPI, assist with data mapping, chart creation
and interpretation. Validate drafts, calculations and findings against the relevant business objects
before use.
04
Keep knowledge and rules traceable
Organize process documents, policies and SOPs with their source versions. Review generated guidance
before publishing it and recheck affected references when a source changes. A document entering the
knowledge base does not automatically become an executable compliance rule.
05
Authorize roles and data separately
Control platform access, teammate use and configuration, and knowledge or business data scope
separately. Use groups to maintain team permissions. Core carries identity and authorization context,
while source systems continue to enforce permissions for business actions.
06
Configure model services for the task
Configure generation, embedding and reranking services separately to suit project requirements. Core
manages retrieval, rules and invocation records. Model output remains subject to business validation and
human review.
07
Validate one workflow before expanding
Choose a real process, participating roles and acceptance criteria. Prepare process documents and
permissions, then verify results, citations, identity mappings and task records. Expand the knowledge
base, roles and system connections after the pilot demonstrates a useful, traceable way of working.