Getting started

Open a case with a defensible boundary.

Start with the authority to review a legal entity, then let policy determine what proof is required and who must decide.

Before you create a case

Required inputWhy it existsExample
PurposePrevents evidence from being reused for an unrelated objective.Assess SME lending eligibility
Legal basisRecords the approved processing justification.Contract performance
SubjectLimits the current product boundary to a legal entity.Example Merchant LLC
JurisdictionSelects relevant policy and data-handling requirements.United Arab Emirates
RetentionDefines when the case becomes eligible for expiry or deletion.180 days
OwnerNames the person or integration accountable for the case.SME lending operations

Merchant onboarding path

Sales operations intake becomes a policy-bound case with document requests, screening checks, analyst review and a decision packet.

Your first merchant-eligibility case

  1. 1

    Create the case

    Use the workspace or Partner API. Clarivy derives tenant and actor authority from the authenticated session or service credential.

    Output: Case reference and request identifier

  2. 2

    Confirm the policy snapshot

    The active published merchant-eligibility policy is copied into the case with its version and compiled hash.

    Output: Frozen control plan

  3. 3

    Add evidence

    Upload an approved document, cite an official web source, or attach a result from a configured connector.

    Output: Source-cited evidence records

  4. 4

    Work the review queue

    Verify reliable proof, reject unsupported claims, or request a specific missing document.

    Output: Named review events

  5. 5

    Resolve the gates

    Record the rationale for exceptions and complete the required maker–checker steps.

    Output: Gate outcomes

  6. 6

    Export the packet

    Generate a packet containing policy, claims, sources, review actions, conflicts and decision lineage.

    Output: Reviewable evidence packet

Example case boundary

Case request
{
  "reference": "LOS-2026-000184",
  "title": "Merchant lending eligibility review",
  "purpose": "Assess the merchant against approved SME lending controls.",
  "use_case": "merchant_eligibility",
  "subject_name": "Example Merchant LLC",
  "subject_type": "legal_entity",
  "legal_basis": "contract_performance",
  "jurisdiction": "AE",
  "retention_days": 180
}

Authority fields stay server-controlled

The caller cannot choose a tenant, policy version, audit actor or review result. Clarivy derives those fields from the signed-in identity, service credential and published policy.

What good looks like

  • Every material claim points to an exact source or artifact.
  • Unresolved contradictions remain visible.
  • AI suggestions never become evidence silently.
  • The reviewer and rationale are named.
  • The policy version can be reconstructed later.
  • Retries do not create duplicate cases or messages.

Continue reading

Core concepts

Understand evidence, lineage, integrity hashes, policy snapshots and decision packets.