Add Rule

To create and enforce governance rules across multiple repositories, you can draft and validate rule metadata in a centralized Supabase rule ledger, then use the distribute_rules.py workflow to propagate changes via MCP or direct SQL.

A centralized rule ledger is a Supabase Postgres database that stores governance policy metadata like rule keys, severity, and autonomy levels. It ensures rules are consistently enforced across all connected repositories via MCP tooling.

You distribute updated SQL compliance policies by running the mandatory distribute_rules.py script across all target repositories, ensuring the new or updated rules from the Supabase ledger are propagated and applied consistently.

Yes, you can use Supabase MCP as an alternative to direct psql access to manage company governance rules. This allows you to draft, validate, and distribute rule metadata entries directly through MCP tooling integrations.

Defining a new governance rule requires metadata fields including rule_key, name, description, domain, trigger_type, trigger_name, priority, severity, and autonomy_level in the rule_ledger.rules table.

You update existing rule variants by using the --update flag when drafting changes, then running the distribute_rules.py workflow to propagate them, followed by executing the provided verification steps to ensure correct application.