Skip to content

Carry each tile's module parameters in the capability contract - #217

Merged
timkpaine merged 2 commits into
mainfrom
tkp/contract-tile-params
Oct 24, 2026
Merged

timkpaine merged 2 commits into
mainfrom
tkp/contract-tile-params

Conversation

@timkpaine

Copy link
Copy Markdown
Member

The capability contract described each tile by registry identity, opcodes and config, but not the module parameters it was built with. A mask, exact-branch or hash key-mask dispatcher therefore looked the same to a planner matching against a resident shell, and the exact-branch mode drops every row whose key is not a branch id.

TileCapability gains params: every parameter the tile declares, at its override or its default. The manifest mapping carries them under params. A mapping without them, as manifests written before this change are, reads as (), so a reader that needs a parameter treats it as unknown. The contract schema stays 1, following how reconfigurable was added.

Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown

Test Results

603 tests  +1   603 ✅ +1   1m 7s ⏱️ -8s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 6f8ff2a. ± Comparison against base commit b9d60a2.

@timkpaine
timkpaine merged commit 6481802 into main Oct 24, 2026
3 checks passed
@timkpaine
timkpaine deleted the tkp/contract-tile-params branch October 24, 2026 19:37
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.

1 participant