Papers
Working paperv0.1
Evidence-Native Postgres Control Planes
This working paper defines a Postgres control-plane architecture where recommendations, approvals, mutations, rollbacks, and buyer exports are bound to explicit evidence artifacts.
Summary
QueryRook should not merely say what it wants to do. It should show the proof, preserve the proof, and make missing proof visible before any production-facing action.
Claims
QR-CLAIM-2026-001
Evidence-native control plane
Every production-facing recommendation should be backed by inspectable evidence before it can become an operator action.
Methods
- Map every agent action to required proof obligations.
- Inject missing proof states and measure whether QueryRook blocks unsafe promotion.
- Compare evidence-native workflows against conventional observability-plus-manual-DBA review.
Metrics
Evidence completeness rate
Time from slow-query detection to reviewable action
Proof packet verification success
Operator time-to-confidence
Limitations
- Architecture evidence does not replace live customer-environment benchmarks.
- Operator time-to-confidence requires human study data before publication-grade conclusions.
Reproducibility
Current status: Planned bundle. Reports generated by ResearchOps include commit hashes, run IDs, artifact paths, required disclosures, and a SHA-256 integrity hash.