Skip to content

Latest commit

 

History

History
191 lines (172 loc) · 15.1 KB

File metadata and controls

191 lines (172 loc) · 15.1 KB

Documentation Index

CarbonOps-Parser is a public climate-tech data infrastructure project for auditable carbon accounting source ingestion and validation. It documents Python, .NET, and PostgreSQL boundaries for public emission factors from GHG Protocol, DEFRA/DESNZ, and IPCC EFDB without claiming production carbon-accounting correctness.

Start Here

Runtime Runbooks

  • Python Ingestion Local Runbook - local Docker PostgreSQL ingestion runbook for the packaged Python path.
  • .NET Runtime Docs - .NET Worker Service path and parity-oriented runtime notes.
  • Architecture - Python, .NET, PostgreSQL, validation, diagnostics, and dry-run boundaries.
  • Examples - deterministic local examples and fixture entry points.

Database Model And PostgreSQL Startup

Phase 2 Roadmap And Review Gate

Contribution, Support, And Security

  • Contribution Guide - issues, features, forks, branches, pull requests, validation, secrets, artifacts, and maintainer-only merge policy.
  • Support Policy - support boundaries and safe information-sharing guidance.
  • Security Policy - responsible disclosure and no-secret expectations.
  • Issue Templates - bug reports, feature requests, documentation requests, and production-readiness questions.
  • Pull Request Template - PR checklist for scope, validation, runtime impact, PostgreSQL impact, docs, secrets, artifacts, and production-ready claims.

Public Discoverability

Repository topics cannot be configured through repository files, but maintainers can use these suggested GitHub topics when publishing or reviewing the public repository:

carbon-accounting, emission-factors, carbon-emissions, ghg-protocol, defra-desnz, ipcc-efdb, climate-tech, data-ingestion, python, dotnet, postgresql, postgres, etl, data-validation, open-source

Search-friendly project description:

Auditable public carbon emission factor ingestion and validation for climate-tech data infrastructure, with Python and .NET contracts, PostgreSQL readiness, non-destructive dry runs, and documented support boundaries for GHG Protocol, DEFRA/DESNZ, and IPCC EFDB.

Discovery wording should stay conservative. The repository may describe source ingestion, parsing, validation, diagnostics, dry-run previews, and reviewable PostgreSQL readiness. It should not claim production carbon-accounting correctness, compliance correctness, legal correctness, source-owner correctness, or factor correctness.

Full Map