SignalSmith

SigSaw™

Fixes your Node/TypeScript build. Proves it worked. Every time.

Terminal-native. Local-first. No Green without sealed Proof (verify must PASS).

Why teams reach for SigSaw™

Your CI is red. You've Googled the error, tried three Stack Overflow answers, and you're still staring at a failing tsc output.

When you finally fix it, nobody knows what you changed or why it worked. SigSaw™ fixes the build and proves exactly what it did.

The contract

SigSaw™ is a terminal-native, local-first build-fix operator for Node/TypeScript repos with enforceable guarantees:

  • ✅ Green with Proof (only success state)
  • 🟡 Approval Needed
  • 🛑 Blocked with Strategy Cards (≥3 structured options)
  • No Green without sealed Proof (verify must PASS): hash-verified receipts, commands, environment, and diff binding
  • No Execute without a locked plan (plus blast radius and capability snapshot)
  • No Learning without verified proof (playbooks are proof-gated)
  • No Black Box Decisions (every approval and step is ledgered)

Plans can be previewed. Proof is produced only after execution and sealing.

How it works

Diagnose

SigSaw reads your build output and identifies the error signature that needs to be resolved.

Plan

It generates a locked strategy with a blast radius score, and nothing runs without your approval.

Execute

Commands run under capability constraints, with no network egress and no out-of-scope writes.

Verify

The fix is checked against a deterministic proof checklist, and it only turns green when every check passes.

Example run

$ sigsaw fix

[Diagnose] TS2322: Type 'string' is not assignable to type 'number'
           src/utils/parser.ts:47:12

[Plan]     Strategy: Add explicit type cast (blast radius: 1, risk: low)
           Approve? [Y/n]

[Execute]  Applied fix to src/utils/parser.ts
[Verify]   ✓ diff produced
           ✓ tsc exit 0
           ✓ error signature resolved
           ✓ no new errors introduced

[Green]    Proof bundle sealed → .sigsaw/runs/run-0042/proof.json

Every run ships with a sealed proof bundle so reviewers can verify what changed, what commands ran, and why the fix is trusted.

When to use SigSaw™

  • CI is red and you need a fix you can trust
  • You want every change to ship with receipts
  • The problem is dependencies, TypeScript errors, or lint failures
  • You care about safety as much as speed

Status / Availability

Private alpha. We're testing with a small group of Node/TypeScript teams. Join the waitlist to get early access updates.

Join the waitlist →
Repository (coming soon)

Public repository link will be published after field testing.

Disclaimer

SigSaw™ operates locally in your working directory. All changes are logged in the run ledger and can be reviewed or rolled back. We recommend using version control and reviewing proof bundles before merging. Provided “as is” without warranty.