@aid-framework/cli 0.1.61 → 0.1.63

package/dist/commands/guard.d.ts

@@ -0,0 +1,55 @@
+/**
+ * `aid guard` -- measure an app's guardrails against a red-team corpus.
+ *
+ * **What is measured, and why it is measured here.** The runtime's `GuardrailEngine` is
+ * the thing that decides whether text is a jailbreak, a secret, or an injection, and the
+ * generated `generated/guardrails.py` is the table of declarations the routes enforce.
+ * This command joins the two and reports, per fixture, whether the table the app actually
+ * shipped caught it. Detection is not reimplemented: a second implementation here would
+ * drift from the one the routes run, and the number it produced would describe the CLI
+ * rather than the application.
+ *
+ * **Why the corpus is an input.** The framework's own corpus lives in
+ * `runtimes/python/tests/redteam/fixtures.json` and is not shipped with any package.
+ * Copying it into the CLI would create a second copy that drifts from the one
+ * `test_redteam.py` gates on, and shipping it with the runtime would change a landed
+ * layer's published contents for one command's convenience. So the format is the
+ * contract: `--red-team` names a file, and without it the command looks for
+ * `redteam.json` beside the spec and then at the project root.
+ *
+ * **Why it evaluates the declared table, not one synthesized definition per fixture.**
+ * `test_redteam.py` builds a `GuardrailDefinition` for each fixture and runs it alone,
+ * because it is testing the detectors. This command is answering a different question --
+ * "would *this app* have caught this?" -- so it hands the engine every declaration that
+ * covers the fixture's stage, exactly as a route does, and a fixture counts as caught
+ * when any of them fires. A declaration that names the wrong policy still counts as a
+ * catch if its other policy fires: the app stopped the payload, which is what matters.
+ *
+ * **Why `covered` is a separate fact from `caught`.** "No declaration at this stage names
+ * this policy" is a spec gap the developer can close by editing the YAML; "declared but
+ * the detector missed" is a detector gap they cannot. Folding both into one recall number
+ * would send a reader to the wrong file, so the undeclared pairs are listed on their own
+ * line and in the `--json` document.
+ *
+ * **Why nothing is regenerated.** A gate measures the tree it is given, and `aid eval`
+ * already sets that precedent: this command reads `generated/guardrails.py`, and a tree
+ * that predates the spec is reported as a missing or stale module rather than silently
+ * replaced. Run `aid gen` first, as CI does.
+ *
+ * **When it does not run, and what it exits with.** Exit 2 is "this command could not
+ * judge the project": an unknown target, a target with no driver, a corpus that is
+ * missing or malformed, or no interpreter that can import the runtime. Exit 1 is a
+ * verdict about the project: it declares no guardrails, its tree has no guardrail module,
+ * the run failed, or the measured recall / false-positive rate misses what the corpus
+ * asks for.
+ */
+import type { CliContext } from '../context.js';
+import type { CommandOutcome } from '../output.js';
+export interface GuardOptions {
+    readonly spec: string | undefined;
+    readonly target: string | undefined;
+    /** The corpus to measure against; discovered beside the spec when omitted. */
+    readonly redTeam: string | undefined;
+}
+export declare function guard(context: CliContext, options: GuardOptions): CommandOutcome;
+//# sourceMappingURL=guard.d.ts.map

package/dist/commands/guard.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"guard.d.ts","sourceRoot":"","sources":["../../src/commands/guard.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4CG;AAMH,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,eAAe,CAAC;AAIhD,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,cAAc,CAAC;AAOnD,MAAM,WAAW,YAAY;IAC3B,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,SAAS,CAAC;IAClC,QAAQ,CAAC,MAAM,EAAE,MAAM,GAAG,SAAS,CAAC;IACpC,8EAA8E;IAC9E,QAAQ,CAAC,OAAO,EAAE,MAAM,GAAG,SAAS,CAAC;CACtC;AAwZD,wBAAgB,KAAK,CAAC,OAAO,EAAE,UAAU,EAAE,OAAO,EAAE,YAAY,GAAG,cAAc,CAkYhF"}