[superWorldSavior]

Summary

• The by feature of a satisfy is resolved.

  • Before, satisfy massBudget by budget; came back as an unresolved link ("Unexpected relationship result: VoidExpressionResult").
  • Cause: SysON v2026.7.0's SatisfyRequirementUsageImpl derives satisfyingFeature from a subsetting or a binding connector, never from the FeatureValue that the textual import writes.
  • When the derived accessor is empty, the trace now reads the explicit binding: subjectParameter → FeatureValue → FeatureReferenceExpression.referent.
  • A satisfy without a by feature stays unresolved, with no inferred target.

• Feature chains.

  • For by rover.pack.cell, the referent is an anonymous Feature carrying FeatureChaining.
  • The trace reports the chain's last feature, a real and navigable element, labelled with the whole path (rover.pack.cell).
  • So two cells in different packs stay distinct.

• An empty collection is no longer an error. SysON answers an empty AQL collection with no result type (a StringsExpressionResult the GraphQL query does not select). Two cases reported errors before:

  • a root with requirements but no satisfy relationship: "Could not resolve satisfy relationships…";
  • a root with no requirements: "Unexpected result type: undefined".

  Both are now zero objects. Other unexpected result types still fail.

Test plan

• Each new test failed before its fix with the production symptom:
  • the by fallback;
  • a satisfy without by;
  • the feature chain (it returned the anonymous Feature);
  • no satisfy relationship;
  • no requirements.
• The test for a resolved satisfyingFeature pins the exact AQL sequence: the fallback is not queried when the derived accessor answers.
• deno task fmt, lint, check, test (281 passed).
• Live, on the local audit project:
  • Drone budget goes from 0/3 to 2/3 covered (massBudget and thrustMargin by budget);
  • a chain probe: cellLife by rover.pack.cell → the cell part usage, packLife by rover.pack → pack;
  • Batmobile's batmobileSpecification by batmobileDesignV23;
  • the viewpoint satisfy without by stays unresolved, with "Satisfaction relationship has no explicit satisfying feature";
  • a root without requirements returns 0, with no error.
• Independent review (Sonnet). The feature-chain and empty-collection findings are fixed here, and its test gaps are filled.

🤖 Generated with Claude Code