Add more detail about the desired competition/challenge

[PeterJCLaw]

While the early (v1, v2) versions of the ops manual contained (in my opinion) far too much detail about what was expected in regards to a competition, the current (v7) version has very little detail.

I think it would be useful to add a little bit more detail about the desired shape of the competition, especially given that the current teams structure is fairly coupled to that shape.

Examples of this are the mention of "Kickstart" and "Tech days" within the Competition Team page, without explanation of what those are. One approach here might be to remove these terms in favour of inline descriptions of them/their goals.

Beyond that, a brief description of the types of challenge that the competition should present the competitors might be useful. I suspect that this doesn't need to be more than a paragraph or so, but I'm not sure.

As a starter, I think we should cover:

• that we want the competitors to have to do quite a bit of thinking and discovering for themselves, on a variety of axes, pulling together existing knowledge with the scenario of their robot as well as potentially new learnings (rather than just plugging things together)
• that we want to offer challenges at a range of abilities and to ensure that the competition achieves differentiation in the quality of the teams (and ideally the effort they've put in, though that's a harder thing to achieve)

(I'm hoping there's nothing new here; there are probably many other things we should include, too)

The Competition Team would then be responsible (as they already are) for delivering this, though it likely also impacts other teams (the design of the Kit Service obviously needs to consider the desired level of challenge for example).

[dianedowling]

A new version of the ops manual is being drafted. This should be picked up again when it is circulated for review.

[Scarzy]

I can't recall how much we discussed this at the last changes, however I'm not really sure this is necessary or appropriate. A similar argument can be applied to all of the teams, and it potentially borders on becoming too prescriptive. There is already an expectation for the incoming team to discuss plans for the upcoming cycle with the trustees, which allows these things to be adopted or flexed as needed without having to update the ops-manual each time.

I accept that the terms Kickstart/Tech Days are not sufficiently clear.