Experience layer
Mobile-first public site, partner onboarding flows, project browsing, report generation, and future authenticated dashboards.
Product & technical strategy
EcoConnect is a public-benefit transparency layer first. The architecture keeps project evidence, buyer reporting, and compliance controls separate from any future trading or payment capability.
Module overview
Modules are intentionally narrow. Each is implementable, testable, and reviewable inside the 24-month pilot window.
Searchable, standardized profiles for forestry, soil, blue carbon, energy, and engineered removal projects.
Structured workspace for verification artefacts, monitoring reports, methodology mapping, and registry linkage.
Transparent, deterministic scoring across additionality, permanence, leakage, safeguards, and retirement evidence.
Surface qualified projects to vetted buyers, funders, and grant programmes based on declared criteria.
Auditable purchase and retirement summaries with claims-language guidance and evidence links.
Structured intake for project developers, verification partners, funders, and public-sector stakeholders.
Role-based review queues, evidence updates, partner approvals, and audit trails for grant reporting.
Transactional capability is intentionally gated until legal, registry, and payments controls are signed off.
Deterministic, not vibes
The same inputs always produce the same score. Reviewers see the full breakdown — what is met, what needs review, and exactly how much each control counts.
EcoConnect · Diligence workspace
Pilot previewProject profile
Tanzania · VCS · 2024 vintage
Integrity
Adequate
Broadly sufficient. Clear residual gaps before buyer-facing reporting.
Weighted controls
Weight · Coverage
Buyer report output
Auditable purchase summary with retirement proof, claims-language guardrails, and evidence links — ready for ESG disclosure.
Admin readiness
Role-based review queues, partner approvals, and grant evidence exports — available post-pilot with full authentication controls.
System layers
The repository separates UI, editorial data, domain logic, validation, and future persistence so the team can add authentication and integrations without rewriting the public product.
Mobile-first public site, partner onboarding flows, project browsing, report generation, and future authenticated dashboards.
Next.js server-rendered pages, route handlers, validation modules, domain scoring logic, and future service boundaries.
Structured project profiles, evidence documents, due diligence assessments, user organisations, audit events, and grant document metadata.
Planned registry APIs, CRM, analytics, storage, identity, payments only after legal approval, and external verification workflows.