Skip to content

Eco Rules Catalog

The Eco Rules Catalog is a SITM-owned standard for identifying, describing, and organizing software inefficiency.

🚀 v0.3.0 — Infrastructure + Scanner Model

The Eco Rules Catalog now includes infrastructure-level inefficiencies.

New in this release

  • Infrastructure category (INF)
  • Docker, Compose, and Kubernetes rules
  • Cleaner scanner integration model

Why it matters

Waste doesn’t stop at code.

It lives in: - images - manifests - scaling behavior - defaults

Making it visible is the first step to reducing it.

What this is

The catalog provides:

  • a shared language for software waste
  • a canonical rule model
  • controlled vocabulary through the registry
  • validation and reproducibility
  • a foundation for tools, education, and certification

In plain English: it helps teams name waste, find waste, and fix waste more consistently.

Because waste is a bug.

Why this matters

Software waste often hides in plain sight.

A little extra polling here. A little oversized payload there. A little retry loop that no one revisits.

At small scale, these things can look harmless.

At real scale, they become:

  • cost
  • latency
  • energy use
  • environmental impact
  • fragility

The Eco Rules Catalog exists to make those patterns visible and actionable.

Start here

New to the catalog?

Read Start Here for the fastest path into the standard.

Core documents

Source of truth

The machine-readable source of truth is:

  • catalog/rules/...
  • catalog/registry.json
  • catalog/schema/...

Generated artifacts include:

  • catalog/master.json
  • docs/catalog/...

catalog/master.json and docs/catalog/... are generated and should not be edited manually.

For contributors

If you want to contribute safely, start with:

For tool builders

If you want to integrate against the catalog, start with:

Releases

  • See v0.3.0 for the current release
  • See v0.2.0 for the first validated standard release.

Because waste is a bug.