OIAR transforms multi-stakeholder interviews and documents into structured, evidence-backed reports — so your assessments hold up to scrutiny and drive real decisions. Human-in-the-loop at every critical gate.
In enterprise contexts, information is distributed, incomplete and often conflicting. Facts, opinions and interpretations mix together. Conclusions don't hold up to scrutiny because sources are not traced.
Every stakeholder has a partial version. Gathering them manually introduces delays, gaps and unverifiable interpretations.
Without systematic isolation and classification, dominant statements suppress minority signals that may be critical.
A report without a traceable link between evidence and recommendation is opinion, not analysis. It won't hold up to scrutiny or generate decisions.
OIAR is not a generic chatbot. It's a framework for orchestrating structured information gathering, isolating sources, classifying evidence and producing operational reports.
The Orchestrator Agent analyzes the objective, produces the Global Objective and Plan, assigns skills to Interviewer Agents and activates them in parallel.
N Interviewer Agents operate in parallel, each segregated in their own scope. They gather documents via MCP channels and produce a structured Interview MD.
The Analysis Agent reads all Interview MDs, classifies every statement (Fact, Evidence, Contradiction), detects gaps and assigns confidence scores.
The Report Agent produces the final document according to the scenario template: Executive Summary, Finding, Evidence Map, Roadmap. Publication only after HITL-REPORT.
Every critical transition requires explicit approval. You can reject with notes: the system returns to the previous phase and incorporates your feedback before re-presenting the result.
You start a chat with the orchestrator: define objective, scope, version and stakeholders. The system generates the assessment plan.
Each stakeholder receives an email link with a private isolated chat. Agents operate in parallel, each in their own scope and Data Room folder.
The Analysis Agent classifies each statement (Fact, Opinion, Hypothesis, Contradiction), detects module gaps and produces a sufficiency score.
The Report Agent produces Executive Summary, Gap Analysis per module, Claim Evidence Map and remediation Roadmap. Written in Markdown, downloadable.
The approved report is published in reports/final-report.md. The audit log of every HITL decision is retained and consultable.
OIAR assumes sources are partial, biased or incomplete. It doesn't seek consensus: it seeks triangulation, evidence and transparency about gaps.
Declared fact, opinion, hypothesis, documentary evidence, contradiction. The classification is preserved in the data model and in the report.
The Interviewer Agent receives no statements from other stakeholders. Cross-source contamination bias is eliminated structurally.
HITL-PLAN, HITL-INTERVIEW, HITL-CLOSE, HITL-REPLAN (opt.) and HITL-REPORT. The system never advances alone at critical transitions.
A minority with strong evidence can be more relevant than a majority without documentary support. Contradictions are made explicit, not suppressed.
OIAR is not a single portal. It's a template instantiated once per scenario. Every instance has the same screens, panels, logic — only the color theme and loaded skills change.
If a change touches layout, panels, menu or behavior → it belongs to the shared layer. If it touches color or font → it belongs to the instance theme file.
Each instance has one accent color (--signal). A second color (--accent-2) is defined but not wired — only for scenarios that explicitly require it.
Duplicate the reference scenario folder. Change only the 4 accent tokens and neutral tint in the theme file. No panels are touched.
Each agent is not hard-coded: its instructions are versioned Markdown files in the repository, selected by the Orchestrator based on the stakeholder profile and scenario. To create a new instance, write its skills.
Skills are MD files in the repository, not runtime configurations. They change via PR with review, not through an interface. Versioning is free.
The Orchestrator picks skills from the Skill Repository suited to each stakeholder's profile and injects them into the assigned Interviewer Agent's prompt.
Technical stakeholder, executive sponsor, vendor representative, operational key user. Each profile has dedicated questions, signals and output format.
New scenario (SAP Migration, Vendor Dispute, …): duplicate the most similar instance folder, write the specific skills, modify the theme file. Zero code.
Same framework, different skills, different theme. Every use case originates from duplicating the base instance with the appropriate skills loaded in the repository.
Gap analysis of Odoo implementation by module, ERP maturity, stakeholder misalignments, prioritized remediation roadmap.
Late, blocked or out-of-control IT project. Root cause diagnosis, risk map, dependencies, missing decisions, recovery plan with evidence.
Rapid evaluation of a vendor, system or technical asset before a major commitment. Key risks, maturity assessment, gaps and prioritized recommendations.
Start with a concrete use case — gap analysis and pre-implementation assessment for Odoo projects. If your use case is different, tell us.
We'll get back to you shortly to arrange a demo of the framework on your scenario.