ECSS SMP L2 — Field Link (space-systems/ecss/e4008-field-link)
Use when the task is a field link of an SMP Level-2 assembly artefact per
ECSS-E-ST-40-08C clause 5.2.7.4 — copying one component's field into another's
every time the assembly applies its data flow — and the question is whether the
copy is admissible and unambiguous.
Domain quick reference
- A field link is a copy, not an expression. Nothing is scaled, converted or
combined on the way across, which is why a source and target of different
primitive datatypes is a defect rather than a widening.
- Direction decides which end a field may occupy. An output or a state field
holds a value the model produced, so it can be read; an input or a state
field is consumed by the model, so it can be written. A state field is the
only one that may sit at either end.
- Array shape is part of the type. A three-element vector and a four-element
quaternion are both arrays of the same primitive and are not
interchangeable, so the shapes are compared element count by element count,
with an unset shape meaning scalar.
- One target, one writer. Two links into the same field produce a value that
depends on the order the assembly applies them, and that order is not a
property either link declares — which is what makes the second writer a
defect rather than a race to be tuned.
- The accepted links define the driven-field set, and that set is the input to
the component-configuration check: a field written every step must not also
carry a configured value, because the configured value would not survive the
first propagation.
- A cycle through field links is legal in structure and awkward in behaviour:
the propagated values depend on application order rather than on the links
themselves, so it is surfaced as an advisory instead of a rejection.
Workflow
- Resolve the source endpoint onto a declared field and require its direction
to be readable; resolve the target endpoint and require it to be writeable,
naming the direction in the finding so the repair is obvious.
- Refuse a link whose two endpoints are the same field, and refuse one whose
endpoints sit on the same instance unless the assembly permits self-links.
- Compare the primitive datatypes for identity and reject any pair that would
need a conversion.
- Compute the array shape of both ends, treating an unset dimension list as
scalar, and compare the shapes as tuples.
- Record the writer of each target field and reject a second link into a
target that already has one, naming the link that claimed it.
- Emit the sorted driven-field set so the configuration check can refuse a
configured value on a linked field.
- Walk the instance-level dataflow graph of the accepted links and report any
cycle as an ordering advisory alongside the findings.
Pitfalls
- Allowing a widening datatype pair. It looks harmless in a review and makes
the assembly depend on a conversion that the copy semantics do not provide.
- Comparing only the number of dimensions. Two one-dimensional arrays of
different extents pass a rank check and then truncate or overrun on copy;
the extents themselves have to match.
- Treating an unset dimension list as an array of one. A scalar field and a
one-element array are different shapes, and conflating them lets a scalar
drive an array target.
- Accepting a second writer because both links are individually valid. Nothing
in either link is wrong; the defect exists only in their combination, so it
is invisible to any check that grades one link at a time.
- Grading the configuration block and the field links separately. A field with
both a configured value and an incoming link looks correct in each artefact;
the driven-field set is what makes the conflict visible.
- Failing an assembly for a dataflow cycle. The cycle is an order dependency,
not an invalid link, and rejecting it outright blocks legitimate feedback
structures that the schedule resolves.
Behavior contract (gate 3)
The direction-checked endpoint resolution, datatype identity, array-shape
comparison, single-writer rule, self-link handling, driven-field export and
cycle detection are exercised by the gate 3 contract test:
scripts/test_e4008_field_link.py against
scripts/e4008_field_link_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e4008_field_link.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e4008-field-link3description: "Evaluate the field links of an SMP Level-2 assembly artefact against ECSS-E-ST-40-08C clause 5.2.7.4: resolve the source onto a readable output or state field and the target onto a writeable input or state field, require identical primitive datatypes because a link copies rather than converts, require identical array shape, refuse a second writer into one target field, and refuse a field linked to itself. The driven-field set the configuration check needs is returned, and a dataflow cycle is raised as an ordering advisory. Use when a value never propagates or two writers fight over one field. Trigger: ecss, e-st-40-08c, smp-level-2, assembly-field-link, field-direction-rule, field-datatype-match, single-writer-field-target, field-link-dataflow-cycle."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/e4008-field-link15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-40-08c-smp-level-2, e4008-field-link, smp-assembly-artefact, assembly-field-dataflow, field-link-direction-rule, field-link-datatype-match, single-writer-field-target]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS SMP L2 — Field Link (space-systems/ecss/e4008-field-link)2324Use when the task is a field link of an SMP Level-2 assembly artefact per25ECSS-E-ST-40-08C clause 5.2.7.4 — copying one component's field into another's26every time the assembly applies its data flow — and the question is whether the27copy is admissible and unambiguous.2829## Domain quick reference3031- A field link is a copy, not an expression. Nothing is scaled, converted or32 combined on the way across, which is why a source and target of different33 primitive datatypes is a defect rather than a widening.34- Direction decides which end a field may occupy. An output or a state field35 holds a value the model produced, so it can be read; an input or a state36 field is consumed by the model, so it can be written. A state field is the37 only one that may sit at either end.38- Array shape is part of the type. A three-element vector and a four-element39 quaternion are both arrays of the same primitive and are not40 interchangeable, so the shapes are compared element count by element count,41 with an unset shape meaning scalar.42- One target, one writer. Two links into the same field produce a value that43 depends on the order the assembly applies them, and that order is not a44 property either link declares — which is what makes the second writer a45 defect rather than a race to be tuned.46- The accepted links define the driven-field set, and that set is the input to47 the component-configuration check: a field written every step must not also48 carry a configured value, because the configured value would not survive the49 first propagation.50- A cycle through field links is legal in structure and awkward in behaviour:51 the propagated values depend on application order rather than on the links52 themselves, so it is surfaced as an advisory instead of a rejection.5354## Workflow55561. Resolve the source endpoint onto a declared field and require its direction57 to be readable; resolve the target endpoint and require it to be writeable,58 naming the direction in the finding so the repair is obvious.592. Refuse a link whose two endpoints are the same field, and refuse one whose60 endpoints sit on the same instance unless the assembly permits self-links.613. Compare the primitive datatypes for identity and reject any pair that would62 need a conversion.634. Compute the array shape of both ends, treating an unset dimension list as64 scalar, and compare the shapes as tuples.655. Record the writer of each target field and reject a second link into a66 target that already has one, naming the link that claimed it.676. Emit the sorted driven-field set so the configuration check can refuse a68 configured value on a linked field.697. Walk the instance-level dataflow graph of the accepted links and report any70 cycle as an ordering advisory alongside the findings.7172## Pitfalls7374- Allowing a widening datatype pair. It looks harmless in a review and makes75 the assembly depend on a conversion that the copy semantics do not provide.76- Comparing only the number of dimensions. Two one-dimensional arrays of77 different extents pass a rank check and then truncate or overrun on copy;78 the extents themselves have to match.79- Treating an unset dimension list as an array of one. A scalar field and a80 one-element array are different shapes, and conflating them lets a scalar81 drive an array target.82- Accepting a second writer because both links are individually valid. Nothing83 in either link is wrong; the defect exists only in their combination, so it84 is invisible to any check that grades one link at a time.85- Grading the configuration block and the field links separately. A field with86 both a configured value and an incoming link looks correct in each artefact;87 the driven-field set is what makes the conflict visible.88- Failing an assembly for a dataflow cycle. The cycle is an order dependency,89 not an invalid link, and rejecting it outright blocks legitimate feedback90 structures that the schedule resolves.9192## Behavior contract (gate 3)9394The direction-checked endpoint resolution, datatype identity, array-shape95comparison, single-writer rule, self-link handling, driven-field export and96cycle detection are exercised by the gate 3 contract test:97scripts/test_e4008_field_link.py against98scripts/e4008_field_link_logic.py (stdlib unittest, offline). Run:99python3 scripts/test_e4008_field_link.py100101## Compliance102103- ECSS standards are freely downloadable (ESA); cite the source and104 paraphrase per standards-map.yaml.105- compliance: STANDARDS-REF, gated: false.