Building a Carbon Asset Traceability Platform from Zero to One
Domain boundaries, tenant isolation and lifecycle modeling across green-power verification, issuance, trading and retirement.
Decide what must be traced
A traceability platform is not a central collection of every log. The important records are business events that prove the origin, state and ownership of an asset: power verification, issuance, packaging, trading, splitting and retirement.
For the initial design, I defined the asset lifecycle and the business evidence behind each event before shaping the database. This keeps tables from growing around a temporary screen or API.
Multi-tenancy is more than a tenant column
Tenants form a hierarchy and contain departmental boundaries. Authorization therefore combines tenant trees, department scope, data ownership and the operations available to a role.
- Make tenant isolation a default condition of data access.
- Define what a parent tenant can see rather than inheriting everything.
- Treat visibility before and after an asset transfer explicitly.
- Reuse the same authorization rules in core queries and exports.
A reusable emissions calculation model
Production processes, emission factors and formulas continue to change. Separating rules, parameters and workflow lets the calculation engine grow without duplicating an entire process for every new case.
From documentation to production troubleshooting
Power verification, asset packaging and ESG questionnaires all require product and engineering to share the same meaning. Requirement documents support review, but they also provide critical context when diagnosing a blocked production flow.
The lasting lesson is that traceability comes from clear domain events, stable data ownership and consistent permission boundaries—not simply from collecting more logs.