Panel Review

Use this before committing to a coding decision you've drafted — a proposed diff before merging, an architectural choice before adopting, a security assessment before signing off, a migration plan before scheduling. Four frontier models stress-test it for blind spots, then revise their critiques in light of specific counter-positions. Returns a structured critique with severity tags and a recommended action class. Runs ~2-5 min with no progress shown mid-call — tell the user it's working before you call. Pass the REAL diff text, never a summary or an abridged version — elision manufactures findings about what was elided. LARGE DIFFS: past roughly 50 KB, split into 2-3 calls chunked by file or section instead of one oversized call — a single huge diff can cut off the panel's structured verdict (you'll see degraded: true with degraded_reason=assessment_parse_failure and an empty findings list). Input fields over 1 MB are clipped with a notice in the response. For a fast broad take use synthesize_coding; for an open-ended decision use deliberate_coding.

Use this before acting on a financial decision with real money at stake — a drafted trade thesis before placing the trade, a risk assessment before approving, an approve/decline call before committing, a backtest interpretation before deploying. Four frontier models critique it for tail risks, unstated assumptions, and asymmetric downside; specific weaknesses are routed back as targeted challenges; each model revises in light of specific counter-positions. Returns a structured critique with severity tags and a recommended action class. Runs ~2-5 min with no progress shown mid-call — tell the user it's working before you call. For a fast broad take use synthesize_financial; for an open-ended decision use deliberate_financial.

Cheap, FREE second opinion to clear a FALSE floor-gate block. When a floor-class gate (auth / secret / money / migration / guard, or a repo-defined custom floor) fired on what you believe is token-shape noise, this runs ONE budget model on your gate_diff: if it agrees the change is noise it mints a receipt that releases the change's FLOOR hunks. If it finds the change material — or is uncertain, errors, or the change touches the gate's own files — it releases NOTHING (run audit_coding instead). It covers FLOOR hunks only: if the gate's 'Still uncovered' line also lists NON-floor hunks, the gate keeps blocking on those — release them with record_gate_skip (a judgment reason) or an audit_coding PASS, which covers both kinds in one call. Forward BOTH the gate_context_id AND the target_hunk_hashes line the block printed (write and commit gates both print them) — the hashes are the deterministic binding tier, so the release binds to the gate's own recorded hunks even when your gate_diff is cosmetically drifted (drift is flagged, not dropped). The id alone does NOT bind unless your gate_diff genuinely overlaps the fire's hunks, so never omit the hashes. Free (no credits).

Use this when a coding decision is hard to undo and there's more than one defensible answer — deployment safety, architectural choices, dependency upgrade strategy, migration timing, security review judgment, contested merge calls. Four frontier models reason independently; conflicts between their reasoning are identified and routed back as specific points each model must defend or revise; refined responses are synthesized. Unlike peer-ranking approaches, models engage with specific counter-positions on the points where they disagreed. Returns a reasoned conclusion, agreement signal, dimensions of disagreement, and a recommended action class. Runs ~2-5 min with no progress shown mid-call — tell the user it's working before you call. For a fast broad take use synthesize_coding; for stress-testing a draft answer use audit_coding.

Use this when a financial decision has asymmetric downside and there's more than one defensible answer — trade-idea robustness, risk-model adequacy, backtest interpretation, lending judgment, fraud signal interpretation, portfolio reasoning. Four frontier models reason independently against tail-risk and asymmetric-downside framing; conflicts are routed back as specific points each model must defend or revise; refined responses are synthesized. Returns a reasoned conclusion, agreement signal, dimensions of disagreement, and a recommended action class. Runs ~2-5 min with no progress shown mid-call — tell the user it's working before you call. For a fast broad take use synthesize_financial; for stress-testing a draft thesis use audit_financial.

Health check — confirms the TruVerifAI MCP server is reachable and your API key is valid. Returns immediately, runs no model orchestration, and consumes no credits.

Release a TruVerifAI proactive-invocation gate WITHOUT running (another) review, by logging an explicit reason. Use it when a gate fired (before a commit or a Write/Edit) and EITHER the review is genuinely unnecessary — e.g. a false positive, a trivial/test/docs-only change, or generated/vendored code — OR you ran ONE review and want to proceed on it: apply its findings and pass recommendations_applied, or pass review_deferred_to_commit to defer a batch to the commit gate. NO judgment skip reason releases a FLOOR hunk (auth/secrets/money/migrations/removed-guard/gate-self — the gate's own code — or a repo-defined custom floor from .truverifai/risk.json) — not even test_or_docs_only / generated_or_vendored_code, because the path doesn't change what the hunk IS (a real credential in a test file is still a live credential, and .github/workflows/ classifies as test/docs). The ONE exception is recommendations_applied WITH your recent review on record: after you ran a review and applied its findings, it releases the re-fired change's floor hunks too (lineage-verified, minutes-TTL, logged distinctly as 'findings applied' — never as an audited PASS). Otherwise, while a floor hunk is UNREVIEWED every skip is denied: cover the floor first — audit_coding, confirm_floor (free), synthesize_coding, or, as a last resort, ship it un-reviewed with accept_risk_no_review (a logged override + substantive pre-mortem) — and the same skip then becomes admissible and releases the change's remaining NON-floor hunks. On a MERGE commit whose branch content was already reviewed, branch_already_reviewed releases the non-floor hunks in one call (merge fires only; name where it was reviewed in reason_text). (Note: 'already reviewed' is NOT a skip — a real prior PASS releases the gate automatically.) On a non-floor change the skip releases it on retry. FREE — no credits; the reason is logged. Pass the gate_repo from the gate's message, plus the gate_context_id it printed (REQUIRED — the server verifies a gate truly fired and releases only the hunks IT recorded, so you never supply hunks yourself). There is no way to skip without it: if the gate printed no id (rare), don't skip — run audit_coding with gate_repo + gate_diff.

Report whether a prior TruVerifAI MCP call (synthesize / deliberate / audit) was useful and whether it changed the decision you would have made without it. Call this AFTER you've acted on (or explicitly rejected) the response from the prior call. Free — no credits charged. The user sees the aggregate on their TruVerifAI dashboard; outcome reporting is how they evaluate whether the tool is worth keeping.

Use this when you want a multi-model second opinion fast — coding questions where being right matters but you don't have time for full deliberation. Library/API choices in production code, idiomatic patterns for new domains, anywhere a single-model answer might miss a viewpoint. Four frontier models answer in parallel and the result is synthesized into one answer with an alignment signal. ~15-30s. For high-stakes decisions reach for deliberate_coding; for stress-testing a draft answer reach for audit_coding.

Use this when you want a multi-model second opinion fast on a financial question where being right matters but you don't have time for full deliberation. Interpretations of market data or model output, factor explanations relevant to live decisions, comparisons of how different framings change an analysis — anywhere a single-model answer might miss a viewpoint. Four frontier models answer in parallel and the result is synthesized into one answer with an alignment signal. ~15-30s. For high-stakes financial decisions reach for deliberate_financial; for stress-testing a trade thesis or risk assessment reach for audit_financial.