EIRAS · Use Case 14
Assumptions & Evidence Validation Register
Every factual claim that feeds a client-facing EIRAS output — a law, a reporting obligation, a figure, a threshold, a methodology — is logged here with its source and verification status. The rule: nothing reaches a client as “fact” unless it is verified here and current. Built after the CLICOM fact-check found a ~45% citation error rate in agent-drafted content.
Client-readiness by domain
A domain is clear to put in front of a paying client only when every registered assumption in it is verified and current.
Regulatory (UC15)
Clear21/21 verified
MEA Reporting (UC16)
Blocked18/77 verified · 1 re-check · 58 unverified
ESG / Emissions (UC17)
Clear6/6 verified
BioMainstream
Clear8/8 verified
ReportBridge
Clear8/8 verified
ResourceMap
Clear6/6 verified
Green Carbon
Clear8/8 verified
ConsentTrack
Clear6/6 verified
Efficiency
Clear4/4 verified
CLICOM
Clear1/1 verified
59 claim(s) not client-ready
These must be resolved before the relevant module ships to a client.
Show all not-client-ready claims- Needs re-checkUnder CBD COP decision 15/6, Ghana must submit its 7th National Report to the Convention on Biological Diversity by end February 2026, and u…reportbridge
- UnverifiedCITES Annual Report field "Permits issued and refused" (C) is partial for CITES reporting. File held but not extracted. Source: Forestry Com…reportbridge
- UnverifiedCITES Annual Report field "Legislative and administrative measures" (B) is partial for CITES reporting. File held but not extracted. Source:…reportbridge
- UnverifiedCITES Annual Report field "Annual trade in CITES-listed species" (A) is partial for CITES reporting. File held but not extracted. Source: Fo…reportbridge
- UnverifiedRamsar NR field "Wetland restoration and rehabilitation" (S4) is partial for Ramsar reporting. File held but not extracted. Source: Forestry…reportbridge
- UnverifiedRamsar NR field "Community engagement and traditional knowledge" (S4) is partial for Ramsar reporting. File held but not extracted. Source: …reportbridge
- UnverifiedRamsar NR field "Wise use policies and practices" (S4) is partial for Ramsar reporting. File held but not extracted. Source: Forestry Commis…reportbridge
- UnverifiedRamsar NR field "Threats and pressures on Ramsar Sites" (S3) is partial for Ramsar reporting. File held but not extracted. Source: Forestry …reportbridge
- UnverifiedRamsar NR field "Ecological character of Ramsar Sites" (S3) is partial for Ramsar reporting. File held but not extracted. Source: Forestry C…reportbridge
- UnverifiedRamsar NR field "Ramsar Site designation status" (S2) is partial for Ramsar reporting. File held but not extracted. Source: Forestry Commiss…reportbridge
Register (6/145)
Filters: domain ConsentTrack; status all.
Event logs store metadata (type, date, venue, participant count, language) but do not store attendee names, contact details, signatures, or sensitive testimony.
Source: GAB data-governance sprint limit, 2026-05-29 (2026-05-29) · verified 2026-05-29 · re-check by 2026-12-01
If wrong: Protects community member PII and maintains sprint-limit discipline.
Attendee registers and detailed minutes must remain outside the OS until a full governance-vault model is approved.
Sync from SiteSense evidence to ConsentTrack profiles and events requires human reviewer confirmation; automated signal detection is directional only.
Source: GAB EIRAS operating protocol, 2026-05-29 (2026-05-29) · verified 2026-05-29 · re-check by 2026-12-01
If wrong: Ensures automated routing does not bypass reviewer judgment for sensitive community-facing work.
Reviewers must confirm that signal matches are relevant before creating events or grievance records.
ConsentTrack data must not be used as the sole basis for investment, lending, or regulatory decisions without independent legal and social review.
Source: GAB risk policy, 2026-05-29 (2026-05-29) · verified 2026-05-29 · re-check by 2026-12-01
If wrong: Prevents over-reliance on OS preparation records for material decisions.
All ConsentTrack outputs must carry a disclaimer referencing this assumption.
Readiness checklist status reflects reviewer assessment of preparation steps, not field verification of community views or consent.
Source: GAB EIRAS sprint definition, 2026-05-29 (2026-05-29) · verified 2026-05-29 · re-check by 2026-12-01
If wrong: Distinguishes desk preparation from field-verified community engagement.
A checklist marked complete means preparation steps are documented, not that community approval has been obtained.
ConsentTrack profiles and event logs are preparation and readiness records only. They do not constitute proof of FPIC, community consent, or legal authority to proceed.
Source: GAB EIRAS sprint definition — ConsentTrack starter-pack scope, 2026-05-29 (2026-05-29) · verified 2026-05-29 · re-check by 2026-12-01
If wrong: Prevents legal over-reach of OS records into statutory FPIC certification.
Any client-facing use must be accompanied by explicit language that these are preparation records, not approval documents.
Grievance records store category, reference code, status, and resolution path but do not store complainant identities or sensitive testimony.
Source: GAB data-governance sprint limit, 2026-05-29 (2026-05-29) · verified 2026-05-29 · re-check by 2026-12-01
If wrong: Protects vulnerable complainants and maintains ethical safeguard discipline.
Detailed grievance narratives with identities must remain outside the OS until a full governance-vault model is approved.
Register a new assumption
docs/projects/2026-05-28_EIRAS-roadmap-use-cases-15-17-and-validation.md