Published Selection Criteria¶
Published standard — instantiates Accountable Gatekeeping Design
Publishes the standards and worked examples a gate selects on, before the fact, so anyone can see what passage actually requires.
Published Selection Criteria takes the standard a gate decides by out of the gatekeeper's head and puts it on the record — a standing, public document, written before any given case is judged, that says what the gate is for and what it looks for. Its defining move is ex ante and general: not why one case was refused (that is a per-case notice) but the rule the whole population will be measured against, stated plainly enough that an applicant can read it, judge their own case, and act on it. Where an opaque gate forces everyone to guess and reverse-engineer the standard from rejections, published criteria let people self-select, improve, or decline before they ever reach the gate — and give every later accountability check a fixed benchmark to test actual decisions against.
Example¶
A mobile-app platform maintains public app review guidelines: the rules an app must satisfy before it is allowed into the store. A solo developer, before submitting, reads the section on background location access and sees the rule — apps that track location in the background must show a clear justification and an in-app disclosure. Her draft did neither. Because the criterion is public and comes with a worked example of an acceptable disclosure, she fixes it before submitting rather than absorbing an opaque rejection weeks later. The same published text does double duty when a different app is refused: the developer, the platform's own reviewers, and an outside critic can all point to the exact clause at issue instead of arguing about an unstated standard.
How it works¶
- Externalize before deciding. The rubric is written and published ahead of the decisions it governs, so it constrains the gatekeeper rather than being assembled to fit a case.
- Show, don't just tell. Positive and negative worked examples pin down what the words mean at the margin, where abstract criteria are otherwise read in whatever way suits the decider.
- State the purpose. The document says why the gate exists — the quality, safety, or scarcity interest it protects — so criteria can be read in light of their intent rather than as free-floating hoops.
- Version it. Changes are dated and visible, so the standard's evolution is a matter of record and yesterday's decisions can be read against the rule that was actually in force.
Tuning parameters¶
- Rule vs. standard — bright-line rules ("no more than X") are predictable and checkable but gameable and rigid; open standards ("must be reasonable") flex to hard cases but hand discretion back to the gatekeeper. Where you sit on this axis is the central design choice.
- Example coverage — how many worked cases, and whether they include near-misses. More examples reduce ambiguity but lengthen the document and can be over-fitted to.
- Versioning cadence — how often the criteria are revised and how loudly changes are announced; frequent quiet edits erode the predictability that is the whole point.
- Disclosure depth — how much of the operative rubric is published versus held back to limit gaming; publishing less protects the gate but reintroduces the opacity it was meant to cure.
When it helps, and when it misleads¶
Its strength is predictability and reviewability: applicants know the bar, borderline cases can be argued on the merits, and every downstream audit or appeal has a written standard to check conduct against. It is the benchmark the rest of the archetype's machinery leans on.
Its failure modes live in the gap between the published rule and the applied one. Over-specify, and the criteria become a checklist gamed to the letter while the intent is missed; under-specify, and discretion creeps back in under cover of vague language — the familiar rules-versus-standards trade-off, with no free position on it.[n1] The classic misuse is window dressing: publish anodyne, agreeable criteria while decisions actually turn on unstated ones, so the document reassures without binding. Published criteria therefore need a companion that checks whether real decisions track the published rule; the standard on paper is a claim about behaviour, not proof of it.
How it implements the components¶
Published Selection Criteria fills the stated-standard slice of the archetype — the ex ante, general rule — and nothing case-specific:
passage_criteria_set— it is the explicit, public criteria set, with worked examples fixing the margins.legitimate_gate_purpose— it names the interest the gate exists to protect, so the criteria are legible as means to a stated end rather than arbitrary hoops.
It does not explain any individual decision — that is Reasoned Decision Notice — nor bound the aggregate mix with a hard invariant (that is Quota or Portfolio Guardrail), nor check whether real decisions match the published rule (that is Random Sample Audit). The standards it publishes are typically authored and owned by an Editorial Standards Board.
Related¶
- Instantiates: Accountable Gatekeeping Design — it supplies the public benchmark the gate's other accountability mechanisms test against.
- Consumes: Editorial Standards Board — the body that authors and revises the standards this document publishes.
- Sibling mechanisms: Reasoned Decision Notice · Editorial Standards Board · Quota or Portfolio Guardrail · Random Sample Audit · Independent Review Panel · Appeals or Reconsideration Workflow · Blind or Double-Blind Review · Gatekeeping Decision Log · Algorithmic Ranking Audit · Transparency Report · Conflict-of-Interest Disclosure
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Published Selection Criteria operates by publishes a rubric before cases are decided so it constrains later gatekeeping. That concrete deployed or enacted form is Rule, Policy & Commitment under the frozen taxonomy.
Nearest alternative: Representation, Specification & Plan — Although Representation, Specification & Plan can support this mechanism, the frozen evidence makes its operative form the act that publishes a rubric before cases are decided so it constrains later gatekeeping; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Publishing complete, nondiscriminatory selection criteria before a gate operates is rooted in legal notice and procedural-fairness controls; public-procurement rules expressly require advance publication and prohibit later alteration.
Related originating lineages:
- Organizational & Management Science — Personnel and organizational selection systems provide a broad applied lineage.
- Public Administration & Policy — Public procurement and program eligibility operationalized advance publication at institutional scale.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of law_governance: Publishing complete, nondiscriminatory selection criteria before a gate operates is rooted in legal notice and procedural-fairness controls; public-procurement rules expressly require advance publication and prohibit later alteration. The other materially formative traditions are retained as alternates; current breadth of use remains separate as domain_reach=universal.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
Published criteria say what should happen, not what did. They are necessary but not sufficient: without an audit to detect drift between the published rubric and the applied one, a well-written document can coexist indefinitely with a gate that decides on something else.
[n1] The rules-versus-standards distinction from legal theory: precise rules are predictable and easy to check but invite gaming and handle edge cases badly, while open-ended standards adapt to circumstance but return discretion to the decider and are harder to review consistently. Publishing criteria forces an explicit choice along this axis for every clause. ↩