How Kohentra builds a proposal
Kohentra always follows the same path, whatever specialized capability is mobilized: observe, contextualize, orchestrate, analyze, explain, submit to a human decision.
1. Business situation
It all starts with real activity in your management tool: a contract moving forward, an intervention carried out, an invoice issued, a thirdparty updated.
2. Observed context
Kohentra rebuilds the context around that activity before drawing any conclusion: the object's history, relations to other business objects, events normally expected at this stage.
A business relation is never treated as established the moment it's first detected: it follows a lifecycle (discovered, observed, activated) before it can weigh into an analysis.
3. Kohentra orchestration
A supervision layer decides which specialized capability is relevant for the identified situation, accounting for cases already resolved and analyses already in flight - never redundant processing.
4. Specialized agent
A capability dedicated to this type of situation (billing, business object closure, business coherence...) analyzes the context Kohentra gathered.
5. Analysis and proposal
The capability formulates an explicit proposal - never an isolated numeric score - citing the facts that justify it.
6. Human decision
A human user confirms, dismisses or defers the proposal in the application. Kohentra never carries out an automatic business action in place of a person.