Reviews
Reviewing a proposed weight change in Tensormorph means loading a weight-space pull request - a Lob-side reviewable object representing a proposed change - and using Tensormorph's existing inspection and comparison tools against it, rather than a separate review-specific feature.
What's confirmed
Tensormorph can load a weight-space pull request and treat it as an ordinary comparison pair: the proposal's result as the candidate, its base as the baseline. Every comparison tool already documented elsewhere applies directly:
- Structural Diff - confirm the proposal didn't change architecture unexpectedly.
- Weight Diff - see exactly which tensors changed and by how much.
- Merge Conflicts - check whether the proposal conflicts with other pending changes to the same base.
- CI Validation - run the same diagnostics headlessly as part of a review gate.
A reviewer using Tensormorph this way is doing the same work a code reviewer does with a diff view - the review content (what changed, is it correct) is confirmed; a dedicated approve/comment/request-changes workflow layered on top is not.
What isn't yet decided
Whether Tensormorph surfaces an in-app approval action that writes back to Lob, or stays read-only (review here, approve through a Lob-native tool) is the same open question Merge Conflicts raises for conflict resolution - don't build against a specific approval UI until that's settled.
Related resources
- Merge Conflicts - the closest confirmed analogue to a review workflow.
- Versions and Branches - how a reviewed proposal is addressed and pinned.
- CI Validation - automating part of what a review checks for.