audit

Principle Audit

One-shot audit of current context through your curated principles, verified by a stronger model (advisor). Unlike /grill (interactive, asks questions), /audit is non-interactive — it loads principles, calls advisor, and returns findings.

Usage

/audit           # p0: auto-pick top 3 most relevant principles
/audit p1        # audit through P1 (First Principles) only
/audit p0        # same as bare /audit
/audit p1 p5     # audit through P1 + P5

How It Works

1. Read principles from {vault}/thinking/principles/tracker.md
2. Pick principles: p0 auto-selects top 3 most relevant to current context, or use specified IDs
3. Print selected principles into conversation (so advisor sees them)
4. State: "Audit this conversation context through these principles. For each principle: does the current approach pass or fail? What specifically needs to change?"
5. Call advisor() — stronger model applies principles independently
6. Format advisor findings for the user
7. Log principle usage to tracker (date, principles, context, outcome)

Principle Selection (p0 logic)

When no specific principle is given, pick the top 3 most relevant to what's currently being discussed. Pick order:

1. Principles that directly challenge the current approach (flag candidates first)
2. Principles that guard the most expensive failure mode (cost-of-wrong matters)
3. Principles most recently applied to a similar context

Single-principle audits produce the sharpest results. Default p0 to 3 but respect user's specific picks.

P3 scope check: P3 (Value Equation) requires ≥50 words of content AND structural differences between options (not phrasing-only). Skip P3 for micro-edits — it won't discriminate.

Output

Present the advisor's findings directly. Then append a structured summary:

## Audit Summary
| Principle | Verdict | Key Finding |
|-----------|---------|-------------|
| P1 | PASS/FLAG/FAIL | one-line finding |

Logged to tracker.

Format contract: The ## Audit Summary heading and table structure (| P{N} | PASS|FLAG|FAIL |) are consumed programmatically by downstream skills (e.g. /slice audit gate). Verdict values must be exactly PASS, FLAG, or FAIL — do not alter heading, column structure, or verdict text.

Tracker Integration

After each audit, append to the Log table in {vault}/thinking/principles/tracker.md:

| {date} | {principles} | {context} | {outcome} |

Also increment the Uses count for each principle applied.

Outcome log

Follow skill-spec.md § 11. Append to {vault}/daily/skill-outcomes/audit.log:

{date} | audit | audit | ~/work/brain-os-plugin | thinking/principles/tracker.md | commit:N/A | {result} | args="{principles}" findings={summary}

• result: pass when audit completes and produces findings (regardless of verdicts); partial if some principles couldn't be fully evaluated; fail if advisor call failed or tracker.md unreadable
• findings: verdict breakdown capturing content quality separately from skill execution — e.g. 3FLAG+2PASS, 1FAIL+1FLAG+1PASS
• args=: principle IDs used (e.g. p1 p5)