CLARIXO
Audit Workspace Manual

Confirm evidence, open a case, define scope, review grouped evidence, and export a structured case packet.

This manual explains how to use CLARIXO Audit Workspace after the evidence path is already working. It is written for implementation owners, reviewers, operators, and teams that need a disciplined case-review workflow around user-facing AI behavior.

Open Audit Workspace Read Protocol Read Evidence Manual Back to Docs
Before You Begin

Do not start here unless evidence is already landing in CLARIXO.

Project Context
Make sure a valid CLARIXO project context already exists and can anchor the case review.
Application Identity
Use a stable application identifier that matches the evidence source you intend to review.
Evidence Availability
Before opening a case, confirm that the target evidence already exists and can be read back under the intended project, application, session, or time scope.
Minimum Workflow

The narrowest complete path is confirm → open → scope → review → export.

Step 1
Confirm that the target evidence already exists inside CLARIXO under the expected project and application context.
Step 2
Open a new case in Audit Workspace and give it a clear scenario-based title.
Step 3
Define a narrow initial evidence scope using project, application, optional session, and recorded-from / recorded-to anchors.
Step 4
Review grouped evidence in Case Detail and preserve reviewer context through summary and notes.
Step 5
Generate a formal export packet when the case is ready for downstream use.
Case Title

Use a real scenario title

Avoid vague internal shorthand. A good case title should reflect the review scenario clearly.

Scope

Keep the first scope narrow

A small, bounded case closes faster and produces stronger export quality than an oversized first case.

Open A Case

Define a stable initial evidence scope before deeper reviewer workflows begin.

Project ID
Use the exact project context tied to the evidence source. Do not switch project identity mid-review.
Application ID
Use one stable application anchor whenever possible. Do not mix unrelated application contexts into a single first case.
Session ID
Use a session identifier when the case is centered on one conversation or one interaction stream.
Recorded From / To
Prefer a tight, bounded time window. For formal review quality, second-level precision is strongly preferred.
Review In Case Detail

Case Detail is the main working page for grouped evidence review.

Confirm Identity
Check that case title, project, application, and scope anchors match the intended review target.
Inspect Continuity
Use grouped evidence reading to understand the event sequence, boundary, and overall continuity inside the selected review window.
Inspect Context Admissibility
When available, review the context admissibility summary carried from the evidence record, including overall state, slice summary, pollution flags, runtime source, runtime scope, clean context hash, and recomposition posture.
Preserve Context
Record reviewer summary and notes without mutating the underlying evidence payload.
Summary And Notes

Use scenario-selectable formal wording rather than one forced tone.

Neutral Review

Default style for internal review

Use a factual tone that explains the case, the scope, the current evidence continuity, and the current review status without overstating certainty.

Audit / Legal

Restrained evidence-centered style

Use this when the output may be consumed by audit, legal, compliance, or responsibility-sensitive review functions.

Client Delivery

Professional external explanation style

Use this when the review packet is prepared for structured external communication and delivery-oriented explanation.

Default Rule

Start from Neutral Review

Unless there is a specific downstream need, Neutral Review should remain the default wording style.

Example Neutral Summary

A formal summary should explain the review scope without claiming more than the evidence supports.

This case was opened to review a bounded set of user-facing AI behavior records associated with the specified project, application context, and selected evidence window. Based on the scoped evidence currently included in this case, the reviewed interaction sequence can be reconstructed in a stable and traceable manner. The available records provide sufficient continuity for initial review within the limits of the defined case scope.

Export

Use export as the structured case packet for downstream review.

What Export Preserves
A structured export should preserve case identity, evidence scope, reviewer context, and stable continuity between the case record and the evidence record.
Typical Uses
Use export packets for internal review circulation, client delivery, audit preparation, legal-support preparation, or responsibility-sensitive investigation workflows.
Field Discipline
Maintain stable project continuity and do not let export links or delivery pages lose the original project anchor.
Lessons From A Live Integration

The recent TGTRACING integration surfaced five practical rules worth preserving.

Project Continuity
Case open, case detail, note writing, export creation, and export-view navigation should remain tied to the same project context.
Narrow Scope
A smaller evidence window produces a more stable first review case and improves export clarity.
Time Precision
Second-level recorded-from and recorded-to precision materially improves formal review quality.
Template Flexibility
Neutral Review, Audit / Legal, and Client Delivery should remain separate selectable wording styles rather than being collapsed into one forced tone.
Review Layer Only
Audit Workspace works best when evidence is already stable before the formal case is opened.
Common Mistakes

Avoid broad cases, weak identity continuity, and evidence-first violations.

Opening Too Early
Do not open a formal case before confirming that evidence already exists and is readable.
Broad First Scope
Do not treat the first case as a historical dump of everything. Start narrow and stable.
Losing Identity
Do not let project, application, session, or export continuity drift during the review chain.
Overstating Conclusions
Keep summaries and notes factual, professional, and bounded by the evidence actually in scope.
Final Operating Rule

Do not use the workspace to invent evidence structure. Use it to organize, review, explain, and export evidence that already exists.

Open Audit Workspace Read Protocol Back to Docs