Charter draft v0.3: stewards, mandates and what happens when they fail

The latest charter draft is in the repository. Highlights for those who will not read the whole thing (you should, but I forgive you):

• Stewards are elected for a fixed term, with a hard limit on consecutive terms.
• All steward decisions affecting the registry are logged publicly with reasons.
• Financial reporting is public, in plain language, every quarter.
• A recall process exists: a proportion of members can trigger a vote.
• Exit by design: a member can export their account, names and content, and leave without penalty.

Open question: how many stewards, and how are they elected without a popularity contest? I think the process matters more than the number.

I propose five stewards, staggered terms so that never all five change at once. That preserves knowledge and prevents capture.

Elections must be hard to game. Define membership age and activity requirements for voting, but light, otherwise we exclude newcomers who care.

I'd like at least one steward who is not a programmer. Someone who asks, 'but how would my aunt do this?'

Seconded. And a teacher, because teachers are professional explainers and professional patience-keepers.

Noted, a note in the draft: mixed skill sets encouraged, with the explicit mention of non-technical stewards.

Please publish the charter in all our languages at the same time, not Latin Croatian first and the rest later.