Technical reference
Five sections, each with its own page listing what is in it. The split follows the question being asked, not the order things happen.
| Section | Answers |
|---|---|
| Protocol & data | What a message is on the wire, and what it means |
| Platform & configuration | How a fleet is configured, and who is allowed into it |
| Gears catalog | What each gear does and what it accepts |
| Operations & analytics | Running the two processes, and reading what they report |
| Development & QA | Extending the platform, and proving it behaves |
Technical stack sits outside them: it is what fluxrig is built on, and the licence of each dependency.
Where to start
Evaluating. Data model for what travels, then Orchestration scenarios for how a node is composed. The Gears catalog says what can be composed.
Integrating a protocol. ISO8583 SDL describes a dialect, and Protocol reference is the document rendered from one, which is what a counterparty reads.
Running it. Operating fluxrig covers both processes; Platform configuration is every field and its default.
TIP
For the "Studio & Stage" thinking behind the naming, see Design philosophy.