MossaicBook a demo

The Mossaic product

How do the pieces
actually work together?

Follow one order through the product. See how source records, AI evidence, credit rules and Finance authority connect to confirmed release.

Explore the product

Explore the Mossaic product

01 / Context

Start with the order and the facts behind it.

“Can we release this order today?” Bring the purchase order, quote and current account credit into one case.

TasksOrder releaseIllustrated preview
Order release request ORD-2076

Can we release this order today?

Order held for review
Order detailsHeld for review
AK
A request to release an order

“Can we release this order today? The purchase order and quote are attached.”

Sample request · Submitted by a colleague
Order value$46,800ORD-2076
Available credit$40,000Current account snapshot

$6,800 needs Finance authority. The order stays held while the evidence and exception are reviewed.

Sample dataORD-2076 · Awaiting review

The $46,800 order exceeds $40,000 available credit by $6,800. It stays held for review.

02 / Plan

Discuss the process. Review what Polaris drafts.

Describe the evidence checks, credit policy and Finance authority. Review a process, one agent and a rule table beside the conversation.

PolarisOrder releaseIllustrated preview
Order release request ORD-2076

Can we release this order today?

Drafts for review
PolarisProcess design conversation · Preview
Illustration
  1. You

    Build an order release process. Check the purchase order, quote and available credit before release.

  2. Polaris

    I’ll draft the evidence check and credit rules. Who can authorize an order above available credit?

  3. You

    The Finance controller. Hold incomplete evidence and exceptions. Approval must apply to one order only.

  4. Polaris

    I’ve drafted the process, one evidence-review agent and the credit rules. Review the holds, Finance decision and system confirmations.

    3 draft artifacts ready to review
Sample dataORD-2076 · Draft design

Three draft artifacts are ready for review. Nothing is published or running.

03 / Create

Give every decision and confirmation a place.

Connect evidence checks, credit rules, Finance review and confirmed follow-through. Keep holds and recovery paths visible.

ProcessesOrder releaseIllustrated preview
Order release request ORD-2076

Can we release this order today?

Process design
Order review and releaseBPMN-style illustration · Draft design

Scroll across to follow every route.

Order review and release with evidence and Finance holdsStart with the order. An AI task compares the purchase order and quote. Missing or conflicting evidence waits for the case owner to correct it and loops back to the comparison. Complete evidence reaches the credit rule. Within available credit follows configured routine authority. An exception goes to Finance, which can request more information, decline and keep the order held, or approve this order. Both authorized routes enter a collapsed release and follow-up subprocess. It revalidates the order and credit with the conditional SAP release action; a material change requires new Finance review. It records the SAP acknowledgement, then the separate HubSpot acknowledgement and retained evidence. Only all confirmed results reach the recorded final outcome, Released for fulfilment. Any failure or timeout leaves follow-up open. This is a process design illustration.AI evidence taskCompare PO + quoteBusiness rule taskApply credit ruleHuman taskFinance reviewWait for case ownerCorrect evidenceCollapsed subprocessRelease + follow-upRecord decisionKeep order heldRecord final outcomeReleased for fulfilmentEvidence complete?Within credit?Decision?Scope result?Order receivedHeld · DeclinedOutcome recordedFollow-up open

Process design · ORD-2076 follows the Finance exception route. No process is running here.

Subprocess: Release + follow-upDetails
  1. Revalidate and conditionally release in SAP. Enforce the order amount, current credit and recorded one-order authority with the release action. A prior read alone cannot guard concurrent changes. Material changes return to Finance.
  2. Record the ERP acknowledgement. A release is confirmed only with the SAP response. For a failure or timeout, reconcile the order state before retrying with the same case key.
  3. Confirm the CRM note separately. Record the HubSpot acknowledgement. A missing response leaves follow-up open while any confirmed SAP release remains recorded.
  4. Retain evidence and record the outcome. Link PO-8629, QT-581, credit facts, rule result, approval and both responses. Evidence-retention failure also leaves follow-up open.

Recovery preserves confirmed actions and never releases the order twice. “Released for fulfilment” requires every confirmation and the retained evidence record.

Sample dataORD-2076 · Illustrative design

The process design separates authority to release from confirmation that each action succeeded.

04 / Agents

Choose the model. Define the job and its limits.

The agent compares the purchase order and quote, retrieves account facts and cites its sources. Rules and Finance own the release decision.

AgentsOrder releaseIllustrated preview
Order release request ORD-2076

Can we release this order today?

Agent configuration
AI agentOrder review assistant
Illustration
Provider options

OpenAI · GPT-5

Model for this task
Other provider options
AnthropicOllamaPrivate model

Models depend on your organization’s provider settings.

