ECSS Packet Utilization — Set Parameter Values (space-systems/ecss/e7041-set-parameter-values)
Use when the task is the parameter setting request of ECSS-E-ST-70-41C
clause 6.20.4.2 -- writing new values into the on-board parameters a
request names, with the seven normative items that clause places on
the request and its outcome.
Domain quick reference
- The request carries instructions, not identifiers: each one pairs a
parameter identifier with the value to write. Reporting takes names
alone; setting cannot.
- An identifier resolves inside one application process, so the
request says which process it is addressing and an identifier held
by another process does not resolve.
- Three separate refusals sit on one instruction and they are not
interchangeable. The parameter may not exist, the parameter may be
read-only, or the value may not fit. An operator needs to know
which one it was, because the fix differs each time.
- A value must fit the representation AND the engineering domain.
Checking one and not the other lets through a value the other would
have caught, and a set request is the point where that becomes a
spacecraft state rather than a bad report.
- Instructions are independent. One refusal does not withdraw the
ones that already applied, because a request that half-applies and
says so is more useful than one that silently rolls back.
- A request where nothing is applicable fails at start. Nothing is
written and the failure is reported once, rather than as an empty
success.
- A parameter named twice in one request is a ground defect. The last
instruction wins so the outcome is deterministic, and the collision
is raised so the operator finds out.
- The store is not mutated in place. A new store is returned, so the
caller keeps the pre-request state to compare against.
Workflow
- Normalize the store first: each parameter carries an application
process, an identifier, a representation, an optional bounded
domain, an access mode and a current value. Reject a repeated
identifier inside one process.
- Normalize the instruction list: reject a non-list, reject an
instruction that is not an identifier-and-value pair, and reject an
empty request rather than treating it as a no-op success.
- Collapse a parameter named more than once, keeping the last
instruction, and record the collision.
- Resolve each instruction against the store scoped to the named
application process, keeping request order.
- Refuse an instruction that resolves to nothing, one that addresses
a read-only parameter, and one whose value falls outside the
parameter's effective domain -- each with its own distinct reason.
- Fail the request at start when no instruction survives, and write
nothing in that case.
- Apply the surviving instructions into a new store, leaving the
original untouched, and record the previous value beside the new
one for each write.
- Compute applied and refused totals from the recorded outcomes,
check them against the instruction count, and close with the
verdict.
Pitfalls
- Collapsing the three refusal reasons into one rejection code. The
operator cannot tell a typo from a protected parameter from a value
the subsystem will not survive.
- Checking the value against the representation only. A value the
hardware can hold but the subsystem cannot survive is written.
- Checking the value against the engineering limits only. A value
inside the limits but outside the representation truncates on the
way down and lands as something else.
- Rolling back applied writes when a later instruction is refused.
The spacecraft is left in a state no ground record predicts.
- Treating an empty instruction list as a successful no-op. Nothing
was written and the outcome says success.
- Applying both instructions when a parameter is named twice. The
final value depends on iteration order, and two runs of the same
request can leave different states.
- Mutating the store in place. The caller loses the pre-request state
and cannot say what the request actually changed.
- Writing a read-only parameter because the check was left to the
definition-time review. The set path is where it bites.
Behavior contract (gate 3)
The store normalization, instruction normalization, duplicate
collapse, scoped resolution, the three distinct refusals, nothing-
applicable failed start, independent application into a new store,
previous-value recording, outcome totals and their accounting check
are exercised by the gate 3 contract test:
scripts/test_e7041_set_parameter_values.py against
scripts/e7041_set_parameter_values_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e7041_set_parameter_values.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-set-parameter-values3description: "Execute and grade the parameter setting request of ECSS-E-ST-70-41C clause 6.20.4.2. Use when a ground request carries new values for named on-board parameters: resolving each identifier against the application process that holds it, refusing a value that does not fit the parameter's representation or engineering domain, refusing a write to a read-only parameter, applying every sound instruction even when a sibling is refused, failing the request at start only when nothing is applicable, resolving a parameter named twice in one request by last-writer-wins with a finding, and carrying applied and refused totals a receiver can check the outcome against. Trigger: ecss, e-st-70-41-packet-utilization-scope, on-board-parameter-setting, parameter-set-value-domain-refusal, read-only-parameter-write-refusal, parameter-set-outcome-accounting."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-set-parameter-values15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-70-41-packet-utilization-scope, e7041-set-parameter-values, on-board-parameter-setting, parameter-set-value-domain-refusal, read-only-parameter-write-refusal, parameter-set-outcome-accounting]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Packet Utilization — Set Parameter Values (space-systems/ecss/e7041-set-parameter-values)2324Use when the task is the parameter setting request of ECSS-E-ST-70-41C25clause 6.20.4.2 -- writing new values into the on-board parameters a26request names, with the seven normative items that clause places on27the request and its outcome.2829## Domain quick reference3031- The request carries instructions, not identifiers: each one pairs a32 parameter identifier with the value to write. Reporting takes names33 alone; setting cannot.34- An identifier resolves inside one application process, so the35 request says which process it is addressing and an identifier held36 by another process does not resolve.37- Three separate refusals sit on one instruction and they are not38 interchangeable. The parameter may not exist, the parameter may be39 read-only, or the value may not fit. An operator needs to know40 which one it was, because the fix differs each time.41- A value must fit the representation AND the engineering domain.42 Checking one and not the other lets through a value the other would43 have caught, and a set request is the point where that becomes a44 spacecraft state rather than a bad report.45- Instructions are independent. One refusal does not withdraw the46 ones that already applied, because a request that half-applies and47 says so is more useful than one that silently rolls back.48- A request where nothing is applicable fails at start. Nothing is49 written and the failure is reported once, rather than as an empty50 success.51- A parameter named twice in one request is a ground defect. The last52 instruction wins so the outcome is deterministic, and the collision53 is raised so the operator finds out.54- The store is not mutated in place. A new store is returned, so the55 caller keeps the pre-request state to compare against.5657## Workflow58591. Normalize the store first: each parameter carries an application60 process, an identifier, a representation, an optional bounded61 domain, an access mode and a current value. Reject a repeated62 identifier inside one process.632. Normalize the instruction list: reject a non-list, reject an64 instruction that is not an identifier-and-value pair, and reject an65 empty request rather than treating it as a no-op success.663. Collapse a parameter named more than once, keeping the last67 instruction, and record the collision.684. Resolve each instruction against the store scoped to the named69 application process, keeping request order.705. Refuse an instruction that resolves to nothing, one that addresses71 a read-only parameter, and one whose value falls outside the72 parameter's effective domain -- each with its own distinct reason.736. Fail the request at start when no instruction survives, and write74 nothing in that case.757. Apply the surviving instructions into a new store, leaving the76 original untouched, and record the previous value beside the new77 one for each write.788. Compute applied and refused totals from the recorded outcomes,79 check them against the instruction count, and close with the80 verdict.8182## Pitfalls8384- Collapsing the three refusal reasons into one rejection code. The85 operator cannot tell a typo from a protected parameter from a value86 the subsystem will not survive.87- Checking the value against the representation only. A value the88 hardware can hold but the subsystem cannot survive is written.89- Checking the value against the engineering limits only. A value90 inside the limits but outside the representation truncates on the91 way down and lands as something else.92- Rolling back applied writes when a later instruction is refused.93 The spacecraft is left in a state no ground record predicts.94- Treating an empty instruction list as a successful no-op. Nothing95 was written and the outcome says success.96- Applying both instructions when a parameter is named twice. The97 final value depends on iteration order, and two runs of the same98 request can leave different states.99- Mutating the store in place. The caller loses the pre-request state100 and cannot say what the request actually changed.101- Writing a read-only parameter because the check was left to the102 definition-time review. The set path is where it bites.103104## Behavior contract (gate 3)105106The store normalization, instruction normalization, duplicate107collapse, scoped resolution, the three distinct refusals, nothing-108applicable failed start, independent application into a new store,109previous-value recording, outcome totals and their accounting check110are exercised by the gate 3 contract test:111scripts/test_e7041_set_parameter_values.py against112scripts/e7041_set_parameter_values_logic.py113(stdlib unittest, offline). Run:114python3 scripts/test_e7041_set_parameter_values.py115116## Compliance117118- ECSS standards are freely downloadable (ESA); cite the source and119 paraphrase per standards-map.yaml.120- compliance: STANDARDS-REF, gated: false.