Contact

Platform module

Sessions + HITL

Keep sources, processing steps and human decisions together. Give responsible users the context needed to review an outcome.

Human review and execution history

  • Source and operation history
  • Review queues
  • Accept, reject and correct
  • Continue after a decision

Scope

Its role in the system.

Inside the application

Application workflow

Selected use cases, source information and operational outputs.

Session history

Source ingestion, model operations, tool calls and human decisions are tracked in one work history. This record explains how a result was formed.

Sessions + HITLScenario / 01
Interface conceptSchematic example

Session history

Traceable record
  1. 1
    SourceSource and scope
  2. 2
    Model operationProcessing context
  3. 3
    Tool callReview point
  4. 4
    User decisionNext operation
The original record and subsequent decision stay separate.
Decision boundary

Source access, action scope and human review are configured for the application.

  • Source, model and tool operations
  • Session identity
OutputConsolidated execution history

Review workspace

Reviewers see the recommendation, evidence and required decision together. Access and action boundaries remain in force throughout review.

Sessions + HITLScenario / 02
Interface conceptSchematic example

Review workspace

RecommendationSource-linked
Evidence
Review context

Required decision

Action boundary

Source and interpretation remain separate.
Decision boundary

Source access, action scope and human review are configured for the application.

  • Recommendation and supporting evidence
  • Action scope
OutputDecision context presented for review

After the decision

A user correction does not erase the initial suggestion. The decision is retained, and subsequent operations follow the defined approval and permission rules.

Sessions + HITLScenario / 03
Interface conceptSchematic example

After the decision

Initial assessment

Initial suggestion

User correction

Decision
Governed continuation

Decision record

Governed continuation

Decision boundary

Source access, action scope and human review are configured for the application.

  • Initial suggestion
  • User approval, rejection or correction
OutputRetained decision and permitted next action
01 / INPUT

Recommendation, sources and work context

Source identity and access scope remain part of the work.

02 / PROCESS

Accept, reject or correct

The module operates within the configured application and control boundaries.

03 / OUTPUT

Decision record and governed continuation

The next step uses the result with its source and execution context.

Control design

Progress, exceptions and decisions.

Reference behavior for implementation; each deployment needs its own configuration and verification.

Ready for review

Show the original suggestion, supporting evidence and decision point together.

Correction or rejection

A user decision does not erase the original suggestion. Keep the rationale and corrected result separately.

Continue after a decision

Track approval separately from target-system execution. Records selected for evaluation need separate permission and suitability checks.

01

The history of a job

Sources, retrieval results, model operations, tool calls and decisions are tracked within a session, showing how an outcome was formed.

02

Context for the right person

Review queues bring together the proposed result, evidence and decision point. Users approve, correct or reject the result.

03

Preserve corrections

Initial suggestions and user decisions are stored separately. Suitable, authorized records may later support evaluation data preparation.

Technical operating model

Review requires more than a result

To decide well, a user needs the proposal, its evidence and the effect of the decision together. Sessions + HITL connects model execution, sources and human corrections without overwriting the original suggestion with the final decision.

Component relationship / schematic

Execution and source history

Show which information and tools produced the result.

Review context

Present the recommendation, evidence and decision point together.

Decision and continuation record

Continue traceably after acceptance, rejection or correction.

01

Connecting it to an application

Define incoming data, resulting records and the people or systems that use them together. A functioning component alone is not an acceptance criterion for the entire workflow.

02

Checking a change

When a schema, tool or model changes, existing use cases are tested again. Errors, permissions and human-review paths matter as much as successful execution.

Components and operating approach

Review requires more than a result

Select a topic to explore the relationships between information, responsibility and delivery.

01

Execution and source history

Show which information and tools produced the result.

Read sourceWithin access scope
Propose resultWith supporting evidence
Write externallySeparate permission and approval
Proposal record
DEMO-PROPOSAL-014
Review
Awaiting correction
Continuation record
Linked to the decision
02

Review context

Present the recommendation, evidence and decision point together.

Read sourceWithin access scope
Propose resultWith supporting evidence
Write externallySeparate permission and approval
Proposal record
DEMO-PROPOSAL-014
Review
Awaiting correction
Continuation record
Linked to the decision
03

Decision and continuation record

Continue traceably after acceptance, rejection or correction.

Read sourceWithin access scope
Propose resultWith supporting evidence
Write externallySeparate permission and approval
Proposal record
DEMO-PROPOSAL-014
Review
Awaiting correction
Continuation record
Linked to the decision

An operating-model illustration, not live operations or measured performance results.

Connected modules

Explore the rest of the platform.

Data management

Data House

A shared data foundation for documents, media and enterprise records. Preserve identity, versions and permissions across retrieval and AI operations.

Explore the module ↗Workflow orchestration

Orchestrator

Coordinate models, tools and people within the same operation. Preserve state and manage errors, retries and review across long-running work.

Explore the module ↗Enterprise integration

WebKit

Connect defined operations in ERP, CRM and enterprise applications to AI workflows, with clear input, output and access boundaries.

Explore the module ↗AI processing modules

AI Modules

Combine document, image, speech, sensor and knowledge processing. Turn different source formats into usable, source-linked data.

Explore the module ↗Model evaluation and adaptation

Model Adaptation

Prepare evaluation and training data from verified examples. Compare changes on consistent tasks and track model versions.

Explore the module ↗

Work with us

Discuss your project with us.

Let’s assess your operations, data landscape and priorities together.

Start a conversation