From scattered
knowledge to
accountable action.

Browse folders, search uploaded documents and open a file in its original context. Folder access gives knowledge owners a practical way to decide who can read and manage each area.

Folders with ownership

Organize manuals, projects and company material; manage folder access where permitted.

Documents with context

Open a document record, its origin and a page-anchored preview; see when a file is still processing.

The source and ingestion workspaces show how a configured implementation can select content, inspect processing and assign source repair. Connection status and searchable content are separate checks.

PROTOTYPE SCOPECurrent prototype: Sources registers sample metadata only. Message content, files and attachments are not downloaded or indexed. Ingestion transitions are simulated; storage and extraction services require implementation.

A deliberate content boundary

Agree which source folders and mailboxes may feed knowledge, with their owners and access limits.

A repairable pipeline

Use the illustrated processing states and retry controls to define operational ownership and exception handling.

Use the Assistant to ask a question against available knowledge. Citation links bring the supporting document into the conversation, so a colleague can check the underlying material before deciding what to do.

Visible source references

Follow the cited material and compare the response with the source context.

A reviewable next step

Keep consequential decisions with the responsible person. Model, provider and retrieval setup are implementation choices.

Memory separates what happened, what is true and what works. Agent-written memories wait for a person to confirm them, while scope and evidence help keep one client's lesson from becoming everybody's instruction.

Three distinct layers

Review episodes, facts and procedures with their origin, status and supporting evidence.

Confirmation and scope

Confirm proposed learning and define where it applies, including a specific customer or document type.

Build a trigger-to-outcome flow with If, Switch and AI sort branches. Configure an AI step's model, readable folders and permitted lookups, then test sample items and inspect the item count on each wire.

A readable decision path

Use the canvas or an ordered sentence view to understand the same workflow, including branches that go nowhere.

Test before activation

Run sample items. The screen refuses activation while required parts remain unfinished and explains why.

Scan the shape of a run before opening its detail. Inspect what each step received, produced and said, and distinguish a branch that was not taken from a step that was never connected.

Step-level evidence

Read inputs, outputs and explanations, including why items did not continue down a branch.

A version to investigate

Use the recorded run and workflow version as the starting point for review; compare process changes with the execution evidence.

Capability policies and agent-action rules make delegation boundaries visible. Action conditions, approval routing and reversibility sit alongside the policy; both remain inside role and data-access limits.

Explicit action modes

Review Automatic, Needs approval and Blocked modes with the applicable scope and conditions.

Accountable handoffs

Inspect the approver, timeout or escalation settings and change history before widening delegation.

The evaluation workspace brings job-level outcomes, recurring errors and human checking into view. Use the sample review patterns to agree how real pilot results will be judged before changing an approval threshold.

Look beyond a single answer

Review task-level results and recurring failure patterns rather than treating a dashboard score as universal accuracy.

Keep human review meaningful

Inspect reviewer checking and use representative cases to agree when a workflow should stop for confirmation.

The privacy workspace includes data requests, retention, a processing register and a view of where data goes. Shared tasks and approval inboxes support the human follow-up around a governed process.

A view of data handling

Inspect processing and retention records with the responsible privacy and implementation teams.

A human route to completion

Use tasks, inboxes and review handoffs to make unresolved work visible to the right people.