Shirasu Evidence Room

This is a demo Evidence Room for a fictional company called Acme AI. It shows what an AI Evidence Review intake looks like across the five governance categories.

Acme AI

Customer Response Copilot

enterprise customer AI readiness review

Review lens
enterprise customer AI readiness review
Handling mode
Enhanced Confidential Handling
Status
Intake Open

Checklist overview

Review categories

Reviewer questions

Workflow basics

Keep the workflow context accurate so contributors and reviewers are working from the same scope.

Back to category overview
Company
Acme AI
Primary contact
Mira Chen (mira.chen@acme.example)
Review lens
enterprise customer AI readiness review
Handling mode
Enhanced Confidential Handling
Read-only demo
This public demo is read-only. You can inspect the workflow, but changes are disabled for demo visitors.

Category 1

Workflow Scope & AI Use

What AI workflow is in scope, and how is AI used within it?

Helpful evidence may include workflow description, process map, system diagram, data-flow note, AI tool/vendor/model list, product screenshots, prompt or instruction summary, retrieval/source description, user roles, customer-facing description, architecture notes, dependency list, launch or rollout notes.

Submittedpartial
No unresolved reviewer questions

Category 2

Authorization & Limits

What is it authorized to do, and what limits apply?

Helpful evidence may include approved use-case description, scope statement, operating limits, prohibited-use list, data-use rules, output-use rules, human-review requirements, approval record, risk acceptance note, launch decision record, change-control rule, escalation or pause authority, customer-facing disclosure, internal policy or standard.

Submittedpartial
No unresolved reviewer questions

Category 3

Evaluation & Readiness

What evidence shows it is fit for that authorized use?

Helpful evidence may include evaluation plan, test plan, test results, red-team or adversarial testing summary, prompt/output samples, representative case set, issue log, acceptance criteria, launch checklist, release gate, readiness memo, subject-matter expert review notes, known limitations, residual risk note, sign-off record, remediation record.

Clarification requestedpartial
Awaiting client: 1

Category 4

Operational Monitoring & Change Control

How do we know it stays within its limits over time?

Helpful evidence may include monitoring plan, logs or log summaries, dashboard screenshots, review cadence, alert rules, issue/ticket process, human review queue, feedback process, override records, complaint records, change log, release notes, prompt/version history, model/vendor update review, periodic review notes, owner responsibilities.

Submittedpartial
No unresolved reviewer questions

Category 5

Failure Handling & Escalation

What happens when it fails, causes harm, or exceeds its limits?

Helpful evidence may include AI-specific incident procedure, general incident process with AI addendum, escalation matrix, severity criteria, pause/rollback procedure, customer communication process, support ticket workflow, issue intake process, remediation tracker, incident review notes, postmortem template, prior incident or near-miss records, root-cause analysis, retesting record, workflow change record.

Submittedweak
No unresolved reviewer questions

Reviewer questions

Awaiting client: 1
Back to category overview