Command documentation

audit

Audit trust: coverage, provenance, gaps, limits, and review status.

Purpose

This command is available over HTTP, MCP and the local CLI. HTTP responses use the compact public response shape with summaries, warnings and bounded tables.

MCP connection

Use endpoint https://bible.grod.es/mcp with tool bible_audit. The MCP Server Card is /.well-known/mcp/server-card.json.

Parameters

Name	Required	Description
`target`	no	Object to audit for coverage, provenance, review status, gaps, and limits. Use scope for corpus-wide audits. Target grammar: natural Bible reference, or prefix:value. Examples: Deut 32:8, John 1, ref:Deut 32:8, strong:H7225, entity:Paul, source:LXX, variant:<id>, resource:<id>.
`scope`	no	Audit boundary; use corpus for whole-database diagnostics. Scope narrows where the command searches or audits; target is what the command is about. Scope grammar: named corpus slice, natural Bible reference, or prefix:value. Examples: corpus, Torah, Pauline epistles, Acts, ref:John 7:53-8:11, source:LXX, topic:covenant.
`limit`	no	Maximum diagnostic rows per audit group. It exposes enough gaps, coverage, and provenance examples to verify trust without dumping every row. Default 20, max 100.
`depth`	no	Expansion depth from 0 to 10. 0 returns direct facts for the target; 1 is the default useful context; higher values include more related context and are clamped by the server --max-depth instead of failing. For audit it expands lineage, gaps, and diagnostic coverage context.
`include`	no	Audit groups to include, such as coverage, gaps, reviews, limits, schema, indexes, ingestion, or semantic diagnostics. Use provenance for lineage detail.
`provenance`	no	Controls provenance detail independently from domain includes: none omits extra provenance sections, summary returns compact source lineage, and full returns the most detailed provenance available for the command.

Examples

HTTP

curl -s 'https://bible.grod.es/api/audit?depth=2&include=coverage&provenance=full&scope=corpus'

MCP

{
  "arguments": {
    "depth": 2,
    "include": [
      "coverage"
    ],
    "provenance": "full",
    "scope": "corpus"
  },
  "name": "bible_audit"
}

CLI

bible audit --scope corpus --depth 2 --include coverage --provenance full

Caveats for this command

Inventory and audit output describes loaded local data and known gaps. It is not a claim of exhaustive global coverage.
DSS material is fragmentary.
LXX GreekResources data is lemma-level and not a full critical apparatus.
The runtime does not call LLM or embedding APIs.