pub struct Numbers {
pub limit: Option<NonZeroU32>,
pub depth: Option<NonZeroU32>,
pub ceiling: Option<NonZeroU32>,
pub streams: Option<NonZeroU32>,
}Expand description
THE FOUR NUMBERS a declaration writes about its own doors — the BONES tier of the wire road’s number design.
#[ingraph::vector(upstream(…), limit = 50, depth = 200, ceiling = 1000)] the CONTAINER
pub struct Shots {
#[ingraph(list(embedding), knn, lance, limit = 10, streams = 16)] the ELECTION
clips: Vec<Embedding<f32, 4, Clip>>,
}§The TRICHOTOMY, which is what makes several words rather than one
limit and depth are PREFERENCES — an author’s semantic defaults for every door of the thing
they are written on, and a request may write past either. ceiling and streams are PROTECTION
— the #293-B ruling’s WALL and the 2026-08-16 SET ruling’s stream guard, upper bounds on what any
one request may cost this deployment, which a request may never rewrite because a bound the
requester can rewrite binds nothing.
The two families sit in one struct because they are written in one position and read by one chain; what keeps them apart is where each is SPENT — a preference lands as an SDL default a client overrides, and neither protective number reaches any wire row at all.
§The two protective words bound two INDEPENDENT axes, which is why there are two
ceiling caps HOW DEEP one stream is walked and streams caps HOW MANY streams there are. The
ruling that minted the second said so in the user’s own words — 一词多义 — and the measurement
behind it is that one number cannot serve both: a per-stream depth of 500 under a stream cap of 16
is unspellable as a single widened ceiling.
§NonZeroU32 and not a plain integer, at both tiers
The door family’s currency is NonZeroUsize and a declaration’s is NonZeroU32 — the width
route_depth already takes a wall at, chosen there because a declaration writes a number a
person typed rather than a machine’s address space. A zero is UNREPRESENTABLE rather than
refused twice over: limit = 0 asks for an answer with no rows, which the retype round made a
type error everywhere else in this family.
§And first is still not one of these
first is the SAME NUMBER as limit wearing GraphQL’s own spelling, so it lives in the skin
block (IndexBackend::first, ElectionBackend::first) and never here. Q6a’s own sentence:
first 是 graphql 的术语.
Fields§
§limit: Option<NonZeroU32>limit = N — how many rows a door of this thing answers with when nothing asks otherwise.
depth: Option<NonZeroU32>depth = N — how deep each stream behind a fold is fetched when nothing asks otherwise.
None falls to the limit chain, which is the same deferral Route::depth spells one grain
up: there is no number that means as deep as whatever is below me.
ceiling: Option<NonZeroU32>ceiling = N — the WALL, and the one number here a request can never reach.
None is the AUTHOR’S INFORMED OPENNESS rather than a gap the framework fills: the engine’s
own corpus clamp is the final safety, exactly as the #293-B ruling states it.
streams: Option<NonZeroU32>streams = N — HOW MANY QUERY VECTORS one request may ask a _with road with.
PROTECTION beside ceiling rather than a preference beside limit: the
number bounds what a REQUEST states, so a request able to rewrite it would bound nothing. Past
it is a REFUSAL naming the count and never a clamp — the ruled clamp-vs-refuse line is clamp
preferences, refuse mutilated questions, and dropping query vectors answers a different
question under the same name.
It guards the _with QUESTION road ALONE. The by-example set road’s m comes out of the
example’s own stored set, which is this deployment’s own data rather than anything a request
can inflate — see IndexModel::similar_set_leg, whose doc states the same absence.
None is ceiling’s own reading of an unwritten word: no guard is emitted at all, and the
road is byte-for-byte what it was before the word existed.
The wire ROW called streams on a set hit is a DIFFERENT word in a different vocabulary — see
ingraph_derive::index::FLOOR_WORDS, where it is the framework’s own answer row and is refused
every rename. One concept, a bones word and a wire surface, which is depth’s own precedent.