Integration toolsExample configuration
Read order and account factsSAP · Read actionsAssigned
Approve or release the orderApproval and write actionsNot assigned

Case input: ORD-2076 · PO-8629 · QT-581. SAP account lookup is read-only.

Task promptv1

You are the order review assistant.

  1. Compare the supplied purchase order and quote: lines, totals and terms.
  2. Retrieve current available credit with its source reference.
  3. Return matched facts, source IDs and any missing or conflicting evidence.

Flag uncertainty for review. Finance owns exceptions; the process owns release.

Structured responseSample output
Document comparison
PO-8629 and QT-581 agree on $46,800.
Account fact
$40,000 available · SAP account snapshot.
Evidence status
Complete in this sample. Conflicts return for correction.

Sources attached for the rulePO-8629 · QT-581 · SAP account record. The agent cannot approve, change credit or release an order.

Sample dataORD-2076 · Draft configuration

The agent supplies evidence. It has no approval, credit-change or order-release action.

05 / Rules

Make the credit policy explicit.

Rules hold incomplete evidence, route orders within available credit and send exceptions to Finance. Arithmetic stays in the rule table.

DecisionsOrder releaseIllustrated preview
Order release request ORD-2076

Can we release this order today?

Policy configuration
Decision modelOrder release policy
Exception$46,800 − $40,000$6,800
Illustrative rules · First matching row
RuleEvidence / available creditRoute
1Missing, conflicting or stale evidenceHold for correction, then recheck
2Complete · Order ≤ available creditConfigured routine authority
3Complete · Order > available creditMatchedFinance controller review

Only complete, current evidence reaches credit routing. Every authorized route revalidates the order and credit with the ERP release action.

Sample dataORD-2076 · Sample rule result

$46,800 − $40,000 = $6,800. This order requires a Finance decision.

06 / Review

Put the evidence beside the human decision.

Finance sees the source records, current credit and exact exception. Approval applies to this order only; the standard credit limit stays unchanged.

TasksOrder releaseIllustrated preview
Order release request ORD-2076

Can we release this order today?

Awaiting Finance

Assigned to Finance controller

Authorize a $6,800 exception?
FC
Order value$46,800
Available credit$40,000

Authority requested

Allow this ORD-2076 order to exceed available credit by $6,800. The standard credit limit stays unchanged.

PO-8629QT-581Comparison + SAP facts
Approve this orderDeclineRequest information
No decision recorded in this earlier view

The order stays held. Finance records a reason and the one-order scope; release still requires revalidation.

Sample dataORD-2076 · Order held

Earlier sample state: Finance has not decided. The order stays held until authority is recorded.

07 / Run

Follow the decision through to confirmed actions.

Inspect the recorded approval, SAP release, HubSpot note and retained evidence. An unconfirmed action leaves follow-up open.

WorkflowsOrder releaseIllustrated preview
Order release request ORD-2076

Can we release this order today?

Completed
Completed sample6 completed
  1. 10:06 · AI agentOrder and quote checked

    PO-8629 and QT-581 agree on $46,800. Source references retained.

    Confirmed
  2. 10:07 · Business ruleCredit exception identified

    $46,800 order; $40,000 available credit. Finance reviews the $6,800 exception.

    Confirmed
  3. 10:12 · Finance controllerOne-order exception approved

    Finance controller approved ORD-2076 only. Standard credit limit unchanged.

    Confirmed
  4. 10:13 · ERPOrder release confirmed

    SAP rechecked the order and credit data and confirmed release. Receipt REL-2076.

    Confirmed
  5. 10:14 · CRMDecision recorded in CRM

    HubSpot confirmed the decision note. Receipt NOTE-2076.

    Confirmed
  6. 10:15 · Run historyEvidence record retained

    Documents, rule result, approval and both responses linked to CASE-2076.

    Confirmed
Released for fulfilmentSAP confirmed release. HubSpot confirmed the note. All evidence is linked to CASE-2076.
Sample dataORD-2076 · Released for fulfilment

Successful sample: ORD-2076 is released for fulfilment. All six events have a recorded result.

Sample data. Read-only illustration; Polaris is in preview.

Controlled autonomy

Give AI more responsibility
within clear boundaries.

Choose the responsibility each agent receives. Keep its work connected to policy checks, named reviewers and the systems around it.

01AI agents

Define the task and the tools.

Choose a model, write the instructions and assign the tools for a specific step. The agent prepares its findings within that scope.

A recommendation is an input to the process. Approval has its own step.

02Business rules

Make the review route explicit.

Evaluate the case against a decision table. Its result determines which path the process takes and who needs to review it.

The policy check runs as a separate step from the agent’s recommendation.

03Human tasks

Put the decision with its owner.

Give the reviewer the request, the agent’s findings and the policy result in one task. The process waits for their decision.

