ECSS Packet Utilization — On-board Parameter Definition (space-systems/ecss/e7041-parameter-definition)
Use when the task is the parameter definition of ECSS-E-ST-70-41C
clause 6.20.3 -- the two normative items that say what an on-board
parameter the parameter management service handles must be, before
any request to report or set one can be written.
Domain quick reference
- Two items carry the whole clause, and both are about making a
request answerable: a parameter must be nameable, and its value
must be checkable.
- Nameable means a unique parameter identifier within its application
process. Uniqueness is scoped to the process, so two processes may
each hold a parameter of the same name and they are two parameters.
- Checkable means the definition declares how the value is
represented -- what kind of value it is and, for an integer, how
many bits it occupies and whether it is signed.
- The representable domain follows from that declaration. It is
derived with integer arithmetic from the width and signedness, not
typed in by hand, because a hand-typed bound drifts from the width
it is supposed to describe.
- Engineering limits are a separate, narrower thing. A definition may
declare limits inside the representable domain; limits outside it
are a defect in the definition, not a wider domain.
- The effective domain a value must satisfy is the intersection:
representable and within limits. Checking only one of the two lets
a value through that the other rejects.
- A boolean takes exactly two values, an enumerated parameter exactly
the codes it declares, and an octet string any byte sequence up to
its declared length. Each needs its own membership rule.
- Read-only is a property of the definition, so it belongs here even
though only the set request acts on it.
Workflow
- Normalize one definition at a time: identifier, application
process, representation, and whatever the representation requires
-- width and signedness for an integer, codes for an enumerated
parameter, a length for an octet string.
- Reject a representation the service does not handle rather than
falling through to a permissive default.
- Derive the representable domain from the declaration using integer
arithmetic, so the bound and the width can never disagree.
- Read any declared engineering limits, reject a lower limit above
an upper one, and reject limits that fall outside the representable
domain.
- Intersect the two into the effective domain the definition will
accept, and carry both so a rejection can say which one bit.
- Normalize the catalogue, rejecting a repeated identifier inside one
application process and allowing the same name under another.
- Decide membership for a candidate value against the effective
domain and the representation's own membership rule, and return the
reason rather than a bare verdict.
Pitfalls
- Making an identifier unique across the whole spacecraft. Two
application processes then cannot each hold a parameter of the same
name, which the clause allows and real catalogues rely on.
- Making an identifier unique per catalogue file rather than per
application process. The same name under one process passes because
it arrived in two files.
- Typing the representable bound in by hand next to the width. The
two drift, and the definition then accepts a value the on-board
representation cannot hold.
- Deriving an integer bound through floating-point exponentiation.
It is not correctly rounded, so a wide parameter's bound lands one
count out on one platform and not another.
- Treating engineering limits as the whole domain. A value inside the
limits but outside the representation is accepted and truncates on
the way down.
- Treating the representation as the whole domain. A value the
hardware can hold but the subsystem cannot survive is accepted.
- Accepting a boolean as the integers zero and one. The set request
then writes an integer into a parameter nothing will read as one.
- Leaving read-only off the definition. The set request has nowhere
to look and writes a parameter that was never writable.
Behavior contract (gate 3)
The definition normalization, representation handling, integer domain
derivation, engineering limit validation, effective domain
intersection, per-process identifier uniqueness, representation
membership rules and value decision are exercised by the gate 3
contract test: scripts/test_e7041_parameter_definition.py against
scripts/e7041_parameter_definition_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e7041_parameter_definition.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e7041-parameter-definition3description: "Validate the on-board parameter definitions the parameter management service works from under ECSS-E-ST-70-41C clause 6.20.3. Use when a parameter catalogue is being reviewed before any report or set request is built against it: enforcing one unique parameter identifier per application process while letting two processes reuse a name, requiring every definition to declare the representation of its value, deriving the representable domain of an integer definition from its width and signedness rather than a hand-typed bound, narrowing that domain by any declared engineering limits, and deciding whether a candidate value belongs to a definition at all. Trigger: ecss, e-st-70-41-packet-utilization-scope, on-board-parameter-definition, parameter-identifier-uniqueness, parameter-value-representation, parameter-value-domain-check."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/e7041-parameter-definition15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-70-41-packet-utilization-scope, e7041-parameter-definition, on-board-parameter-definition, parameter-identifier-uniqueness, parameter-value-representation, parameter-value-domain-check]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Packet Utilization — On-board Parameter Definition (space-systems/ecss/e7041-parameter-definition)2324Use when the task is the parameter definition of ECSS-E-ST-70-41C25clause 6.20.3 -- the two normative items that say what an on-board26parameter the parameter management service handles must be, before27any request to report or set one can be written.2829## Domain quick reference3031- Two items carry the whole clause, and both are about making a32 request answerable: a parameter must be nameable, and its value33 must be checkable.34- Nameable means a unique parameter identifier within its application35 process. Uniqueness is scoped to the process, so two processes may36 each hold a parameter of the same name and they are two parameters.37- Checkable means the definition declares how the value is38 represented -- what kind of value it is and, for an integer, how39 many bits it occupies and whether it is signed.40- The representable domain follows from that declaration. It is41 derived with integer arithmetic from the width and signedness, not42 typed in by hand, because a hand-typed bound drifts from the width43 it is supposed to describe.44- Engineering limits are a separate, narrower thing. A definition may45 declare limits inside the representable domain; limits outside it46 are a defect in the definition, not a wider domain.47- The effective domain a value must satisfy is the intersection:48 representable and within limits. Checking only one of the two lets49 a value through that the other rejects.50- A boolean takes exactly two values, an enumerated parameter exactly51 the codes it declares, and an octet string any byte sequence up to52 its declared length. Each needs its own membership rule.53- Read-only is a property of the definition, so it belongs here even54 though only the set request acts on it.5556## Workflow57581. Normalize one definition at a time: identifier, application59 process, representation, and whatever the representation requires60 -- width and signedness for an integer, codes for an enumerated61 parameter, a length for an octet string.622. Reject a representation the service does not handle rather than63 falling through to a permissive default.643. Derive the representable domain from the declaration using integer65 arithmetic, so the bound and the width can never disagree.664. Read any declared engineering limits, reject a lower limit above67 an upper one, and reject limits that fall outside the representable68 domain.695. Intersect the two into the effective domain the definition will70 accept, and carry both so a rejection can say which one bit.716. Normalize the catalogue, rejecting a repeated identifier inside one72 application process and allowing the same name under another.737. Decide membership for a candidate value against the effective74 domain and the representation's own membership rule, and return the75 reason rather than a bare verdict.7677## Pitfalls7879- Making an identifier unique across the whole spacecraft. Two80 application processes then cannot each hold a parameter of the same81 name, which the clause allows and real catalogues rely on.82- Making an identifier unique per catalogue file rather than per83 application process. The same name under one process passes because84 it arrived in two files.85- Typing the representable bound in by hand next to the width. The86 two drift, and the definition then accepts a value the on-board87 representation cannot hold.88- Deriving an integer bound through floating-point exponentiation.89 It is not correctly rounded, so a wide parameter's bound lands one90 count out on one platform and not another.91- Treating engineering limits as the whole domain. A value inside the92 limits but outside the representation is accepted and truncates on93 the way down.94- Treating the representation as the whole domain. A value the95 hardware can hold but the subsystem cannot survive is accepted.96- Accepting a boolean as the integers zero and one. The set request97 then writes an integer into a parameter nothing will read as one.98- Leaving read-only off the definition. The set request has nowhere99 to look and writes a parameter that was never writable.100101## Behavior contract (gate 3)102103The definition normalization, representation handling, integer domain104derivation, engineering limit validation, effective domain105intersection, per-process identifier uniqueness, representation106membership rules and value decision are exercised by the gate 3107contract test: scripts/test_e7041_parameter_definition.py against108scripts/e7041_parameter_definition_logic.py109(stdlib unittest, offline). Run:110python3 scripts/test_e7041_parameter_definition.py111112## Compliance113114- ECSS standards are freely downloadable (ESA); cite the source and115 paraphrase per standards-map.yaml.116- compliance: STANDARDS-REF, gated: false.