Reports and break-glass (retired in 3.0)
Removed in 3.0
In Relata DB 3.0 the foundation no longer composes or signs application reports or runs a HUMINT approval workflow (ADR-0309). The five former routes
POST /report/pdf, POST /report/sign, POST /humint/breakglass/request, POST /humint/breakglass/approve and GET /humint/breakglass/status/{request_id} answer HTTP 410 with code=domain-route-retired before parsing the body. The matching SDK helpers are removed. The released 2.5.8 line still has them.What to do instead
- Report content. Fetch the governed rows with
POST /v1/query(withWITH PROVENANCEandAS OF SYSTEM TIMEwhen the report must be reproducible) and render the sections in your application. Browser printing produces a PDF. - Integrity. Sign your own report manifest with a key you own. Relata no longer derives a signing key from its audit chain. Tamper-evident, signed and exportable audit is Relata Enterprise DB.
- Approval workflows. Own the request, justification and two-person approval in your application, and verify the approver's identity there. Relata does not unmask identities through a built-in approval flow.
- Evidence for an alert.
GET /v1/alerts/{id}/evidencereturns a SHA-256 over the contributing events; see SIEM / SOC.
See also Retrieval evidence and Audit log.