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 (8/145)
Filters: domain BioMainstream; status all.
WDPA protected-area data is accurate for Ghana screening context
Source: WDPA Protected Planet — Ghana protected area layer (2026-01-01) · verified 2026-05-29 · re-check by 2026-11-29
If wrong: Protected-area intersection and proximity logic in trigger groups depends on this dataset being current.
Verify against official Ghana Forestry Commission gazettement records before statutory conclusions.
Hansen GFC tree-cover loss signals are disturbance indicators, not proof of illegality
Source: Hansen Global Forest Change v1.12 — methodology note (2026-01-01) · verified 2026-05-29 · re-check by 2026-11-29
If wrong: Core forest-change interpretation. All trigger groups and risk bands treat loss as a screening signal.
Tree cover is not statutory forest. Loss may include plantation harvest, agriculture, fire, mining, infrastructure, natural disturbance, or data artefacts.
Ramsar site boundaries are current for Ghana
Source: Ramsar Sites Information Service — Ghana designated sites (2026-01-01) · verified 2026-05-29 · re-check by 2026-11-29
If wrong: Wetland/water sensitivity triggers depend on Ramsar boundary accuracy.
Official Ramsar data. Re-check if new designations or boundary revisions are announced.
ESA WorldCover 2021 land-cover classification is suitable for dominant land-use context
Source: ESA WorldCover 2021 product specification (2026-01-01) · verified 2026-05-29 · re-check by 2026-11-29
If wrong: Land-use change risk triggers depend on WorldCover class composition.
May misclassify mixed agroforestry, young secondary forest, or recent land-use change. Cross-check with field context.
SiteSense evidence classification separates public data, client claims, community contributions, and analyst conclusions
Source: EIRAS SiteSense evidence architecture (2026-01-01) · verified 2026-05-29 · re-check by 2026-11-29
If wrong: Decision quality depends on correctly classifying evidence sources before routing or banding.
Community contributions, local claims, and field observations must never be mixed with official datasets or analyst conclusions without review.
BioMainstream review checklist must be completed before client-facing recommendations
Source: EIRAS BioMainstream review protocol v1 (2026-01-01) · verified 2026-05-29 · re-check by 2026-11-29
If wrong: HITL gate condition. All 7 checklist items must be checked or marked not_applicable.
Client-facing reports are watermarked PRELIMINARY until review status is reviewed or converted.
BioMainstream decision routes are advisory only and require specialist review for statutory or investment conclusions
Source: EIRAS risk control policy (2026-01-01) · verified 2026-05-29 · re-check by 2026-11-29
If wrong: Risk control. No trigger group or decision route constitutes statutory approval, legal opinion, or investment recommendation.
Explicit disclaimer required on every client-facing output.
Community contributions remain unverified intelligence until GAB reviewer approval
Source: EIRAS community data governance policy (2026-01-01) · verified 2026-05-29 · re-check by 2026-11-29
If wrong: Safeguard for community data. Community contributions must not flow into client outputs without verified_by_gab status.
Sensitive community identities, grievances, land claims, and customary details must not be exposed publicly.
Register a new assumption
docs/projects/2026-05-28_EIRAS-roadmap-use-cases-15-17-and-validation.md