ECSS SpaceWire Service Primitive — Semantics Subclause (space-systems/ecss/e5053-semantics)
Use when the task is the semantics subclause of ECSS-E-ST-50-53 clause
5.2.2.2 — the parameter list a service primitive carries, the presence
category of each parameter, and whether the four primitives of one
service still describe the same exchange when read together.
Domain quick reference
- The semantics subclause is the only place a primitive's parameters are
declared. Each entry needs three things to be implementable: a name a
caller can bind, a type that fixes its representation, and a presence
category saying whether it is always there, there under a stated
condition, or at the user's discretion.
- Conditional presence without the condition is the defect that looks
like a complete entry. An implementer reading it has to guess when to
supply the parameter, and two implementations will guess differently.
- A service is specified as up to four primitives around one exchange:
request and confirm at the originating user, indication and response at
the peer. They are not independent lists. A parameter the originator
must always supply cannot vanish on the way to the indication, and the
indication cannot require a parameter the request never carried unless
the service provider itself generates it.
- Relaxation across a pair is legitimate in one direction only. A
mandatory request parameter may arrive as conditional at the indication
when the provider may legitimately withhold it; the reverse, a
conditional request parameter that is mandatory at the indication, is
unimplementable.
- Duplicate parameter names inside one primitive are a specification
error rather than a finding: the list can no longer be indexed, so
nothing downstream of it can be graded.
Workflow
- Validate each parameter entry: name present and non-empty, type
present and non-empty, presence category inside the closed set of
mandatory, conditional and optional, and a condition supplied for
every conditional entry.
- Build the per-primitive parameter index, refusing a list that names
one parameter twice once case and surrounding space are normalised.
- Split each primitive name into its service and its kind so the four
primitives of a service can be grouped without relying on ordering.
- Group the specification by service and check that a service declares
at most one primitive of each kind.
- For each service holding a request, align every partner primitive
against it: report a mandatory request parameter absent from the
partner, a partner parameter that the request never declared and that
is not listed as provider generated, and a partner parameter whose
presence category is stronger than the one the request gave it.
- Roll the per-primitive and per-service findings up into a compliant
count against the total so a partially clean service definition can be
reported without hiding the failures.
Pitfalls
- Grading a primitive in isolation. Every entry can be well formed and
the service still be unimplementable, because the defect lives in the
relationship between the request and its indication.
- Treating an optional parameter as free. Optional at the request and
mandatory at the indication is the same unimplementable pairing as the
conditional case, only harder to see.
- Accepting conditional presence with the condition written in the
additional comments subclause. The condition has to sit with the
parameter, otherwise the entry is incomplete wherever the reader is.
- Matching parameter names case sensitively. A list carrying both a
lowercase and a capitalised spelling of one name is a duplicate, and
passing it through produces two bindings for one field.
- Adding a provider-generated parameter to an indication without
declaring it as such. It then reads as a request parameter that was
lost, and the real finding is buried under a false one.
Behavior contract (gate 3)
The parameter validation, presence-category enforcement, duplicate
rejection, primitive-name splitting, service grouping, pair alignment and
roll-up are exercised by the gate 3 contract test:
scripts/test_e5053_semantics.py against scripts/e5053_semantics_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e5053_semantics.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e5053-semantics3description: "Validate the semantics subclause of a SpaceWire service primitive against ECSS-E-ST-50-53 clause 5.2.2.2. Use when a protocol service definition declares its per-primitive parameter lists and they have to hold together before baseline: check every parameter for a name, a type and a presence category, refuse a conditional parameter with no stated condition, reject duplicate or unnamed entries, then align each request against its paired indication, response and confirm so no mandatory parameter is dropped across the pair and no parameter appears that the originator never supplied. Trigger: ecss, e-st-50-53, service-primitive-semantics-subclause, primitive-parameter-list, parameter-presence-category, conditional-parameter-condition, request-indication-pair-alignment, spacewire-service-definition."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/e5053-semantics15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-50-spacewire-scope, e5053-semantics, service-primitive-semantics-subclause, primitive-parameter-list, parameter-presence-category, request-indication-pair-alignment, spacewire-service-definition]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS SpaceWire Service Primitive — Semantics Subclause (space-systems/ecss/e5053-semantics)2324Use when the task is the semantics subclause of ECSS-E-ST-50-53 clause255.2.2.2 — the parameter list a service primitive carries, the presence26category of each parameter, and whether the four primitives of one27service still describe the same exchange when read together.2829## Domain quick reference3031- The semantics subclause is the only place a primitive's parameters are32 declared. Each entry needs three things to be implementable: a name a33 caller can bind, a type that fixes its representation, and a presence34 category saying whether it is always there, there under a stated35 condition, or at the user's discretion.36- Conditional presence without the condition is the defect that looks37 like a complete entry. An implementer reading it has to guess when to38 supply the parameter, and two implementations will guess differently.39- A service is specified as up to four primitives around one exchange:40 request and confirm at the originating user, indication and response at41 the peer. They are not independent lists. A parameter the originator42 must always supply cannot vanish on the way to the indication, and the43 indication cannot require a parameter the request never carried unless44 the service provider itself generates it.45- Relaxation across a pair is legitimate in one direction only. A46 mandatory request parameter may arrive as conditional at the indication47 when the provider may legitimately withhold it; the reverse, a48 conditional request parameter that is mandatory at the indication, is49 unimplementable.50- Duplicate parameter names inside one primitive are a specification51 error rather than a finding: the list can no longer be indexed, so52 nothing downstream of it can be graded.5354## Workflow55561. Validate each parameter entry: name present and non-empty, type57 present and non-empty, presence category inside the closed set of58 mandatory, conditional and optional, and a condition supplied for59 every conditional entry.602. Build the per-primitive parameter index, refusing a list that names61 one parameter twice once case and surrounding space are normalised.623. Split each primitive name into its service and its kind so the four63 primitives of a service can be grouped without relying on ordering.644. Group the specification by service and check that a service declares65 at most one primitive of each kind.665. For each service holding a request, align every partner primitive67 against it: report a mandatory request parameter absent from the68 partner, a partner parameter that the request never declared and that69 is not listed as provider generated, and a partner parameter whose70 presence category is stronger than the one the request gave it.716. Roll the per-primitive and per-service findings up into a compliant72 count against the total so a partially clean service definition can be73 reported without hiding the failures.7475## Pitfalls7677- Grading a primitive in isolation. Every entry can be well formed and78 the service still be unimplementable, because the defect lives in the79 relationship between the request and its indication.80- Treating an optional parameter as free. Optional at the request and81 mandatory at the indication is the same unimplementable pairing as the82 conditional case, only harder to see.83- Accepting conditional presence with the condition written in the84 additional comments subclause. The condition has to sit with the85 parameter, otherwise the entry is incomplete wherever the reader is.86- Matching parameter names case sensitively. A list carrying both a87 lowercase and a capitalised spelling of one name is a duplicate, and88 passing it through produces two bindings for one field.89- Adding a provider-generated parameter to an indication without90 declaring it as such. It then reads as a request parameter that was91 lost, and the real finding is buried under a false one.9293## Behavior contract (gate 3)9495The parameter validation, presence-category enforcement, duplicate96rejection, primitive-name splitting, service grouping, pair alignment and97roll-up are exercised by the gate 3 contract test:98scripts/test_e5053_semantics.py against scripts/e5053_semantics_logic.py99(stdlib unittest, offline). Run:100python3 scripts/test_e5053_semantics.py101102## Compliance103104- ECSS standards are freely downloadable (ESA); cite the source and105 paraphrase per standards-map.yaml.106- compliance: STANDARDS-REF, gated: false.