Five roles.
One accountable loop.
You set direction. The team owns the routine work, shares the same evidence, and brings back only the decisions that need you. Five roles. One name — NOVUS.
One production signal becomes one governed improvement.
Shared assets sit underneath the team.
They are not extra employees.
"Never pushy. Always closing."
Owns
Every live customer conversation and its outcome.
Delivers
Answer · recommendation · approved action · sale or service result.
Routes when
Confidence, policy, or customer risk requires a human. Hand-offs are free.
escalated 6% · message-level
quality bar: conversion + CSAT
at human-rep parity
"Trusts nothing until it's tested."
Owns
Quality signals, risk grading, and repair routing.
Delivers
Badcase · severity · evidence · named repair owner.
Routes when
Facts → Vera · strategy → Ugo · patterns → Skye · exceptions → human.
→ intent[size-calc] · fixed ✓
P1 "[photo] what size is this?"
→ fixed ✓ · in suite forever
"Four gates. No exceptions."
Owns
The product facts behind every answer.
Delivers
Approved knowledge version · conflict alert · provenance trail.
Routes when
Low-confidence or long-tail facts need named human review.
Approved → Published
named owner per batch
four gates, always
"Ships only what passes."
Owns
Behavior, routing, and strategy changes.
Delivers
Strategy diff · evaluated proposal · canary · rollback-ready version.
Routes when
A change is unmeasurable, high-risk, or needs human approval.
V2.24_1 · rolled back
draft · in eval
scope: product-level
"Finds the pattern behind the noise."
Owns
Recurring patterns and measured business impact.
Delivers
Opportunity · root-cause report · brief · post-release lift.
Routes when
A finding needs a knowledge repair from Vera or strategy change from Ugo.
reception reports · VOC mining
one source of truth,
governed definitions
They share one operating core.
Nova encounters the issue. Odin classifies the root cause. Product facts go to Vera; behavior and routing go to Ugo; recurring patterns and measured impact go to Skye. Every change passes the same evaluation and versioning gates, and exceptions still have a human owner. The value is not five chatbots. It is one accountable operating loop.