The supplier stays unapproved while the human review is pending.

04System actions

Connect the decision to the action.

Place system updates after the required approval. Follow the run to see the completed steps, the current wait and the work still ahead.

The approval and the system action are separate, visible steps.

Explore each part of an illustrative supplier review.

Supplier review · SUP-032Product illustration
Agent configuration

Supplier review assistant

v1
Provider & modelOpenAI · GPT-5Example configuration
Provider optionsOpenAIAnthropicPrivate model
Task instructions

Review the supplier’s insurance document against the checklist.

  1. Extract the coverage and expiry date.
  2. Identify missing or expired documents.
  3. Return findings for procurement review.
Leave supplier approval to the owner.
Assigned tools
Read supplier documentsRead
Read supplier recordRead
Approve supplierNot assigned
Example output: insurance document has expired.
Decision model

Supplier document policy

v1
Case input
Insurance documentExpired
Example decision table
Insurance statusReview route
CurrentContinue checks
ExpiredMatchedProcurement owner
MissingProcurement owner
Decision resultOwner review required

The expired document routes this case to procurement.

Next step: create the human review task.
Human task

Review supplier documents

Waiting
PO
Assigned reviewerProcurement owner
Why this needs your review

The insurance document has expired. Review the findings and decide what the supplier must provide next.

Agent finding
Insurance expired
Policy result
Owner review required
Supplier approval
Pending
Insurance documentAgent findingsPolicy result
No decision recorded

The process is waiting for the procurement owner.

Run history

Supplier review

SUP-032
  1. AI agentDocument findings prepared
    Completed
  2. Business ruleInsurance check evaluated
    Completed
  3. Human taskProcurement owner review
    Waiting
  4. System actionUpdate supplier record
    Not reached
System actionNot reached
supplier.update_recordsupplier_id: SUP-032approval: required

The supplier record can be updated after the approval step.

No update has been requested in this example.

Integrations

Bring your tools into the process.

Bring enterprise records, customer context, messages and files into the same process, using the systems your team already works with.

Enterprise and ERP

Bring finance, purchasing and supply chain records into the work.

  • SAP S/4HANAAPI example

Team communication

Send the update to the people who need it, in a channel or by email.

  • SlackConnector setup
  • GmailAPI example

Customer and service systems

Find the customer context and record the next step in the work.

  • HubSpotConnector setup
  • ZendeskAPI example

Data and files

Use the facts and files a decision needs, then store the agreed result.

  • Google SheetsConnector setup
  • PostgreSQLDatabase setup
  • Amazon S3Connector setup

SAP S/4HANA, Gmail and Zendesk are API examples to assess and build. Every connection needs account access, permissions and testing of the required actions.

Tools through MCP

Give agents the tools for the task.

Model Context Protocol (MCP) gives agents a standard way to use tools and data from other systems.

  • NotionDocuments and knowledge
  • LinearIssues and projects
  • GitHubCode and reviews
  • AtlassianJira and Confluence

These providers publish MCP servers. Check compatibility, authentication and the actions each server exposes, then test the connection for your process.

Another system in mind? We can assess its API, webhooks or a suitable MCP server.

Discuss your systems

Security and control

Keep sensitive changes in the right hands.

Choose who can access the work and what an agent can do. Add approval steps before sensitive updates and keep the result with the run.

  • Access for the right people
  • Human approval where it matters
  • A record of the work
Order release request · ORD-2076Can we release this order today?
Before approval

  1. Order review assistant

    Check the order evidence

    Compare PO-8629 with QT-581 and retrieve current account credit.

    Complete

  2. Order release policy

    Route the $6,800 exception

    $46,800 exceeds $40,000 available credit. Finance must review.

    Complete

  3. Finance controller

    Review this order only

    Before approval, ORD-2076 stays held. The standard limit is unchanged.

    Waiting for approval

  4. SAP

    Recheck and release the order

    Requires recorded approval and a fresh order and credit check.

    Not reached
Kept with the runIllustrative case · Source checks and rule result recorded. Finance review pending.

Access

Choose who sees the work.

Organization and project permissions govern access. Assign human tasks to the person responsible.

Agent actions

Assign the actions an agent needs.

Choose the operations available through a connector. Review the actions exposed by any connected MCP server.

Credentials

Manage connection credentials.

Keep connection secrets at organization or project scope. Review the permissions granted by each connected system.

Run history

See the decision and the result.

Review workflow history and task completion records to see what happened, who responded and what followed.

Checks and approval routes are defined in the process. Review data access, model providers and connection permissions for your deployment.

Start with the work on your mind

Where does your
process get stuck?

Bring a process, a recurring exception or a handoff that takes too much chasing. We’ll explore where Mossaic could help.

Book a demo