Some mix of product, support and eng decides how refunds work. It lives in a Notion doc. Then Slack. Then hardcoded as a bunch of if statements. No tests. No trace. No version control.

decision-layer is a small framework to clean that up.

You write the logic in YAML. Run it like code. Test it. Trace it.

What it does: - Versioned YAML policies - CLI to run and test them - Trace output with every rule fired - Examples: refunds, escalation, tiering

All in plain Python. No weird dependencies. Just testable logic defined clearly.

⸻

Would love to hear what confuses, breaks or annoys you. (Or what would make this usable where you work.)