ECSS SMP L2 — Event Link (space-systems/ecss/e4008-event-link)
Use when the task is an event link of an SMP Level-2 assembly artefact per
ECSS-E-ST-40-08C clause 5.2.7.3 — wiring an event source published by one
instance to an event sink published by another, and deciding whether the
emission will actually reach the handler.
Domain quick reference
- An event element has a fixed role. A source emits; a sink receives. The two
are not symmetric ends of one concept, so a link written with the roles
swapped resolves to two real elements and still connects nothing.
- The argument is part of the contract, not decoration. A source that carries a
duration and a sink that expects an integer are both well formed on their
own; the link between them is what is not, and it is the only place the
mismatch can be seen.
- The void argument means "this event carries no value". It is a declared
argument type, distinct from an argument that was omitted from the model.
Treating void as a wildcard lets a typed emission reach a handler that has
nowhere to put it.
- Fan-out is the normal shape: one source reaching many sinks is how a single
tick drives a whole subsystem, and none of those links constrains the others.
- Fan-in is legal but not neutral. Several sources reaching one sink are
invoked in the order the assembly declares them, so the assembly file becomes
load-bearing for behaviour; that deserves an advisory even when every link is
individually valid.
Workflow
- Resolve the emitting endpoint onto a declared event element and require its
declared role to be source; do the same for the receiving endpoint with the
sink role, so a reversed link is named as such.
- Read the argument type each end declares, defaulting an unstated argument to
void rather than to "any".
- Compare the two arguments for identity. Admit a void sink receiving a
carried argument only when the assembly explicitly permits the argument to
be discarded.
- Refuse a link whose source and sink sit on the same instance unless the
assembly permits self-links.
- Form the (source path, sink path) signature and refuse a second link with a
signature already present.
- Group the accepted links by source to produce the fan-out map, and by sink
to find the fan-in cases that need an invocation-order advisory.
- Report the accepted links, the fan-out map, advisories and findings
separately, so an ordering caution never reads as a rejection.
Pitfalls
- Reading void as a wildcard. It makes every source appear connectable to every
argument-less sink, and the defect only appears when the handler needs the
value that was never delivered.
- Accepting a link because both endpoints exist. Existence is the first check,
not the whole one; a sink named at the emitting end is a declared element and
a wrong one.
- Reporting fan-in as an error. Several sources into one sink is a normal
pattern; the risk is the hidden ordering dependency, which an advisory
surfaces without failing a valid assembly.
- Deduplicating on the link name instead of the endpoint pair. Two differently
named links between the same source and sink deliver the event twice, and
only an endpoint-pair signature sees it.
- Assuming the argument is optional because the model compiled. Argument
agreement is an assembly-time question; the two components are built
separately and neither one can detect the mismatch on its own.
Behavior contract (gate 3)
The role-checked endpoint resolution, argument-compatibility rule including the
void case and the discard option, self-link rule, duplicate-signature detection,
fan-out mapping and fan-in advisory are exercised by the gate 3 contract test:
scripts/test_e4008_event_link.py against
scripts/e4008_event_link_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e4008_event_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-event-link3description: "Assess the event links of an SMP Level-2 assembly artefact against ECSS-E-ST-40-08C clause 5.2.7.3: resolve each endpoint onto a declared event element with the right role, refusing a sink used as an emitter or a source used as a receiver, then compare the argument the source carries with the argument the sink expects, treating the void argument as a type of its own rather than an absent one. Fan-out from one source is admitted, fan-in into one sink raises an invocation-order advisory, and an identical link declared twice is refused. Use when an event never reaches its handler or an assembly rejects a wiring. Trigger: ecss, e-st-40-08c, smp-level-2, assembly-event-link, event-source-sink-role, event-argument-compatibility, event-fan-out-ordering, void-event-argument."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-event-link15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-40-08c-smp-level-2, e4008-event-link, smp-assembly-artefact, event-source-sink-binding, event-argument-compatibility, event-link-fan-out, void-event-argument]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS SMP L2 — Event Link (space-systems/ecss/e4008-event-link)2324Use when the task is an event link of an SMP Level-2 assembly artefact per25ECSS-E-ST-40-08C clause 5.2.7.3 — wiring an event source published by one26instance to an event sink published by another, and deciding whether the27emission will actually reach the handler.2829## Domain quick reference3031- An event element has a fixed role. A source emits; a sink receives. The two32 are not symmetric ends of one concept, so a link written with the roles33 swapped resolves to two real elements and still connects nothing.34- The argument is part of the contract, not decoration. A source that carries a35 duration and a sink that expects an integer are both well formed on their36 own; the link between them is what is not, and it is the only place the37 mismatch can be seen.38- The void argument means "this event carries no value". It is a declared39 argument type, distinct from an argument that was omitted from the model.40 Treating void as a wildcard lets a typed emission reach a handler that has41 nowhere to put it.42- Fan-out is the normal shape: one source reaching many sinks is how a single43 tick drives a whole subsystem, and none of those links constrains the others.44- Fan-in is legal but not neutral. Several sources reaching one sink are45 invoked in the order the assembly declares them, so the assembly file becomes46 load-bearing for behaviour; that deserves an advisory even when every link is47 individually valid.4849## Workflow50511. Resolve the emitting endpoint onto a declared event element and require its52 declared role to be source; do the same for the receiving endpoint with the53 sink role, so a reversed link is named as such.542. Read the argument type each end declares, defaulting an unstated argument to55 void rather than to "any".563. Compare the two arguments for identity. Admit a void sink receiving a57 carried argument only when the assembly explicitly permits the argument to58 be discarded.594. Refuse a link whose source and sink sit on the same instance unless the60 assembly permits self-links.615. Form the (source path, sink path) signature and refuse a second link with a62 signature already present.636. Group the accepted links by source to produce the fan-out map, and by sink64 to find the fan-in cases that need an invocation-order advisory.657. Report the accepted links, the fan-out map, advisories and findings66 separately, so an ordering caution never reads as a rejection.6768## Pitfalls6970- Reading void as a wildcard. It makes every source appear connectable to every71 argument-less sink, and the defect only appears when the handler needs the72 value that was never delivered.73- Accepting a link because both endpoints exist. Existence is the first check,74 not the whole one; a sink named at the emitting end is a declared element and75 a wrong one.76- Reporting fan-in as an error. Several sources into one sink is a normal77 pattern; the risk is the hidden ordering dependency, which an advisory78 surfaces without failing a valid assembly.79- Deduplicating on the link name instead of the endpoint pair. Two differently80 named links between the same source and sink deliver the event twice, and81 only an endpoint-pair signature sees it.82- Assuming the argument is optional because the model compiled. Argument83 agreement is an assembly-time question; the two components are built84 separately and neither one can detect the mismatch on its own.8586## Behavior contract (gate 3)8788The role-checked endpoint resolution, argument-compatibility rule including the89void case and the discard option, self-link rule, duplicate-signature detection,90fan-out mapping and fan-in advisory are exercised by the gate 3 contract test:91scripts/test_e4008_event_link.py against92scripts/e4008_event_link_logic.py (stdlib unittest, offline). Run:93python3 scripts/test_e4008_event_link.py9495## Compliance9697- ECSS standards are freely downloadable (ESA); cite the source and98 paraphrase per standards-map.yaml.99- compliance: STANDARDS-REF, gated: false.