Skip to content

feat: exempt BoundaryAction blocks from G-002 signature completeness check#104

Merged
rororowyourboat merged 1 commit intodevfrom
feat/94-g002-boundary-exemption
Mar 4, 2026
Merged

feat: exempt BoundaryAction blocks from G-002 signature completeness check#104
rororowyourboat merged 1 commit intodevfrom
feat/94-g002-boundary-exemption

Conversation

@rororowyourboat
Copy link
Collaborator

Summary

  • G-002 now only enforces the output requirement for BoundaryAction blocks (no inputs by design)
  • Propagates kind as block_type in default block compiler so role info reaches the IR
  • 3 new tests: boundary pass, boundary no-outputs fail, non-boundary no-inputs still fails

Closes #94

…check

BoundaryAction blocks have no inputs by design — they model exogenous
signals entering the system from outside. G-002 now skips the input
requirement for blocks with block_type="boundary" while still requiring
outputs. The default block compiler now propagates the block's kind
field into BlockIR.block_type so role information is available in the IR.
@rororowyourboat rororowyourboat merged commit b71fac2 into dev Mar 4, 2026
@rororowyourboat rororowyourboat deleted the feat/94-g002-boundary-exemption branch March 4, 2026 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

enhancement: exempt BoundaryAction from G-002 signature completeness check

1 participant