Know when production answers drift.

What Watchtower returns

Each completed monitoring cycle produces a retained, reviewable evidence package tied to that deployment and cycle.

• Bound Monitoring Report and leadership Executive Summary
• System Card, Monitoring Scope, and Monitored Traffic Card
• Flagged Answers report with the production questions, answers, verdicts, and supporting evidence
• Gap and Remediation Diagnostic plus Data Findings
• Framework Crosswalk and Annex IV Monitoring Record
• Isolation Posture and Audit Dossier
• Machine-readable evidence, model card, SARIF findings, and OpenTelemetry spans
• Canonical monitoring record, configuration, logs, signed manifest, integrity checker, and hash-bound reviewer trail

From traffic to evidence

Watchtower supports passive JSONL or HTTP capture and active endpoint probing.

• Hourly, daily, weekly, monthly, or manual cadence
• Trigger gates and per-cycle sample controls
• Session-aware context for captured conversations
• Append-only captured records and durable audit outputs
• Reindexing that preserves the live index if a rebuild fails

Monitor quality, not just uptime

A healthy endpoint can still return a confident wrong answer. Watchtower is built to identify answer-quality failures and changing patterns, not merely latency and availability.

Inside the approved boundary

The daemon can remain local and token-gate capture and administrative routes. Captured turns are audited on the next scheduled or manually started cycle, not during the capture request.