The working A prototype: use its controls to test the build question.
Test whether an AI vendor’s promises, evidence, controls and procurement answers are actually defensible.
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 021-A
AI Vendor Claim / Procurement X-Ray
Break a vendor promise into the evidence, scope, controls, and commitments a procurement decision can actually rely on.
SELECTED CLAIM / CL-01
CONDITIONAL
5 / 10 verification paths closed. Scope-specific verification is not a general endorsement or procurement approval.
X-RAY / Performance
Reduces review time by 40%
OPEN VERIFICATION PATHS
- Controls are demonstrated: Named owners can monitor, intervene, stop, correct, appeal, and preserve a record.
- Independent verification exists: A competent source not controlled by the vendor tested the relevant proposition and scope.
- Commitment is enforceable: The scoped answer survives into signed terms, audit rights, change notice, and exit duties.
- Failure has a remedy: The record names cure, suspension, termination, indemnity, or another proportionate recourse path.
- Corrections remain traceable: Contradictions, version changes, incidents, and corrected answers append to the evidence chain.
- Entity check · Build 011
- Vendor, product, model, version, hosting path, and subcontractor identities must not be conflated.
- Consequence check · Build 012
- Required evidence, review, control, and recourse rise with the consequence of the proposed use.
- Evidence chain · Build 020
- Sources, answers, decisions, contradictions, and corrections remain reconstructable.
Synthetic, client-local demonstration. No vendor, bid, personal information, security detail, or procurement response is submitted or retained. Export contains only this synthetic fixture. Do not enter confidential material. A real review requires competent procurement, legal, security, privacy, accessibility, finance, affected-community, and domain reviewers.