Trust level 3 requirements: a clarification

Trust level 3 requirements: a clarification — setting out what I have, and where I think it stops being reliable.

Nominating something for promotion into the documentation commons.

The topic in question keeps being re-asked, has a good marked solution, and contains a worked example that would be more useful on a page with a review date than buried in a reply. That is exactly the promotion criterion as written.

Objections welcome and genuinely wanted — the whole point of discussing promotions in public is that a bad promotion is harder to undo than a bad reply.

This follows the opening post rather than contradicting it.

When announcements are made: major policy changes, technical changes affecting site function, planned downtime, and changes to guidelines all get announced here.

Worth separating two things that the opening post runs together.

Two things before anyone answers the substance.

First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.

Scheduled maintenance: if the site is going offline for maintenance, advance notice will be posted here with the duration and scope.

Picking up post #3: that is the part I would want checked first.

Archives: older announcements are archived by date. Checking archives is useful if you want to know what changed when.

Feedback to announcements: if you have feedback on an announced change (not a question, but your position) post it in the Meta category rather than here.

For anyone arriving from a search: the marked solution above is the direct answer, and the replies underneath it add the caveats that make it safe to use.

Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.

Staff announcements, policy changes, and scheduled maintenance. Read-only except for questions clarifying what was announced.

Implementation timeline: announcements include when a change takes effect. Marking the date helps you know whether the change is already in effect.

Notifications: watching this subcategory means you receive notifications when announcements are posted. Useful if you want to stay current.

I disagree with the reply above, and I think the disagreement is substantive rather than terminological.

The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.

Worth separating two things that post #10 runs together.

Staff-only posts: some announcements are visible only to staff (concerning internal operations). Members see public announcements.