Classification starts with the use case
A deployment must be assessed in its real context, including intended purpose, affected persons, decision impact and whether RAIVA acts as provider, deployer support or processor.
No general product label can replace a documented classification for the customer's concrete workflow.
Transparency and evidence
RAIVA is designed to connect individual claims to concrete source passages and to keep missing evidence and conflicts visible.
A source link does not prove completeness. Users must be able to distinguish an AI-generated result, its supporting material and the points that still require review.
Human oversight
High-impact outputs should remain subject to a competent human decision. Roles, permissions, review points and escalation paths must be defined for each deployment.
Virtual Employees describe a future direction and do not imply unsupervised autonomous operation.
Documentation and monitoring
Relevant system versions, input scope, sources, outputs and review actions should be documented in proportion to risk and contractual requirements.
Quality, incidents and material changes require ongoing review. The evidence available for one result does not establish performance across every workflow.
Governance contact
For AI-governance documentation or a use-case review, contact ai-governance@raiva.io.
Legal classification and any required conformity assessment remain subject to professional review before deployment.