User-side Protection

Capture behavior evidence before user-side disputes become unprovable.

Use this path when your first need is to preserve user-facing AI behavior as traceable, verifiable records, then move toward responsibility review when a case requires stronger attribution.

TAL Chain Entry Point

Layer 2 Responsibility Attribution upgrade path starts here.

Free Evidence Intake captures behavior evidence and basic verification. Layer 2 Responsibility Attribution is a higher upgrade path for explicit closure, bound authority, declared responsibility, classification context, and stable trace continuity. This page marks the user-side path without turning the free intake into Layer 2 certification.

Commercial boundary: the free path is for intake and basic verification. L2 promote, responsibility-object reports, L2→L3 handoff packages, and Audit Workspace continuation are upgraded responsibility capabilities for formal review or pilot delivery.

Beyond evidence capture

CLARIXO is an upstream responsibility-object interface for AI decision systems. It helps turn system behavior into responsibility-bearing objects that downstream layers can test, anchor, verify, transport, admit, or enforce.

In TAL terms, CLARIXO operates at Layer 2 — Responsibility Attribution, making responsibility closure, authority coherence, attribution consistency, classification context, threshold status, and trace continuity observable before downstream handoff.

The current L2 path now supports a controlled responsibility-object loop: derive an L2 view from existing evidence, promote selected evidence into a separate L2 Responsibility Object, read the promoted object, and verify that its source evidence hash, schema, promotion policy, and mutation boundary remain intact.

This is the customer-facing User-side path. It does not require customers to understand internal demo systems or pass through the LLM-side runtime path first.

Free Evidence Intake

Generate a trial key and write user-facing behavior evidence for basic traceability and verification.

Basic Verification

Check retained evidence records, hash status, event identity, and readable behavior summaries before formal review.

Layer 2 Upgrade Path

Move beyond capture into responsibility attribution when closure, authority, and responsibility must be explicitly assessed.

Path clarity

Free intake first. Responsibility attribution later.

The first step is intentionally simple: capture behavior evidence and verify it. The Layer 2 path remains clearly marked as an upgrade path, not something silently included in the free intake.

1. Capture Use Free Evidence Intake to record user-facing behavior evidence.
2. Verify Confirm that the record is readable, traceable, and integrity-checkable.
3. Upgrade Move into Layer 2 Responsibility Attribution when formal closure and responsibility are needed.