What it does
The engine contains a federated query gateway library: an operator-supplied certification registry, a planner that pushes down bounded predicates and nothing richer, and an executor that verifies, authorises and merges the results with lineage. The crate states that it is planned and unmounted, and the server does not import it, so no route or command exposes it.
How it works
Every source must be certified by an operator registry (source id, one tenant, certifier, expiry, binding and classification) before it is queried. A claim made by the source itself is merely a claim; an unknown, expired or contradicting entry is refused before any call. The request purpose must equal the subject purpose, and each source and each filter field is authorised by the default-deny decision engine first.
The planner pushes down equality, and and all predicates and nothing else, with a page size and an explicit field projection. Anything richer is refused as unsupported rather than approximated. Each source runs under one deadline measured by the gateway clock. Every returned row must carry the query tenant stamp, contain nothing beyond the pushed fields, satisfy the pushed filter and not repeat an entity id, and every page must follow the paging contract; any violation fails the whole query instead of being trimmed.
Authorisation then runs again on every row and every field, denied rows are dropped and denied fields removed, and the merge is capped at the caller limit counting authorised rows alone. A source that times out fails the query unless partial results were requested, and then the result is labelled partial. Merge edges record project, query id and time for lineage.
Where you reach it
- Library
kynetra_federation::execute with CertificationRegistry and FederatedSource (Rust crate; not mounted by the server)
Limits
- Not reachable through any route, command or setting of the private-preview server.
- Certification entries are not cryptographically signed; the registry is trusted operator input.
- The crate records that, before any customer-facing mount, the owner must accept an availability residual: hidden rows can make a scan read a later page on which a source fails or times out.
- No source adapter for a specific external database ships in the crate; sources implement a trait.
Evidence
- Tests75 integration test functions cover certification refusals, pushdown limits, deadline enforcement, per-row and per-field authorisation, paging violations, partial-result labelling and scan-budget exhaustion
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
This is not available in the preview. Request a preview to discuss the current scope.