pub struct WireFace {
pub object: Option<RustSafeName>,
pub filter: Option<RustSafeName>,
}Expand description
The WIRE activation: graphql, and the two SDL names its block may move.
§A third activation, and saddle-agnostic where the other two are host kinds
record and entity name the rungs that may HOLD this fragment. This one names nothing of the
sort: it says the declaration has a face on the wire at all. Without it a fragment is a
storage-only value — a width, a bind, a read and a predicate, with no object, no crossing and no
input-object registration — which is a shape the tier could not express before, every declaration
publishing whether anything asked or not.
The old refusal’s sentence survives as the SIGNPOST rather than as a rule: a fragment still has no queryable ROOT, and what it shows on the wire is a fragment of whatever holds it. What the word activates is the object that holder resolves through.
§Two SDL names, which is the seat #340’s survey left open
A fragment publishes four named surfaces — its object, its filter input object, and one member
name on each per field — and had no graphql(…) word to hang a rename on. Two seats close all
four: the two TYPE names here, and one FIELD name per field, from which the fourth surface
derives. That is the guide’s own classification (a name derived from a base a word already
moves), and it is what a record does too — its filter slot reads the field’s declared wire name
rather than the member’s.
Fields§
§object: Option<RustSafeName>graphql(rename = "…") — what a client calls the fragment’s own OUTPUT OBJECT.
None is the fragment’s own name, which is what the #[Object] block spelled before this
seat existed.
filter: Option<RustSafeName>graphql(filter(rename = "…")) — the BASE the FILTER family’s schema names compose off.
§It moves a base, not a name, and #340’s twin law is why
A fragment publishes up to TWO input objects — the full field set at a rowless host and the
stored subset at a row-holding one — and a derived name is composed off the SCHEMA base rather
than off the Rust ident, so a renamed face carries its twin. filter(rename = "Dim") therefore
publishes DimFilter beside DimColumnFilter; composing off the ident would have published a
renamed face beside a twin still wearing the old stem, which is the half-working rename the
law calls worse than none.
None is the fragment’s own name, which composes to <Fragment>Filter — exactly the name
the composed door minted before the second face existed.
The stored face takes no independent word. What one would be FOR is a schema publishing both faces that wants the second called something else, and no consumer has asked — the admission bar, 2026-08-22.