audit-emit

What problem does it solve?

It prevents audit logging drift and missing state transitions by funneling all cross-tool workflow events into a single, schema-enforced append-only emitter.

Core Features & Use Cases

• Centralized append-only audit boundary: All Dispatcher steps, Scribe sends, and CoS routing decisions emit through a single function that writes to .harness/swarm/swarm.jsonl.
• Schema enforcement with strict type validation: Unknown event types are rejected at the boundary to avoid silent data corruption and schema drift.
• PII redaction guardrails: String fields beyond a configured length are redacted before writing to the audit log.
• Optional external observability sink: When Langfuse environment variables are set, the emitter also forwards rows asynchronously while keeping the local jsonl write as the source of truth.

Quick Start

In your workflow code, replace any direct .harness/swarm/swarm.jsonl writes with calls to audit_emit.row(type, actor_role, ...) so every transition is consistently captured with validated schema and redaction.