Guidelines, not principles — and opt-in

What the community is creating are guidelines, not principles: practical, opt-in standards of behaviour rather than additions to the foundational principle set.

Deliberately left open

What "opt-in" means once registration on the tool is gated on agreement (F2) interacts with OD-007 (re-agreement when guidelines change).

What 'opt-in' means when tool access is gated on agreement

The guidelines are framed as opt-in, but F2 gates registration on agreeing to them, and OD-007 governs whether members must re-agree when the guidelines change. 'Opt-in' and 'you must agree to participate' are in tension.

If left open If unresolved, the tool can appear to compel agreement while the guidelines claim to be voluntary — undermining the legitimacy the opt-in framing is meant to protect, and leaving re-agreement behaviour undefined when drafts are revised.

Options for resolution

Keep agreement as a soft acknowledgement (read + understood) rather than binding consent
Require agreement only for features that need it, leaving read-only guideline access open
Define an explicit OD-007 re-agreement rule (e.g. re-prompt only on material changes)

Where this comes from · 2 source items

This draft merges what the community actually said across 2 source items — every source ID is permanent and traceable.

GTC-067 These are guidelines, not principles
OPIN-093 Loves community guidelines idea – opt in or out, not principles

Themes · governance and legitimacy · education and onboarding

Your signal on this draft

Sentiment only — no action is taken from these tallies. You can change it any time.

Comments · members only

Comments and tallies are visible to registered members. Log in.