Operator documentation

Deploy with the behavior understood.

A concise field guide for the three shipping products. VeriTrooper produces decision-support evidence; a qualified human remains responsible for interpreting results and signing off.

Scout

Run a defined question set against one or more assistants and preserve comparable evidence.

Product details

Watchtower

Audit captured or probed traffic on a cadence inside your environment.

Capture contract

SitRep

Turn completed evidence packages into an executive-ready summary.

Product details

Five-minute start

Install the signed-for-delivery Windows package and open VeriTrooper.
Select Scout, Watchtower, or SitRep according to the job you need to complete.
Choose the dataset, endpoint, or completed evidence package requested by that workflow.
Review the scope and settings before starting. Keep customer and production data within the boundary approved by your organization.
Run the workflow, inspect warnings and evidence, then complete human review and signoff before relying on the result.

Hardware planning baseline for local Selene analysis: 16 GB RAM minimum, 32 GB recommended; 8 GB VRAM and 8 GB free disk recommended. The bundled model is approximately 4.92 GB. Endpoint-based workflows may have different requirements.

Watchtower capture contract

Passive Watchtower accepts JSONL files and live HTTP capture. Each record needs a non-empty question and answer. The reader also accepts common aliases and optional context fields.

Field	Required	Accepted names	Purpose
`query`	Yes	`query`, `question`, `UserQuery`	User prompt or question.
`answer`	Yes	`answer`, `response`, `Response`	Assistant response to audit.
`session_id`	No	`session_id`, `sessionId`, `ChatSessionId`	Threads turns and supplies prior-turn context.
`timestamp`	No	`timestamp`, `time`	Orders and identifies captured activity.

JSONL example

{"query":"What is the retention period?","answer":"Records are retained for 30 days.","session_id":"case-1042","timestamp":"2026-08-09T14:20:00Z"}

HTTP capture

POST http://127.0.0.1:8190/v1/capture
Content-Type: application/json
Authorization: Bearer <token, when configured>

{"query":"What is the retention period?","answer":"Records are retained for 30 days.","session_id":"case-1042"}

A successful capture returns {"ok":true,"captured":true}. The equivalent path /capture is also supported. When no token is configured, the daemon is limited to local access; when a token is configured, capture and administrative routes require it. Captured turns are appended and evaluated on the next scheduled or manually started audit cycle—not during the capture request.

Troubleshooting

Symptom	What to check
`missing or invalid token`	Send the configured bearer token. Do not place tokens in query strings or evidence exports.
`capture requires non-empty 'query' and 'answer'`	Supply both values as non-empty strings; accepted aliases are listed above.
`bad request body`	Validate JSON syntax and send `Content-Type: application/json`.
No captured turns appear	Confirm the capture path, permissions, selected log file, and that new turns arrived before the audit cycle.
Reindex fails	The existing live index is retained. Correct the corpus or access issue, then retry reindexing.
Package verification warns or fails	Stop and compare the manifest, checksums, and expected files. Do not treat an altered package as verified.

Evidence and package handling

Keep the complete output package together. Machine-readable records, human-readable reports, manifests, checksums, configuration snapshots, and signoff material serve different review needs. Do not rename a package “verified” merely because a workflow completed; verification depends on the controls and human review documented for that run.

For deployment architecture, evidence boundaries, or procurement review, request a scoped pilot. See also package contents, methodology, security, privacy, and terms.