Some formal system technologies let you "extract" algorithms into other languages. Model checkers like Alloy don't. What you take away is what you learn and what you can use of that learning to convince others.
A good concrete takeaway would be information you could use to design a test suite that breaks the system even where others believe it to be solid.
In a past life, I worked on automatic test pattern generation for sequential logic circuits. Which, if you want to tilt at windmills for little $return (1), is as good a pursuit as any. But it strikes me that this is a very similar problem. Given a description of a state space, create stimulus that covers it, sensitizing all the logic paths in a way that produces an observable result that differs from expectations.
(1) The central lesson of trying to sell test: Electronic Design Automation dollars are like western US water law, the first to divert wins. In the case of EDA, the up-front design tools get all the dollars, and there is hardly a trickle of money left by the time it reaches test phase.
I’d emphasize that using Alloy/TLA is often an iterative process where you refine your model over time. In this way, it’s possibly faster to dig through several iterations in Alloy before identifying a counter-example to a property of interest.
But if you are mostly interested in finding interesting test sets then you should be able to stop once you’ve modeled your actual implementation well enough.
https://repositorio-aberto.up.pt/bitstream/10216/59949/1/000...
http://www.dcc.fc.up.pt/~rvr/resources/MAP-i/2014s7c-mapi.pd...
One application to hardware with Alloy:
http://www.samkirk.com/atpg-in-alloy4/ATPG_in_Alloy.pdf
Honestly, I'd have thought TLA+ would be better of the two for hardware given it deals with concurrent things. Also, it can do stuff similar to SPIN model-checker that was used extensively for hardware verification in the past. For hardware, I'd have experimented with SPIN for lightweight method with ACL2 for heavyweight esp thanks to Jared Davis at Centaur contributing ACL2 components he used.
http://spinroot.com/spin/whatispin.html
https://www.cs.utexas.edu/~jared/publications/2011-memocode-...
Just for kicks, I did some quick Googling on test generation for sequential circuits to see if I could find anything interesting for you. Me, too, as I enjoy seeing what people do in your field. Most were paywalled but this one wasn't:
Alloy will tell you where things are over or under-specified. You can ask the system to generate you scenarios in the "world" so you can see a graphical representation of states. You can test/check your assumptions or operating criteria against the structures/rules of the of the "world" and it'll find and show you counter-examples where things fail. I especially like working in Alloy because it's incremental and interactive, like a REPL for you design work, providing some of the benefits of property-based testing in the design portions of creating your system. Simply put: It helps you think through and explore your design!
So assuming I could specify this system with Alloy, what would I learn? I'm guessing I would at least detect gaps in the protocols and missing error recovery arcs in state machines. But that doesn't yield a correct implementation... it might help me fill in gaps in the validation test coverage space. Is this what I should expect?