PLATFORM
Workflows and orchestration
Model steps, conditions, hand-offs, approvals and outcomes.
Overview
A workflow makes a process explicit: what starts it, what information it needs, which steps run, where decisions occur and how completion is verified. In Neocortex, available execution paths depend on the configured environment and integrations. Treat this as workflow-design guidance rather than a promise that every deployment contains a built-in visual workflow canvas.
Trigger and inputs
Define the initiating event, required fields, source of truth and validation rules.
Steps and routing
Break work into clear, testable steps. Make conditions, retries, timeouts and failure paths intentional.
Policy and approval
Check permissions at the point of action. Route high-impact or ambiguous decisions to an accountable person.
Idempotency and recovery
Where supported, design retries to avoid duplicate writes and provide a safe way to resume or compensate for partial work.
Observability
Record status, timing, errors and material decisions without unnecessarily copying sensitive payloads into logs.
Outcome checks
Verify the business result in the target system; a successful model response is not proof that the task completed.
Worked example
A governed approval workflow
A useful pattern for work that drafts an action but must not commit it without approval.
- 1Receive the request and validate required fields.
- 2Retrieve only the context the requesting identity is allowed to access.
- 3Prepare a draft and show the supporting context and intended action.
- 4Pause for approval by the nominated person or role.
- 5Execute only the approved action, then verify the result in the target system.
- 6If authorisation, approval or verification fails, stop safely and notify the workflow owner.
Was this guide useful?
Send feedback or flag a gap. Include the article link so the team can improve the right guide.