Terms for using RIVAL
Use this reference when a product term is unfamiliar. Availability statements describe the product as of 15 August 2026. A planned term explains direction. It does not mean that the feature is available now.
Read How the platform works for the complete path from role-based practice to evidence.
Service and people
Operator
The professional firm that provides the service to client organizations. It can be a consultancy, IT or security partner, accountant, or trainer. The EU AI Act uses operator as a broader legal umbrella for several regulated roles. Operator accounts and their first owner are available now.
Operator owner
The person who controls one operator account, its client portfolio, branding, billing, and seats. The first operator-owner account and current portfolio controls are available now.
Operator member
A consultant seat inside an operator. A member works only in client organizations to which the member has access. Operator members are planned for a later enterprise release.
Operator console
The operator's overview across its client organizations. It answers where clients need attention. The current operator dashboard is available now; the complete console is planned for the first release.
Client organization
A business served by an operator. It is the main boundary for people, policies, evidence, and scores. Creating and entering a client organization is available now.
Organization administrator
A person at a client organization with delegated responsibility for people and policy management. The role boundary is available now; its complete management journeys are planned for the first release.
Organization template
An operator-owned configuration that can reuse role profiles, policy sets, and assignment schedules without copying person data. Templates are planned for a later enterprise release.
Person
An employee, contractor, or other AI user inside a client organization. A person is the unit of readiness. Person management is available now.
Workspace
An optional group of people inside a client organization, such as a team or department. Workspace storage exists; workspace management is not yet available.
Tenant
The authorization and data boundary for an operation. An operator owns portfolio data. A client organization owns its people and evidence. Tenant isolation is available now.
Mapping and policy
AI map
The living inventory of AI use in one client organization. It is the organization's AI system inventory. It covers AI tools, people, use cases, data sensitivity, policies, and classifications. The AI map is planned for the first release.
AI tool
An AI system used or reviewed in a client organization, such as a chatbot, copilot, or internal assistant. AI tool management is planned for the first release.
AI tool classification
The review state of one AI tool in one organization, with data-sensitivity notes. The states are approved, unreviewed, and restricted. AI tool classification is planned for the first release.
Role profile
The risk profile for a role in one client organization. It records tools, data classes, possible consequences, and required practice. Role profiles are planned for the first release.
Role track
The role-specific set of scenarios built from shared principles. The launch library covers common employee, management, people, communication, and technical work. Role tracks are planned for the first release.
Policy
A governed document that states expectations for AI use in one client organization. Policies are planned for the first release.
Policy version
One fixed revision of a policy with a change summary, effective date, and acknowledgement state for each person. Policy versions are planned for the first release.
Acknowledgement
A person's recorded confirmation of one policy version. A material policy change also requires a comprehension check. Acknowledgements are planned for the first release.
Comprehension check
One or two questions that check understanding of a material policy change before the acknowledgement records. Comprehension checks are planned for the first release.
Pulse
A monthly check-in of about 30 seconds that helps keep the AI map current. Pulses are planned for the first release.
Practice and content
Assignment
A scheduled unit of work for a person. It can be a drill, acknowledgement, or pulse check-in. Assignments are planned for the first release.
Drill
A realistic decision that takes about 30 seconds to 3 minutes. It contains a situation, decision options, direct feedback, and a transferable principle. Drills are planned for the first release.
Principle
A behavioral rule that transfers between situations, such as checking important claims produced by AI. Principles and the launch content pack are planned for the first release.
Scenario
One authored content unit. It connects a principle, risk pattern, situation frame, role context, tool context, and consequence. One drill renders one scenario. Scenarios are planned for the first release. Scenario authoring does not mean that AI generates them.
Content pack
A named set of principles and scenarios. AI Readiness Core starts a growing library for common work situations. Its links identify affected drills after a source change. Content packs are planned for the first release.
Mastery
A person's demonstrated judgment for one principle in the person's role context. Strong mastery reduces repetition. Struggle increases targeted practice. Mastery is planned for the first release.
Freshness
How current a score, acknowledgement, classification, or practice state is. Freshness is planned for the first release.
Decay
The configured reduction of freshness over time. Decay prompts the smallest useful intervention. Decay is planned for the first release.
Refresh
The smallest useful action after decay or a change, such as one question, drill, or acknowledgement. Refreshes are planned for the first release.
Evidence and method
Evidence event
One append-only record of a meaningful action: who did what, when, in which tenant, and under which policy or assignment. The evidence-event foundation is available now. Drill-answer evidence is planned for the first release.
Evidence ledger
The append-only store of evidence events for one client organization. Normal product behavior does not update or delete a written event. The evidence-ledger foundation is available now.
Evidence pack
An export for a selected period and scope, with a PDF and data files. It reports what the organization did. Evidence packs are planned for the first release. They are not a certificate or a compliance guarantee.
Readiness score
One client-organization score with visible components. It describes operational confidence, not legal compliance. Readiness scores are planned for the first release.
System audit log
The platform-owned record of privileged and security-relevant actions. It stays separate from client evidence. System audit logging is available now.
Compliance theater
Work that produces completion artifacts without improving readiness. The platform is designed to favor current practice and evidence instead. This is a product doctrine, not a software feature.
RIVAL method
The service loop: Reveal, Identify, Verify, Assemble, Loop. It connects discovery, priorities, practice, evidence, and review. The method is product guidance, not a separate control.
RIVAL review
The recurring operator-led review of a client organization's score, AI map, and evidence. It is a planned service ritual, not a software feature.
Terms with their own journey
These terms have instructions in the article that owns the current behavior:
- Account menu: profile, settings, and sign out. See Manage your account.
- Operator invitation: an expiring, single-use invitation for the first operator owner. See Accept an operator invitation after you sign in as the invited actor.
- Tenant context: the organization or operator where you choose to work. See Choose where to work after you sign in.
- Language, time zone, date notation, time notation, and number notation: saved presentation settings. See Manage your account after you sign in.