QueryRook claims are scoped, caveated, and linked to evidence types. This lets us revise claims when new tests teach us something uncomfortable.
Every production-facing recommendation should be backed by inspectable evidence before it can become an operator action.
QueryRook proof packets, DDL obligations, readiness checks, and burn-in artifacts.
This is an architecture claim until repeated customer-environment measurements are published.
A multi-day database-agent burn-in can expose onboarding, permission, workload-drift, and evidence-freshness failures before production authority is granted.
168-hour QueryRook burn-in runs against AWS-hosted QueryRook and TLS-enabled Postgres targets.
The first public confidence level must wait for the current AWS burn-in to complete.
Autonomous Postgres operations are safer when the hosted control plane issues bounded, signed action capsules that a customer-owned Conduit verifies locally.
QueryRook Conduit capability-token prototypes and action-capsule verification tests.
The current production deployment still supports hosted-direct operation while Conduit matures.