The working A prototype: use its controls to test the build question.
Test whether an organization can actually implement an AI use safely and operationally.
RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.
This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.
Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.
The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.
BUILD 025-A
AI Implementation Readiness X-Ray
Test whether an organization can actually implement an AI use safely and operationally.
NOT READY
2 blocking findings
People
Owner: Clinical operations lead
Authority: May assign reviewers and pause the pilot
Evidence: Role matrix documents reviewer coverage for every pilot session
Evidence record: PEOPLE-01
Validation: Capacity walk-through against twenty synthetic cases
Gap: No open gap in this fixture
Data
Owner: Data steward
Authority: May deny access and require dataset correction
Evidence: Dataset inventory defines the synthetic-data and access boundary
Evidence record: DATA-01
Validation: Inventory reconciled against the pilot input schema
Gap: Drift baseline is not approved
Workflow
Owner: Service owner
Authority: May change handoffs and restore the manual fallback
Evidence: Current-state map records handoffs, review, fallback, and release authority
Evidence record: FLOW-01
Validation: Tabletop walkthrough including fallback and boundary breach
Gap: No open gap in this fixture
Controls
Owner: Not assigned
Authority: Not defined
Evidence: Not provided
Evidence record: Not linked
Validation: Not tested
Gap: Stop authority and incident route are not assigned
Evidence
Owner: Evaluation lead
Authority: May reject the test result and require a new protocol
Evidence: Task-specific validation protocol defines material-error seeds
Evidence record: EVAL-01
Validation: Protocol review against the bounded use and success measure
Gap: Independent result is pending
Inherited assessment records
- Build 012: CONTROLLED USE · 012-SYNTH-CTRL-01
- Build 013: WORKFLOW SCANNED · 013-SYNTH-FLOW-01
- Build 021: NOT ATTACHED · record missing · Vendor claim verification record is not attached.
Blocking findings
- Build 021: provide a traceable assessment ID, engine version, outcome, and review date.
- Build 021: inherited assessment is not closed without unresolved gaps.
Boundary: title, job, B-Web sentence, and lineage are frozen canon. The fixture, rubric, and thresholds are derived. Evidence IDs are synthetic demonstrations, not verified real-world records. Runs client-locally; enter no real or confidential data.