Back to main page

Technical documentation

How OIAR works

Complete flow from assessment initialization to report delivery — with Human-in-the-Loop gates, parallel interviews and Data Room.

Multi-agent Human-in-the-Loop MAP-REDUCE Parallel interviews Claim & Evidence Audit log
01
Conversation with the orchestrator

The consultant starts a chat with the OIAR orchestrator. Together they define the assessment objective, the target Odoo version, modules in scope and the list of stakeholders to involve. Once satisfied, the consultant finalises the conversation: the orchestrator generates the structured plan.

Objective Odoo Version Modules in scope Stakeholder Orchestrator Guided chat
HITL-Plan · Plan Approval Gate · Mandatory
The consultant reviews the generated plan: structured objective, stakeholder list and interview outline for each one. They approve to start the process or reject with notes — the system incorporates the feedback and re-presents the updated plan.
HITL-PLAN
HITL-Interview · Start Interviews · Mandatory
The consultant approves sending email invitations to stakeholders and creating dedicated chats. Data Room folders are created only at this point. By rejecting, it is possible to go back and revise the plan and the stakeholder list.
HITL-INTERVIEW
02
Parallel interviews via dedicated chat

Each stakeholder receives an email link granting access to a private, isolated chat. OIAR agents operate in parallel — one per stakeholder — each in their own Data Room folder. Each interviewee completes the session independently, at their own pace.

IT Manager
infrastructure · customizations · integrations
Running
Business Owner
processes · KPIs · user adoption
Running
CFO / Finance
accounting · reporting · compliance
Running
Operations
warehouse · logistics · inventory
Running
Data Room — storage under user control
Google Drive SharePoint / OneDrive Dropbox Notion Local filesystem
Isolated chats per stakeholder Parallel agents (MAP) Data Room per agent Documents uploaded by stakeholder
03
Evidence synthesis and structuring (REDUCE)

Once interviews are complete, the orchestrator runs the REDUCE phase: it aggregates findings from all agents, identifies contradictions between stakeholders, classifies evidence using the Claim & Evidence model and structures processes, requirements, gaps and risks.

Processes
As-is mapping per candidate Odoo area
Requirements
Tracked with source and reference stakeholder
Gaps
Classified HIGH / MED / LOW with description and action
Risks
Data migration, customisations, integrations
Contradictions
Highlighted between different stakeholders for review
Open questions
To be resolved in the next workshop
MAP-REDUCE Claim & Evidence Cross-stakeholder validation Audit log
HITL-Review · Consultant Approval · Mandatory
The consultant reviews the structured draft: approves individual findings, corrects classifications, adds their own notes and manages the highlighted contradictions. No finding passes into the final report without explicit approval.
HITL-REVIEW
04
Pre-assessment report generation

The system composes the final report from the findings approved by the consultant. The report is structured, exportable. It contains all the sections needed to support the estimate or proposal to the client.

OIAR_PreAssessment_GammaMetalli_v1.pdf
Executive Summary Analysed processes Candidate Odoo areas Preliminary fit Classified gaps Risks Open questions Complexity by area Next steps Consultant notes
Export PDF Shareable Consultant-reviewed Attached audit log
Architecture

Key technical components

For those who want to understand what’s under the hood — without these architectural choices impacting the consultant’s experience.

Orchestration
Multi-agent with MAP-REDUCE
A central orchestrator coordinates specialised agents operating in parallel (MAP). Results are aggregated and synthesised in the REDUCE phase.
orchestrator → [agent₁ ‖ agent₂ ‖ agentₙ] → reduce
Control
Human-in-the-Loop (HITL)
The process includes three mandatory consultant approval gates: plan, interview start, finding review. No gate can be bypassed automatically.
HITL-Plan · HITL-Interview · HITL-Review
Evidence
Claim & Evidence
Every finding is traced to its source: stakeholder, transcript, supporting document. No statement in the report is without verifiable evidence.
finding → [claim, source, evidence_ref, confidence]
Storage
Data Room with scope enforcement
Data stays in the user’s chosen document system. Access control ensures isolation between agents and between distinct assessments.
scope: /assessment/{id}/agent/{n}/
Traceability
Audit log
Every agent decision, every HITL approval and every draft modification is recorded in the audit log — attachable to the report or independently accessible.
timestamp · actor · action · finding_id
Context
Context window management
Interview sessions are isolated to avoid context overflow. The orchestrator receives structured summaries from agents, not raw transcripts.
agent → summary(structured) → orchestrator

Interested in the closed beta?

Test OIAR on a real Odoo deal. Assisted assessment, reviewable report, final review call included.

Join the closed beta →