Audit research findings for completeness
grounding-auditworkflowsetup L3★3
LogosLang/prologos ↗What it does
Grounding Audit
Best for
Parallel read-only audits against design claims with completeness criticism.
Outputs
- · findings array with evidence + root causes
Requires
- · agent-orchestration-engine
- · parallel-execution-runtime
- · schema-validation (zod or JSON-schema)
- · phase-tracking-system
- · logging-framework
Preconditions
- · workflow must export meta={name, description, phases}
- · args may be JSON-stringified; parse defensively
- · multi-phase execution context available
Failure modes
- · null/undefined agent results filtered; total < expected → synthesis data-starvation
- · agent output fails schema validation → workflow errors or graceful downgrade
- · loop terminates at MAX_ROUNDS even if not converged → incomplete results
Trust signals
- · Method discipline codified in prompt preamble
- · Structured schemas with required fields and enums
- · Confidence levels distinguish verified vs inferred claims
- · Explicit null-filtering on agent results
- · Read-only audit discipline (no mutations)
- · Git HEAD pinning + verification protocol