[Insert standard boilerplate here - if you're a registered competitor and have a technical question about the Global Learning XPRIZE, please send it to firstname.lastname@example.org to get the most accurate and most timely response.]
Although it makes little difference here (the language is the same, only the formatting changed), please remember that the current version of the GLEXP Guidelines is not the v4 draft but the version incorporated as Exhibit A in the Competitor Agreement all teams signed when registering.
The judges will have latitude to decide how to evaluate submittals and weigh various subjective factors. These assessments are, of course, subjective, and we can't speak for the judges or "pre-judge" a team's work. However, it's reasonable to explain what we mean here.
"Code transparency" is both a design and implementation measure, an evaluation of how self-evident the operation of the code is to a new person looking at it, how easy it is to modify that code, and how practical it is for the code to be repurposed to another (human) language or culture. Since the finalist apps will be released as open source without a large OS community having grown around them, transparency will be important to the adoption and application of that software.
"Resiliency" refers to your software's ability to deal with adverse conditions. To some degree this depends on what your software does and how you respond to unexpected/undesirable situations. It also addresses your ability to identify and plan for such conditions.