{"resourceId":"govai-factsheet-vendor-disclosure-study-202604","versions":[{"version":"external-0e7afbba86479d267c38039c0ed2a938ae6d37defb5388de218152b424301ff1","resource":{"id":"govai-factsheet-vendor-disclosure-study-202604","title":"Vendor disclosure study questions whether completed forms establish evaluation readiness","organization":"Blaine Kuehnert, Nari Johnson, Ravit Dotan and Hoda Heidari","sector":"Public-sector AI procurement","geography":"United States; local-government study with limited state transferability","publishedAt":"April 1, 2026 preprint","publicationDate":"2026-04-01","eventDate":null,"sourceName":"arXiv: Disclosure or Marketing?","sourceLabel":"Original academic preprint; document analysis and interviews","sourceUrl":"https://arxiv.org/pdf/2604.01332","evidenceClass":"academic-research","outcomeClass":"cautionary","topics":["data-security","governance-procurement","operating-model"],"finding":"Completed vendor FactSheets often lack the evidence needed for technical assessment.","sledRelevance":"Interpretation: state procurement teams can test this concern locally; city-centered findings do not establish state failure.","evidence":"Study combines 19 interviews and 39 FactSheets, using thematic analysis and expert rubric scoring resolved by consensus. It examines disclosure, not deployed accuracy or causal procurement outcomes.","architectureImplications":"Interpretation: turn unverified architecture statements into requests for system diagrams, version records and reproducible tests.","governanceImplications":"Interpretation: distinguish a completed intake form from a documented acceptance decision.","securityPrivacyImplications":"Interpretation: request evidence of tenant isolation, retention and incident handling through an appropriately protected review channel.","caveats":"Coalition-centered sample and embedded researchers limit generalization. No controlled baseline; proposed governance improvements were not experimentally validated.","streamIds":["state-government"],"roles":{"sales":"Interpretation: The buyer problem is assessing whether a proposed system fits a service when available descriptions leave important questions unanswered. Engage procurement, technical reviewers, privacy and the service owner. Ask what evidence would change the purchase decision and which claims cannot currently be tested. A bounded engagement could review one candidate's disclosures and build a prioritized evidence request. The value hypothesis is a clearer, more defensible decision process. Do not claim that a filled form proves safety, that every supplier is misleading, or that this study demonstrates savings. State use should be justified by the local procurement process.","engineering":"Interpretation: Fit is a review workflow linking each material claim to an artifact and a test. Prerequisites include access to a sandbox, version identifiers, test data rights and a named supplier contact. Inspect model and application boundaries, third-party dependencies and customer configuration separately. Use local representative inputs and adversarial cases to test unresolved claims; protect sensitive procurement material with role-based access. Proposed proof of value: a second reviewer can reproduce the decision-relevant tests and identify remaining unknowns. No particular model, cloud platform or on-premises stack is validated by this documentation study. Agent action permissions require additional execution tests.","delivery":"Interpretation: Give procurement an evidence register and assign a service owner to resolve open acceptance questions. Dependencies include technical review skills, supplier response time, legal review of confidential material and user participation. Train reviewers to distinguish missing information from demonstrated failure. Proposed acceptance criteria: every critical claim is tested or explicitly restricted, unresolved items have owners and deadlines, and a material supplier change reopens the relevant review. These are proposed local controls. Plan for recurring review capacity and escalation if evidence is unavailable. Risks include converting the register into another completion checklist or excluding smaller suppliers without proportionate requests."},"retrievedAt":"2026-09-14T03:02:46Z","enrichedAt":"2026-09-14T03:02:46Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: include accessible user testing and budget technical reviewer training; the study does not measure accessibility.","procurementImplications":"Interpretation: specify evidence delivery and retesting obligations before contract award.","operatingModelImplications":"Interpretation: maintain an accountable decision owner across procurement, deployment and renewal.","updateExplanation":"No matching URL, arXiv identifier or title in all 274 archived resources. Historical evidence backfill adds empirical scrutiny of disclosure practice, distinct from archived contract-policy analysis.","sourceVerification":{"openedUrl":"https://arxiv.org/pdf/2604.01332","referenceExcerpt":"None of the reported evaluations used publicly available datasets","promptVersion":"sled-research-v3.2","model":null,"basis":"agent-reported inspection"}}}]}