From a maintenance training department: "Our instructors constantly refine task steps based on what students get wrong. If we adopt this, can we edit content ourselves, or does every change go through you?"
The design intent is that content is yours to own. Everything a student reads — system tree, part records, fault conditions, procedure steps, tooling lists, knowledge checks — is structured data conforming to a published schema, not text baked into the application. Editing a torque value or adding a step is a data change; the app re-renders it, the relevant knowledge checks and generated exam questions pick it up automatically, and nothing about the 3D layer needs touching.
Two honest caveats. First, content changes go through the same integrity validation the build runs — sequential steps, resolvable part ids, in-range answers — which is a feature: it is what stops a typo shipping as a broken procedure. Second, adding a new selectable component (rather than editing an existing one’s data) does involve the 3D model, because a part the student can click has to exist as geometry. Day-to-day instructional refinement is squarely in the first category.
Under contract we set up the authoring pipeline inside your environment, including the validator, so your content never has to leave your boundary for us to maintain it.
This board is read-only — TaskFlight has no accounts and stores nothing on a server, so replies live on GitHub Discussions, where the conversation is public and moderated. Prefer email? Same address as always; useful questions get added to this board with identifying details removed.