Policy as data

{
  "specVersion": "1.0.0",
  "onStoreError": "open",
  "checks": [
    { "id": "consent" },
    { "id": "mode", "allow": ["normal", "commute"] },
    { "id": "snooze", "defer": true },
    { "id": "quietHours", "priorityFloor": "high" },
    { "id": "trustRamp", "days": 7, "minPriority": "high" },
    { "id": "dismissalCooldown", "dismissals": 3, "withinDays": 30, "silenceDays": 7 },
    { "preset": "usTcpa" },
    { "id": "utilityFloor", "costFalseAlarm": 1, "costMissedHelp": 2, "shadow": true },
    { "id": "dailyBudget", "limit": 3, "bypassPriority": "critical", "nearLimit": 0.67 }
  ]
}

Each entry names a check id or a preset, plus that check’s options. shadow: true keeps it observing without deciding. onStoreError and keyPrefix are policy-level.

import { createGate } from "proactive-gate";
const gate = createGate({ policy: JSON.parse(await readFile("policy.json", "utf8")), store });

npx proactive-gate replay day.jsonl --policy policy.json --commit

compilePolicy(policy) is exported for callers that want the check list. An unknown id or preset throws and names the known ones; a specVersion whose major this package does not implement throws too. The JSON Schema lives at spec/schema/policy.schema.json.

The JavaScript policy (examples/policy.js, an ES module exporting a gate) stays as the escape hatch for checks that need functions, such as a kill switch that reads your flag service.