Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
The projected query read path: exact, signed projection artifacts
answered through DataFusion behind a verified credential.
This crate is the Query plane's read model. A deployment composes
[core_service::ProjectedCoreService] once at startup, then runs each
credential-bearing request through it. Everything between those two
points stays private: core_resolution plans the statement against the
closed catalog, core_execution executes it over verified artifacts,
statement_gate admits only query-shaped ASTs, and credential carries
the two sealed impls polyc-query-credential's witness needs. Nothing
outside this crate can assemble those parts in an order
[core_service] never checked — see that module's own doc for the seam.
[QueryLimits], re-exported here because it is a plain
resource-ceilings struct the service composition takes by value, is the
one other public item — every field on it is one the projected path
reads. The wire
JSON envelope is [polyc_query_model::QueryResultJson]: it lives in the
DataFusion-free protocol vocabulary crate (POLY-359), so a caller
names it without linking this engine.