Storage

In-memory and PostgreSQL storage adapters for governance-sdk. Swap backends with one line.

Pluggable storage backends for governance state. In-memory by default, PostgreSQL for production. Import the PostgreSQL adapter from governance-sdk/storage-postgres.

Adapters

Adapter	Signature	Description
In-memory (default)	`createGovernance({ rules })` — no storage option	All state held in process memory. Zero configuration. Ideal for development, testing, and stateless environments. Data lost on restart.
createPostgresStorage	`createPostgresStorage({ pool, tablePrefix?, autoMigrate? }) => Promise<PostgresStorage>`	PostgreSQL adapter. Pass a pg Pool instance. Durable across restarts.

In-Memory (Default)

import { createGovernance } from 'governance-sdk';

// In-memory storage is the default — no configuration needed
const gov = createGovernance({
  rules: [...],
  // storage is implicitly in-memory
});

// All audit entries, kill switch state, and policy data
// live in process memory. Lost on restart.

Note: In-memory storage is perfect for development and CI. No database required. All state resets when the process exits.

PostgreSQL

import { createGovernance } from 'governance-sdk';
import { createPostgresStorage } from 'governance-sdk/storage-postgres';
import { Pool } from 'pg';

const pool = new Pool({
  connectionString: process.env.DATABASE_URL,
});

const storage = await createPostgresStorage({ pool });

const gov = createGovernance({
  rules: [...],
  storage,  // All state persisted to PostgreSQL
});

// Tables are auto-created on first use:
//   lua_governance_audit    — audit chain entries
//   lua_governance_kills    — kill switch state
//   lua_governance_policies — policy snapshots

Note: Tables are auto-created with IF NOT EXISTS. No migrations needed. The adapter uses the standard pg package — bring your own Pool with your preferred connection settings.

Switching Backends

The storage interface is identical across backends. Switch from in-memory to PostgreSQL by adding one option — no other code changes.

// Development: in-memory (fast, no setup)
const devGov = createGovernance({ rules });

// Production: PostgreSQL (durable, queryable)
import { createPostgresStorage } from 'governance-sdk/storage-postgres';

const prodGov = createGovernance({
  rules,
  storage: await createPostgresStorage({
    pool: new Pool({ connectionString: process.env.DATABASE_URL }),
  }),
});

// Both use the exact same API — enforce(), kill(), audit, etc.
// Zero code changes when switching storage backends.