audit-engine

Orchestration Log: When this skill is activated, append a log entry to outputs/orchestration_log.md:

### Skill Activation: Audit Engine
**Timestamp:** [current date/time]
**Actor:** AI Agent (audit-engine)
**Input:** [paper + repo being audited]
**Output:** [brief summary — e.g., "Audited 18 claims: 12 CONFIRMED, 3 PARTIAL, 2 MISSING, 1 MISMATCH"]

Audit Engine

Core Principle

Papers make claims. Code embodies what was actually done. This engine systematically checks whether the two agree. For every empirical or technical claim in the paper — datasets used, models trained, metrics reported, hyperparameters set, ablations run — the engine locates supporting evidence in the linked repository and classifies the match.

This is the complement to verification-engine, which checks citations against external sources. Audit-engine checks the paper's own claims against the paper's own code. Together they cover both failure modes of LLM-assisted writing: mis-cited prior work and unsupported own-work claims.

Inspired by the /audit command in the Feynman research agent (Companion AI, 2026), adapted to the IS/CS methodological style of this plugin.

When to Activate

• User says "audit the paper", "check paper vs. code", "verify my experiments", "reproducibility audit", "does the code match what I wrote"
• Before submitting a paper with an accompanying code release
• Before open-sourcing the repo of a published paper
• When reviewing someone else's paper + artifact
• As optional Phase 7.5 of the paper machine pipeline (after verify-citations, before prepare-submission)

When NOT to Activate

• The paper has no code artifact (pure theory, position paper, qualitative study without computational analysis) → say so and exit
• The user wants to verify citations → activate verification-engine instead
• The user wants to check writing quality → activate the writing-engine /analyze-writing command

---

Inputs

Required:

1. Paper source — paper.tex, draft.md, or explicit $ARGUMENTS path
2. Code repository — one of:
   • Local path (./experiments/, ~/repos/myproject)
   • GitHub URL (clone or use gh repo view / WebFetch on raw files)
   • Archive link (Zenodo, OSF) — ask user to download locally first