Guard Saga Config

Saga-creation config validator. Refuses empty steps array, duplicate step names, non-ASCII saga name, non-async-function run/compensate fields, oversized step count.

b.guardSagaConfig.validate(config, opts?) #

{
  profile:   "strict" | "balanced" | "permissive",
  posture:   "hipaa" | "pci-dss" | "gdpr" | "soc2",
}

Validate saga config. Returns config on success; throws on refusal.

b.guardSagaConfig.validate({
  name: "mail.send",
  steps: [
    { name: "sign", run: async () => {}, compensate: async () => {} },
  ],
});

b.guardSagaConfig.compliancePosture(name) #

Return the effective profile NAME for a compliance posture, or null for a name this parser does not map. Unlike the content-guard variant this returns the resolved profile string (every line-protocol parser composes gateContract.ALL_STRICT_POSTURES, so "hipaa" / "pci-dss" / "gdpr" / "soc2" all resolve to "strict") and never throws — the parser shape carries no overlay-clone, no buildProfile, and no loadRulePack. Wired by gateContract.defineParser.

b.guardSagaConfig.compliancePosture("hipaa");                   // → "strict"
b.guardSagaConfig.compliancePosture("not-a-regime");            // → null

Last updated 2026-08-08T16:39:49.652Z by seeder.