/** * `totem doctor --compliance` — query-before-derive section (mmnto-ai/totem#2510). * * Renders ONE number: of the derive-class actions in an agent session (spec * synthesis, orientation derivation, review grounding), what fraction was * preceded by a corpus query correlated to that action — plus its trend and the * pre-registered threshold it will be judged against. * * Sensor, not actuator (Tenet 13): this section renders and returns. It never * throws for a compliance verdict and never influences the exit code. Nothing * in Totem blocks on this number in v1, by charter. * * Reads alongside the existing ADR-029 recall-compliance section rather than * replacing it: that metric is search-before-COMMIT at commit granularity; this * one is query-before-DERIVE at event granularity with explicit correlation IDs. * Different denominators, different claims, both printed under `--compliance`. */ export interface QbdComplianceCliOptions { /** Test seam — production callers omit and the command uses `process.cwd()`. */ cwdForTest?: string; /** Test seam — inject raw ledger NDJSON instead of reading from disk. */ ledgerContentForTest?: string; /** * Test seam — point global-profile resolution at a temp home. Without it a * test in a config-less directory resolves the developer's REAL `~/.totem/` * profile and reads (or, on the write side, writes) their live ledger. */ homeDirForTest?: string; } /** * Render the query-before-derive compliance section. * * Degraded-read contract (ADR-115 § 2): a scan that hit malformed lines, * correlation-contract violations, or unjoinable correlation IDs renders under * an explicit `DEGRADED` / `UNVERIFIED` envelope with per-item counts. A broken * ledger scan must never render like a clean 100% or a clean 0% — that * indistinguishability IS the defect class, not an acceptable degradation. */ export declare function doctorQbdComplianceCommand(options?: QbdComplianceCliOptions): Promise; //# sourceMappingURL=doctor-qbd.d.ts.map