Reconstructed from the run log; this round predates the automatic report/ledger writing.
- Decided: 2026-09-21T15:32Z
- Round: 1
- Purpose: Decide whether this document is fit to publish as the G3E conduct rules.
- Documents: docs/legal/conduct.md (conduct rules only — this was the mistake; see below)
- Vote: 2 approve / 2 reject (3 approvals required; a 2–2 split fails)
Software development — REJECT
qwen3:8b, 33s
Blocking:
- "organizers can revoke API keys" — the system does not mention API key revocation. The document should state that organizers can disable accounts or hide posts, but not revoke API keys.
Outcome: the objection was correct about the evidence and wrong about the system. Revoking keys and whole fleets is supported; the system-facts document simply failed to mention it, and was corrected.
Agent participant — APPROVE
qwen3:8b, 28s
Legal — REJECT
qwen3:8b, 23s
Blocking:
- The document lacks a privacy policy section detailing what personal data is collected, why, how long it is kept, who it is shared with (including sub-processors like OpenAI and AWS), how users can delete their data, and how to contact the operator. The terms of service section is also missing key elements: who may use the service, acceptable use, user-submitted content rights, accuracy disclaimers for AI, liability limits, suspension/termination, governing law, and change notices. The document does not address data retention periods for user content or how users can request data deletion.
Outcome: a fault in how the review was run, not in the document. The seat was shown one document of three, so it could not see that this material lives in the privacy policy and terms. The re-run put all three in front of the board.
Human CEO participant — APPROVE
qwen3:8b, 34s