One pipeline, with a hard line through the middle. This page shows what runs on each side of the line, how the line is enforced in code rather than by convention, and how the whole thing sits inside your perimeter. The evidence for each statement is in the white paper.
An Eagle deployment is small. It runs on ordinary CPU servers in your data centre or your private cloud, and it ships with an air-gapped configuration.
The screening service and the analyst interface. Stateless; scales out behind your load balancer.
PostgreSQL. Screening data in one schema; the audit log in its own schema, written by a role that can only insert and read, with write-once triggers.
Serves the local model to the application. The only path from the product to a model. Absent, AI assist is off and screening runs unchanged.
All three on an internal network with no route out, under a sovereign mode that assumes no outbound connection. Lists, rulesets and models come in through your change process.
In a working session we plant a violation and show the build guard refuse it, run the integrity check on a live log, and run the replay conformance test.
