Access Layer

Arif is accessed through Qriib Business rather than a public standalone API. The public contract is the user experience: chat sessions, companion assistance, approvals, file upload, voice input, plan review, and rollback.

Responsibilities

The access layer coordinates:

• Authenticated Qriib users and their active sessions.
• Message submission and streaming responses.
• Session history, rename, star, delete, and export actions.
• File attachment upload and association with a message.
• Voice transcription and speech responses when enabled.
• Approval decisions for pending actions.
• Rollback requests for supported changes.

Authentication

Arif follows Qriib authentication. A user must be signed in unless a specific public documentation assistant is being used.

Authorization

Every business action is constrained by Qriib permissions and Arif safety policy. Users only see and use capabilities that are available to their account, role, plan, and enabled modules.

Public Guidance

For public integrations, use the supported Qriib product surfaces and administrator-approved connectors. Raw internal method names and deployment routes are intentionally not part of the public documentation.