|
tin
1.5.9
|
The generation pipeline keeps machine behavior reviewable while letting tools produce diagrams, simulators, and implementation scaffolds from the same machine description.
C++ is the production authoring surface. Use it when the machine is already part of the firmware, library, or application.
.hsm is the compact review surface. Use it when a machine needs to be edited or reviewed outside C++ syntax while still lowering to the same state/event model.
YAML and JSON are the tooling surfaces. Use YAML for hand-authored machines and JSON as the stable interchange format between importers, validators, generators, diagrams, and test harnesses.
Every generated path should pass through validation:
Validation catches:
The .hsm importer performs additional syntax and inference checks before emitting JSON.
Diagram exports are review artifacts generated from the machine definition:
The tin artifact manifest indexes target, runtime, transport, evidence, package version, and generated artifact metadata:
Python export is a simulator artifact:
C++ and pybind11 outputs are scaffolds:
Generated scaffolds are starting points for product integration and should be reviewed like source code.