Skip to main content
R.I.C.H.O.
A RICHO SYSTEMS PLATFORM

R.I.C.H.O. Use Cases

Use Cases

Threeprimaryusecases.Honestaboutwhateachdoes.

Each use case shows the input, process, output and limit. Enforcement labels explain how each control actually works — not how it is described in marketing.

Enforcement Labels

Each control in the use cases below is labelled with its actual enforcement level. These labels describe how the control works in practice, not how it is aspirationally described.

POLICY-DESCRIBED

The control is defined in policy documentation. Enforcement depends on implementation.

PROMPT-CONFIGURED

The control is applied through AI prompt instructions. Effective within the prompt context.

INTERFACE-RESTRICTED

The control is enforced by the absence of a capability in the interface. Not a security control.

APPLICATION-ENFORCED

The control is enforced by application logic. Effective within the deployed application.

PROVIDER-RESTRICTED

The control is enforced by the AI provider's own safety systems.

HUMAN-APPROVAL ENFORCED

The control requires explicit human approval before proceeding. Recorded with identity and timestamp.

01

Controlled Business Intelligence

INPUT

Structured business information — company background, market context, competitive landscape, financial indicators.

PROCESS

AI-assisted analysis inside a defined assessment framework. The system applies structured analytical roles to identify patterns, risks and evidence gaps. Each finding is classified by confidence level.

OUTPUT

Scored findings, identified risks, evidence gaps and recommended actions. All outputs are labelled with their evidence basis and confidence level.

LIMIT — The system does not independently verify information unless an external source is explicitly used. Findings are based on the inputs provided. The output is an analytical aid, not a verified report.

CONTROLS AND ENFORCEMENT LEVELS

Analysis scopePrompt-configured

The analytical framework is defined in the prompt. The AI operates within the stated scope.

Output labellingApplication-enforced

All outputs are labelled with confidence level and evidence basis by the application.

External data accessInterface-restricted

The public demonstration has no live external data access. Analysis is based on provided inputs only.

Human reviewHuman-approval enforced

Findings are presented for human review before any action is recommended.

02

Commercial-Readiness Assessment

INPUT

Product documentation, ownership structure, customer evidence, revenue data and technical specifications.

PROCESS

Assessment against documented readiness dimensions — product maturity, market evidence, commercial structure, technical foundation and risk profile. Each dimension is scored and explained.

OUTPUT

Commercial-readiness report with dimension scores, identified gaps and improvement priorities. Clearly labelled as an assessment, not a valuation or certification.

LIMIT — The result is not a formal valuation, audit or certification. It is a structured analytical assessment based on the information provided. Professional review is required before commercial decisions.

CONTROLS AND ENFORCEMENT LEVELS

Assessment frameworkPolicy-described

The readiness dimensions and scoring criteria are documented in the assessment framework.

Claim verificationPrompt-configured

The AI is instructed to distinguish between stated claims and verified evidence.

Output classificationApplication-enforced

Outputs are classified as assessment findings, not verified facts or professional opinions.

Automatic decisionsInterface-restricted

The demonstration has no capability to make commercial decisions or commitments.

Final reviewHuman-approval enforced

Assessment outputs require human review before any commercial use.

03

Controlled Pilot Preparation

INPUT

Customer problem statement, proposed scope, responsibilities, deliverables, success criteria and timeline.

PROCESS

Structured pilot-planning framework applied to the inputs. The system produces a draft pilot proposal covering scope, deliverables, responsibilities, risks and success criteria.

OUTPUT

Draft pilot proposal requiring commercial and legal review before use. Clearly labelled as a draft requiring professional review.

LIMIT — No agreement or customer commitment is created automatically. The output is a structured draft only. Commercial and legal review is required before the proposal is used in any negotiation.

CONTROLS AND ENFORCEMENT LEVELS

Proposal scopePrompt-configured

The planning framework constrains the proposal to the stated scope.

Legal languagePrompt-configured

The AI is instructed to avoid legally binding language and to flag items requiring legal review.

Automatic commitmentsInterface-restricted

The demonstration has no capability to create agreements or send proposals to third parties.

Output labellingApplication-enforced

All outputs are labelled as drafts requiring professional review.

Approval before useHuman-approval enforced

The proposal requires explicit human approval before any commercial use.

See these use cases in a private demonstration.

Request a guided walkthrough of any use case applied to your specific business context.

Demonstrations are available for qualified commercial and technical evaluators.