How the work is really done.
Iron Curriculum is the field context for heavy mobile autonomy: what a competent crew does, in what order and under which rules, written down as use cases and plays, each cited to its source. It is one of the mule.bot systems that Iron Context ties together.
A machine can be specified without the job
The job is in people's heads
How a loader meets a truck, where a truck waits, who gives way at the face. Crews know it. Little of it is written where an engineer can cite it.
Requirements without a source
A requirement says what the machine shall do. With no record of the practice, rule or standard it came from, it cannot be checked against the field.
Edge cases found on site
A blocked dump, a truck spotted wrong, wet ground. These turn up after delivery, when they could have been read from the record first.
Courses, procedures, rules and footage, as one body of evidence
Operator training courses, mine and heavy civil operating procedures, codes of practice and standards say how the work should be done. Field footage shows how it is done. Each clip is labeled by machine, technique and interaction, and read beside the written sources.
Use cases and plays, each with its source
Use case
The job as a crew does it: who takes part, the steps in order, and what ends it. Each one names the course, procedure or rule it was read from.
Play
Who moves, in what order, and where each machine stands. A play is small enough to plan, to drive and to test.
Edge case
The moments that leave the plan, kept beside the use case they belong to, so a test can be written for each.
One chain from the site to the record
A play is where the curriculum meets the plan. The planner picks plays for the day's targets and issues them as work orders; a system carries them out; what happened is recorded. Iron Context is the whole of it: the systems below and the interface between each pair of them, written down, so any one of them can be replaced by yours.
Iron Detector
Where the work is: sites drawn from public registers and imagery, with the machines counted on each.
irondetector.ai ▶ PlanningIron Tactics
Which machine runs which play, where and in what order, turned into work orders a machine can drive.
blockmodel.ai ▶ Test tracksIron Range
Tracks where a planner or a whole autonomy stack drives the plays and leaves a record that replays.
mule.bot ▶ The systemHitch
The connection to your machine or system: the full system less the machine, or the one interface your product needs.
mule.bot ▶Working with us
We share reference traces with the teams we work with. Each follows one site from the public record to a test result. Write to us for access, or sign in if you have a password.