EcoIQ Certification & Trust Badge Engine
Show readiness, verification and trust status through clear badges.
EcoIQ Certification & Trust Badge Engine converts evidence, review, MRV, finance, governance and public-reporting status into clear trust badges. It helps investors, governments, suppliers, sponsors, communities and internal teams quickly understand whether a project is draft, evidence-ready, finance-ready, expert-reviewed, MRV verified, public-summary approved or blocked by missing evidence.
Core purpose: Make EcoIQ trust status visible, explainable and evidence-backed.
Connected EcoIQ Modules
Knowledge Graph & Relationship Map
Exposes badge nodes and relationships across the relationship graph.
Frontend Experience & Google Stitch Design System
Defines how badges are displayed across every screen.
Impact MRV Layer
Supplies MRV status feeding the MRV badge category.
Governance & Expert Review Board
Supplies reviewer decisions feeding the governance badge category.
Data Room & Evidence Vault
Supplies evidence completeness feeding the evidence badge category.
Public Trust & Impact Portal
Publishes only badges approved for public display.
Institutional Finance Engine
Supplies finance readiness feeding the finance badge category.
Supplier & Funding Marketplace
Supplies due diligence status feeding supplier/funding badges.
Portfolio & Country Transition Atlas
Surfaces badge status across country and portfolio views.
Command Centre
Surfaces badge summaries across the live project pipeline.
Security, Privacy & Compliance Centre
Enforces who may view or approve which badges.
AI Agent Operations Console
Shows which agent proposed or drafted a badge.
Product Analytics & KPI Engine
Tracks badge issuance and completion as platform KPIs.
Microsoft Ecosystem Core Stack
Provides the building blocks Microsoft-readiness badges describe.
Maqasid/Mizan ethical scoring
Supplies the ethical review status behind governance badges.
No Harm Gate
Blocks badge issuance where unresolved risk remains.
Badge Categories
Badges are readiness/status labels, not formal certification unless separately obtained.
Rules: Evidence Strong requires baseline evidence, relevant documents, timestamped files and linked asset/project records.
Rules: MRV Verified requires before/after evidence, measurement or documented proxy, evidence quality review and human approval.
Rules: Finance Ready requires CAPEX/OPEX assumptions, payback logic, risk notes, evidence quality and governance review.
Rules: Expert Reviewed requires assigned reviewer decision, timestamp, evidence version and audit trail.
Rules: Public Summary Approved requires MRV support or clear estimated label, privacy check, consent where needed and human approval.
Rules: Supplier Approved requires human approval and relevant due diligence notes.
Important: Do not claim Microsoft certification or partnership unless actually obtained. Use "ready" or "designed to integrate with".
Rules: No Harm Gate Passed requires evidence, risk review, human approval and no unresolved high-risk alerts.
Badge Lifecycle
Badge Dashboard Cards
Badge Table Fields
Badge status levels
Example Project Badge Sets
Boiler House #3 Modernisation
Factory Compressed Air Optimisation
Village Clean Heating Pilot
UK SME Efficiency Portfolio
Badge Evidence Requirements
Every badge should explain:
- What it means
- What evidence is required
- Who can approve it
- Whether it can be public
- Whether it expires
- What blocks it
- What next action unlocks it
Public Badge Rules
Public badges can be shown only if
- Public summary approved
- Sensitive data redacted
- Consent recorded where needed
- MRV/estimate label is clear
- Sponsor name approved if shown
- No Harm Gate checked
Private badges remain internal if they include
- Financial models
- Supplier due diligence
- Sensitive industrial data
- Personal/community data
- Unresolved expert review comments
Badge Revocation Rules
A badge can be revoked or downgraded if:
- Evidence is found weak
- Consent expires
- MRV data is corrected
- Expert review is reversed
- Supplier due diligence fails
- Public claim becomes unsupported
- Project conditions change
- Security/privacy concern appears
Frontend Integration
Trust badges should be visually reusable across
Frontend display rules
- Use clear badge colours
- Separate draft from verified
- Separate estimated from MRV verified
- Show tooltip with evidence requirement
- Show linked evidence and approval
- Never make unverified badges look certified
- Never imply Microsoft certification unless actually obtained
Knowledge Graph Integration
The Knowledge Graph should use badge nodes and relationships
PROJECT_HAS_BADGEBADGE_REQUIRES_EVIDENCEBADGE_APPROVED_BY_REVIEWBADGE_BLOCKED_BY_RISKBADGE_VISIBLE_IN_PUBLIC_PORTALBADGE_REVOKED_DUE_TO_EVIDENCE_CHANGE
Graph should show
- Which projects are Finance Ready
- Which projects are MRV Verified
- Which badges are blocked
- Which evidence unlocks badges
- Which badges are public-safe
- Which badges require human approval
Amanah Autopilot for Trust Badges
Amanah Autopilot can run overnight and:
- Detect projects ready for new badges
- Flag badges blocked by missing evidence
- Identify expired badges
- Downgrade unsupported claims to Needs Verification
- Prepare badge review queue
- Suggest finance-ready or sponsor-ready projects
- Prepare morning trust status briefing
Morning briefing example: "Overnight, 4 projects became Finance Ready, 2 public summaries need consent, 1 MRV badge is blocked by missing after-data and 3 Data Rooms are now complete."
Microsoft Integration
- Microsoft Fabric for badge metadata
- Power BI for trust badge dashboards
- Teams for badge approval workflows
- SharePoint for evidence pack links
- Power Automate for expiry/review alerts
- Dynamics 365 for investor/customer badge status
- Security/Compliance Centre for permission checks
Use careful wording: "designed to integrate with" or "can use", not "Microsoft certified".
No Harm Gate for Badges
Before issuing a badge, check:
- Is the evidence strong enough?
- Is the badge meaning clear?
- Could the badge be misunderstood as formal certification?
- Is human approval required?
- Is public display allowed?
- Is consent recorded?
- Are financial, environmental and impact claims supported?
- Is Islamic finance or Maqasid/Mizan wording reviewed?
- Is the badge expiry/review period defined?
- Can every badge claim be traced to evidence?
Safety and Governance
- EcoIQ trust badges are internal readiness and evidence-status labels unless formal certification is separately obtained.
- Do not claim third-party certification, Microsoft certification, Shariah certification or regulatory approval unless actually granted.
- MRV Verified means verified according to EcoIQ evidence workflow, not necessarily external audit unless stated.
- Maqasid/Mizan is ethical decision-support, not a fatwa.
- Public badges require consent, privacy review, evidence support and human approval.
- Badges must be downgraded or revoked if evidence changes.