# Rule set: does this position exceed what the board authorised?

slug: ruleset-board-authority-breach · https://miscsubjects.com/a/ruleset-board-authority-breach · category: adjudication · tags: adjudication, ruleset, provenance · updated 2026-07-30T02:35:35.559Z

This rule set is pinned at SHA-256 `0df4794458ac525eb13051621e0058fc7ddeaf1afcef261f1ff7d59c9cf0e815`. A finding made under it names this hash, so a reader a year later can tell whether the rules were the same rules. Amending it produces a new hash and does not silently re-grade any finding already made.

**Declared provenance: `counterparty-authored`.** The governing instrument is the board resolution itself, supplied as the artifact and hashed before the panel ran. The board wrote the rule; this system did not. That is the correct shape for a consequential rule set: the party carrying the liability authors the rule, and the instrument executes it. The clauses below are the adjudication procedure only.

## The question this rule set answers, and only this question

Do the supplied records establish that an executive action exceeded a limit, condition, or authority granted by the supplied governing resolution, such that a notification obligation in that resolution is engaged?

## The clauses, numbered, as supplied to every adjudicator

**1.** The governing instrument is the supplied resolution text. Apply its words. Do not import governance norms, statutes, or standards not present in the supplied text.

**2.** AFFIRM only if the supplied records show an action whose measured value, timing, or counterparty falls outside a limit or condition stated in the resolution, and you can quote both the limit and the record that exceeds it.

**3.** DENY only if the supplied records positively establish the action was inside every stated limit and condition.

**4.** CANNOT_CONCLUDE if the resolution's limit turns on a term the supplied records do not define or measure, if the measurement basis is ambiguous on the face of the records, or if a required approval may exist in a record that was not supplied.

**5.** RECORDS_ABSENT is mandatory. Name every record a competent reviewer would expect and that was not supplied: prior written consent or waiver, minutes of any authorising meeting, the pre-clearance log, the trading plan, the compliance sign-off, and any amendment to the resolution.

**6.** If the resolution states a notification obligation and the finding engages it, name the obligation, name every party the resolution requires to be notified, and state the deadline the resolution sets.

**7.** Never characterise intent. Adjudicate the action against the limit. Intent is not in the records and is not the question.

## What a finding under this rule set must contain

A verdict of AFFIRM, DENY or CANNOT_CONCLUDE; the conditions the adjudicator operated under; the records supplied; **the records absent**; the reasoning with a clause number against each step; what would change the verdict; and a signature naming the model that actually ran. A finding missing RECORDS_ABSENT is void under clause 5, not merely weak.

## Canonical bytes

```json
{"provenance":"counterparty-authored","question":"Do the supplied records establish that an executive action exceeded a limit, condition, or authority granted by the supplied governing resolution, such that a notification obligation in that resolution is engaged?","rules":["The governing instrument is the supplied resolution text. Apply its words. Do not import governance norms, statutes, or standards not present in the supplied text.","AFFIRM only if the supplied records show an action whose measured value, timing, or counterparty falls outside a limit or condition stated in the resolution, and you can quote both the limit and the record that exceeds it.","DENY only if the supplied records positively establish the action was inside every stated limit and condition.","CANNOT_CONCLUDE if the resolution's limit turns on a term the supplied records do not define or measure, if the measurement basis is ambiguous on the face of the records, or if a required approval may exist in a record that was not supplied.","RECORDS_ABSENT is mandatory. Name every record a competent reviewer would expect and that was not supplied: prior written consent or waiver, minutes of any authorising meeting, the pre-clearance log, the trading plan, the compliance sign-off, and any amendment to the resolution.","If the resolution states a notification obligation and the finding engages it, name the obligation, name every party the resolution requires to be notified, and state the deadline the resolution sets.","Never characterise intent. Adjudicate the action against the limit. Intent is not in the records and is not the question."],"slug":"ruleset-board-authority-breach","version":"1.0.0"}
```

Verify the hash yourself:

```bash
curl -s https://miscsubjects.com/api/articles/ruleset-board-authority-breach | python3 -c 'import sys,json,hashlib;b=json.load(sys.stdin);print(b["slug"])'
```

## Sources

1. This rule set as bytes, at 0df4794458ac525e — https://miscsubjects.com/api/articles/ruleset-board-authority-breach


---

# Rule set: were the required pre-trade risk controls in place before the order flow?

slug: ruleset-pretrade-risk-controls · https://miscsubjects.com/a/ruleset-pretrade-risk-controls · category: adjudication · tags: adjudication, ruleset, provenance · updated 2026-07-30T02:35:33.064Z

This rule set is pinned at SHA-256 `e0bb2c0d866450a8964049a9e20860ece2b2a2fdebc75e137f4344e192b15472`. A finding made under it names this hash, so a reader a year later can tell whether the rules were the same rules. Amending it produces a new hash and does not silently re-grade any finding already made.

**Declared provenance: `external-regulatory`.** The question and the operative standard are taken from Rule 15c3-5(c)(1)(i) under the Securities Exchange Act of 1934, quoted verbatim in the artifact supplied to each adjudicator. The clauses below are the adjudication procedure, authored by the operator of this system; the standard being applied is not. A rule set written by the party who benefits from the answer binds less than one written by the party carrying the loss, which is why the provenance field exists and why it says what it says here.

## The question this rule set answers, and only this question

Do the supplied records establish that the financial risk management controls and supervisory procedures required before order entry were in place and operative at the time the order flow was sent?

## The clauses, numbered, as supplied to every adjudicator

**1.** Read only the records supplied. Never rely on recollection of any firm, incident, or filing.

**2.** AFFIRM only if the supplied records show, for the specific order flow in question, that each required control existed, was enabled, and was applied to that flow before entry. A control that exists in configuration but is recorded as disabled for the flow is not in place for that flow.

**3.** DENY only if the supplied records positively establish that a required control was absent, disabled, or bypassed for the flow in question. Name the control and quote the record that establishes it.

**4.** CANNOT_CONCLUDE if the supplied records do not settle the question — including when the control configuration is supplied but no record shows it was applied to this flow, or when the certification or testing record a reviewer would expect is absent.

**5.** RECORDS_ABSENT is mandatory. Name every record a competent reviewer would expect for this question and that was not supplied: control configuration at the time of the flow, change history, the annual CEO certification, test evidence, the kill-switch authority, and the pre-entry log for the specific orders.

**6.** Distinguish a control that did not exist from a control whose operation was not recorded. These carry different consequences and the finding must say which one the records support.

**7.** State whether the records supplied are contemporaneous with the flow or reconstructed after it, and say which, on the face of the records.

## What a finding under this rule set must contain

A verdict of AFFIRM, DENY or CANNOT_CONCLUDE; the conditions the adjudicator operated under; the records supplied; **the records absent**; the reasoning with a clause number against each step; what would change the verdict; and a signature naming the model that actually ran. A finding missing RECORDS_ABSENT is void under clause 5, not merely weak.

## Canonical bytes

```json
{"provenance":"external-regulatory","question":"Do the supplied records establish that the financial risk management controls and supervisory procedures required before order entry were in place and operative at the time the order flow was sent?","rules":["Read only the records supplied. Never rely on recollection of any firm, incident, or filing.","AFFIRM only if the supplied records show, for the specific order flow in question, that each required control existed, was enabled, and was applied to that flow before entry. A control that exists in configuration but is recorded as disabled for the flow is not in place for that flow.","DENY only if the supplied records positively establish that a required control was absent, disabled, or bypassed for the flow in question. Name the control and quote the record that establishes it.","CANNOT_CONCLUDE if the supplied records do not settle the question — including when the control configuration is supplied but no record shows it was applied to this flow, or when the certification or testing record a reviewer would expect is absent.","RECORDS_ABSENT is mandatory. Name every record a competent reviewer would expect for this question and that was not supplied: control configuration at the time of the flow, change history, the annual CEO certification, test evidence, the kill-switch authority, and the pre-entry log for the specific orders.","Distinguish a control that did not exist from a control whose operation was not recorded. These carry different consequences and the finding must say which one the records support.","State whether the records supplied are contemporaneous with the flow or reconstructed after it, and say which, on the face of the records."],"slug":"ruleset-pretrade-risk-controls","version":"1.0.0"}
```

Verify the hash yourself:

```bash
curl -s https://miscsubjects.com/api/articles/ruleset-pretrade-risk-controls | python3 -c 'import sys,json,hashlib;b=json.load(sys.stdin);print(b["slug"])'
```

## Sources

1. This rule set as bytes, at e0bb2c0d866450a8 — https://miscsubjects.com/api/articles/ruleset-pretrade-risk-controls


---

# Rule set: is this the same individual?

slug: ruleset-identity-match · https://miscsubjects.com/a/ruleset-identity-match · category: adjudication · tags: ruleset, adjudication, evidence, self-authored · updated 2026-07-30T00:29:43.265Z

A rule set is the load-bearing object in an adjudication, so it is published as an object: versioned, content-addressed, and citable by the exact hash a finding was made under. When these rules change, every prior finding stays legible against the rules it was actually made under.

## Provenance of these rules

Declared provenance: **self-authored**. Written by the operator against the published face-recognition error literature and deliberately biased toward CANNOT_CONCLUDE. An AFFIRM under these rules is not usable for any consequence without the panel's probe-measured miss rate attached.

A reader who does not trust this operator can price a finding by this field alone: rules written elsewhere bind harder than rules written by the party who benefits from the finding.

## Question

Does the supplied evidence establish that the individual in the query image is the same individual as in the reference?

## Rules

1. AFFIRM only if a stated, checkable feature correspondence is documented and no exclusionary feature is present.
2. DENY if any stable exclusionary feature differs.
3. CANNOT_CONCLUDE for low resolution, occlusion, extreme pose, motion blur, lighting outside the reference conditions, or any case where a feature correspondence cannot be stated. In crowd imagery this is the expected finding and must not be avoided.
4. Resemblance, demographic similarity and clothing are never sufficient for AFFIRM.
5. A finding must name the features relied upon. A finding that cannot name them is CANNOT_CONCLUDE.
6. The panel's probe-measured miss rate under these rules must accompany any AFFIRM before the finding is used for any consequence.

## Permitted verdicts

`AFFIRM` · `DENY` · `CANNOT_CONCLUDE`. Abstention is first class: a panel that cannot conclude says so, and that recorded absence is itself evidence rather than a silent null.

## Content hash

The canonical form is the JSON object `{id, version, question, rules, verdicts}` with no whitespace. SHA-256:

`e3f91b3b3733ca9791f9764b85ad25535a8a2889c74a190028f85791269d6855`

Recompute it from the canonical form below and compare. A finding that names a different hash was made under different rules.

```json
{"id":"ruleset-identity-match","version":"1.0.0","question":"Does the supplied evidence establish that the individual in the query image is the same individual as in the reference?","rules":["AFFIRM only if a stated, checkable feature correspondence is documented and no exclusionary feature is present.","DENY if any stable exclusionary feature differs.","CANNOT_CONCLUDE for low resolution, occlusion, extreme pose, motion blur, lighting outside the reference conditions, or any case where a feature correspondence cannot be stated. In crowd imagery this is the expected finding and must not be avoided.","Resemblance, demographic similarity and clothing are never sufficient for AFFIRM.","A finding must name the features relied upon. A finding that cannot name them is CANNOT_CONCLUDE.","The panel's probe-measured miss rate under these rules must accompany any AFFIRM before the finding is used for any consequence."],"verdicts":["AFFIRM","DENY","CANNOT_CONCLUDE"]}
```

## How a finding under these rules is produced

Each adjudicator is a directory row driven through this system's own gateway. No code was deployed to add them and adding another model is one more row. Every finding records the model, the rule set hash, the quoted span, the exposure (`independent` when the adjudicator saw no other finding, `concurring` when it did), the ordering seed, and a signature. A mandatory recorded adversary argues the strongest honest case against the majority and is published whether it prevails or not.

Adjudicator rows: https://miscsubjects.com/api/directory/ADJUDICATE_KIMI · https://miscsubjects.com/api/directory/ADJUDICATE_GROK · https://miscsubjects.com/api/directory/ADJUDICATE_GLM · https://miscsubjects.com/api/directory/ADJUDICATE_LLAMA · https://miscsubjects.com/api/directory/ADJUDICATE_MINIMAX · adversary: https://miscsubjects.com/api/directory/ADJUDICATE_ADVERSARY · error-rate probe: https://miscsubjects.com/api/directory/ADJUDICATE_PROBE

## What a finding under these rules does and does not establish

It establishes that named adjudicators, under these exact rules at this exact hash, returned these findings on this claim against this source, with their exposure and ordering recorded — at a measured error rate when a probe report is attached.

It does not establish that the claim is true. No adjudication anywhere does that. A court, a journal and a clinical endpoint committee each declare rules, take findings from named parties under those rules, and preserve dissent. This is that structure, with the rule set pinned at a hash instead of scattered through case law.


---

# Rule set: was this specific record in that dataset?

slug: ruleset-dataset-membership · https://miscsubjects.com/a/ruleset-dataset-membership · category: adjudication · tags: ruleset, adjudication, evidence, self-authored · updated 2026-07-30T00:29:42.543Z

A rule set is the load-bearing object in an adjudication, so it is published as an object: versioned, content-addressed, and citable by the exact hash a finding was made under. When these rules change, every prior finding stays legible against the rules it was actually made under.

## Provenance of these rules

Declared provenance: **self-authored**. Written by the operator and deliberately biased toward CANNOT_CONCLUDE, because the failure mode being guarded against is a model asserting membership from resemblance.

A reader who does not trust this operator can price a finding by this field alone: rules written elsewhere bind harder than rules written by the party who benefits from the finding.

## Question

Does the supplied evidence establish that the specific record was present in the named dataset?

## Rules

1. AFFIRM only on a direct identifier match documented in the supplied evidence: an exact record, a hash, or an index entry.
2. DENY only if the evidence positively excludes the record, for example a documented complete enumeration that does not contain it.
3. CANNOT_CONCLUDE for statistical resemblance, partial-field matches, format matches, or any inference from similarity. Similarity is not membership.
4. Absence from the supplied evidence is not absence from the dataset unless the evidence is a documented complete enumeration.
5. Never treat a model's ability to produce a similar-looking record as evidence of membership.
6. Quote the span relied on. If the finding rests on absence, SPAN is NONE and the rationale must state what enumeration was or was not available.

## Permitted verdicts

`AFFIRM` · `DENY` · `CANNOT_CONCLUDE`. Abstention is first class: a panel that cannot conclude says so, and that recorded absence is itself evidence rather than a silent null.

## Content hash

The canonical form is the JSON object `{id, version, question, rules, verdicts}` with no whitespace. SHA-256:

`427e366b460fa21320ce89cd2eb223304e319d8ec57c4ee66e3a998dee966a3d`

Recompute it from the canonical form below and compare. A finding that names a different hash was made under different rules.

```json
{"id":"ruleset-dataset-membership","version":"1.0.0","question":"Does the supplied evidence establish that the specific record was present in the named dataset?","rules":["AFFIRM only on a direct identifier match documented in the supplied evidence: an exact record, a hash, or an index entry.","DENY only if the evidence positively excludes the record, for example a documented complete enumeration that does not contain it.","CANNOT_CONCLUDE for statistical resemblance, partial-field matches, format matches, or any inference from similarity. Similarity is not membership.","Absence from the supplied evidence is not absence from the dataset unless the evidence is a documented complete enumeration.","Never treat a model's ability to produce a similar-looking record as evidence of membership.","Quote the span relied on. If the finding rests on absence, SPAN is NONE and the rationale must state what enumeration was or was not available."],"verdicts":["AFFIRM","DENY","CANNOT_CONCLUDE"]}
```

## How a finding under these rules is produced

Each adjudicator is a directory row driven through this system's own gateway. No code was deployed to add them and adding another model is one more row. Every finding records the model, the rule set hash, the quoted span, the exposure (`independent` when the adjudicator saw no other finding, `concurring` when it did), the ordering seed, and a signature. A mandatory recorded adversary argues the strongest honest case against the majority and is published whether it prevails or not.

Adjudicator rows: https://miscsubjects.com/api/directory/ADJUDICATE_KIMI · https://miscsubjects.com/api/directory/ADJUDICATE_GROK · https://miscsubjects.com/api/directory/ADJUDICATE_GLM · https://miscsubjects.com/api/directory/ADJUDICATE_LLAMA · https://miscsubjects.com/api/directory/ADJUDICATE_MINIMAX · adversary: https://miscsubjects.com/api/directory/ADJUDICATE_ADVERSARY · error-rate probe: https://miscsubjects.com/api/directory/ADJUDICATE_PROBE

## What a finding under these rules does and does not establish

It establishes that named adjudicators, under these exact rules at this exact hash, returned these findings on this claim against this source, with their exposure and ordering recorded — at a measured error rate when a probe report is attached.

It does not establish that the claim is true. No adjudication anywhere does that. A court, a journal and a clinical endpoint committee each declare rules, take findings from named parties under those rules, and preserve dissent. This is that structure, with the rule set pinned at a hash instead of scattered through case law.


---

# Rule set: does an AI Act obligation apply to this system?

slug: ruleset-eu-ai-act-obligation · https://miscsubjects.com/a/ruleset-eu-ai-act-obligation · category: adjudication · tags: ruleset, adjudication, evidence, external-statutory · updated 2026-07-30T00:29:41.901Z

A rule set is the load-bearing object in an adjudication, so it is published as an object: versioned, content-addressed, and citable by the exact hash a finding was made under. When these rules change, every prior finding stays legible against the rules it was actually made under.

## Provenance of these rules

Declared provenance: **external-statutory**. These rules restate the reading discipline for Regulation (EU) 2024/1689. The provision text adjudicated against is the Union's, not this operator's, which is what makes a finding under this rule set bind harder than one under self-authored rules.

A reader who does not trust this operator can price a finding by this field alone: rules written elsewhere bind harder than rules written by the party who benefits from the finding.

## Question

Under the cited provision of Regulation (EU) 2024/1689 (the AI Act), does the stated obligation apply to the described system as characterised?

## Rules

1. Read only the provision text supplied. Do not import obligations, definitions, or annexes from recollection of the Regulation.
2. AFFIRM only if the supplied provision text, on its own terms, imposes the stated obligation on a system of the described characterisation.
3. DENY if the provision excludes the described system, addresses a different actor (provider, deployer, importer, distributor), or imposes a different obligation than the one stated.
4. CANNOT_CONCLUDE if applicability turns on a classification, annex, threshold, or definition not contained in the supplied text.
5. Distinguish the addressee. An obligation on providers is not an obligation on deployers.
6. Quote the shortest verbatim span of the provision that carries the finding.

## Permitted verdicts

`AFFIRM` · `DENY` · `CANNOT_CONCLUDE`. Abstention is first class: a panel that cannot conclude says so, and that recorded absence is itself evidence rather than a silent null.

## Content hash

The canonical form is the JSON object `{id, version, question, rules, verdicts}` with no whitespace. SHA-256:

`0dd9afef93503a92280c90869eaf6a5a13ee508b2ec3506045f1803bce1a4d3c`

Recompute it from the canonical form below and compare. A finding that names a different hash was made under different rules.

```json
{"id":"ruleset-eu-ai-act-obligation","version":"1.0.0","question":"Under the cited provision of Regulation (EU) 2024/1689 (the AI Act), does the stated obligation apply to the described system as characterised?","rules":["Read only the provision text supplied. Do not import obligations, definitions, or annexes from recollection of the Regulation.","AFFIRM only if the supplied provision text, on its own terms, imposes the stated obligation on a system of the described characterisation.","DENY if the provision excludes the described system, addresses a different actor (provider, deployer, importer, distributor), or imposes a different obligation than the one stated.","CANNOT_CONCLUDE if applicability turns on a classification, annex, threshold, or definition not contained in the supplied text.","Distinguish the addressee. An obligation on providers is not an obligation on deployers.","Quote the shortest verbatim span of the provision that carries the finding."],"verdicts":["AFFIRM","DENY","CANNOT_CONCLUDE"]}
```

## How a finding under these rules is produced

Each adjudicator is a directory row driven through this system's own gateway. No code was deployed to add them and adding another model is one more row. Every finding records the model, the rule set hash, the quoted span, the exposure (`independent` when the adjudicator saw no other finding, `concurring` when it did), the ordering seed, and a signature. A mandatory recorded adversary argues the strongest honest case against the majority and is published whether it prevails or not.

Adjudicator rows: https://miscsubjects.com/api/directory/ADJUDICATE_KIMI · https://miscsubjects.com/api/directory/ADJUDICATE_GROK · https://miscsubjects.com/api/directory/ADJUDICATE_GLM · https://miscsubjects.com/api/directory/ADJUDICATE_LLAMA · https://miscsubjects.com/api/directory/ADJUDICATE_MINIMAX · adversary: https://miscsubjects.com/api/directory/ADJUDICATE_ADVERSARY · error-rate probe: https://miscsubjects.com/api/directory/ADJUDICATE_PROBE

## What a finding under these rules does and does not establish

It establishes that named adjudicators, under these exact rules at this exact hash, returned these findings on this claim against this source, with their exposure and ordering recorded — at a measured error rate when a probe report is attached.

It does not establish that the claim is true. No adjudication anywhere does that. A court, a journal and a clinical endpoint committee each declare rules, take findings from named parties under those rules, and preserve dissent. This is that structure, with the rule set pinned at a hash instead of scattered through case law.


---

# Rule set: does the cited source support the claim?

slug: ruleset-claim-support · https://miscsubjects.com/a/ruleset-claim-support · category: adjudication · tags: ruleset, adjudication, evidence, self-authored · updated 2026-07-30T00:29:39.571Z

A rule set is the load-bearing object in an adjudication, so it is published as an object: versioned, content-addressed, and citable by the exact hash a finding was made under. When these rules change, every prior finding stays legible against the rules it was actually made under.

## Provenance of these rules

Declared provenance: **self-authored**. Written by the operator of this system. A finding under self-authored rules is weaker than one made under external statutory rules, and that is declared here rather than left for a reader to discover.

A reader who does not trust this operator can price a finding by this field alone: rules written elsewhere bind harder than rules written by the party who benefits from the finding.

## Question

Does the cited source support the claim as stated?

## Rules

1. AFFIRM only if a verbatim span of the source establishes the claim as stated, without inference beyond ordinary reading.
2. DENY if the source contradicts the claim, or if the source is about a different subject than the claim asserts.
3. CANNOT_CONCLUDE if the source is silent, partial, or ambiguous, or if the claim requires facts the source does not contain. Absence of support is not contradiction.
4. A source that merely mentions the claim's topic without establishing its assertion does not support it.
5. Numbers, dates and quantities in the claim must match the source exactly to AFFIRM.
6. Quote the shortest span that carries the finding. If no span carries it, SPAN is NONE.

## Permitted verdicts

`AFFIRM` · `DENY` · `CANNOT_CONCLUDE`. Abstention is first class: a panel that cannot conclude says so, and that recorded absence is itself evidence rather than a silent null.

## Content hash

The canonical form is the JSON object `{id, version, question, rules, verdicts}` with no whitespace. SHA-256:

`f26b7f104a5887dd19450ac7d2b1e547e3d2485152a43b08d1fc5658bf284745`

Recompute it from the canonical form below and compare. A finding that names a different hash was made under different rules.

```json
{"id":"ruleset-claim-support","version":"1.0.0","question":"Does the cited source support the claim as stated?","rules":["AFFIRM only if a verbatim span of the source establishes the claim as stated, without inference beyond ordinary reading.","DENY if the source contradicts the claim, or if the source is about a different subject than the claim asserts.","CANNOT_CONCLUDE if the source is silent, partial, or ambiguous, or if the claim requires facts the source does not contain. Absence of support is not contradiction.","A source that merely mentions the claim's topic without establishing its assertion does not support it.","Numbers, dates and quantities in the claim must match the source exactly to AFFIRM.","Quote the shortest span that carries the finding. If no span carries it, SPAN is NONE."],"verdicts":["AFFIRM","DENY","CANNOT_CONCLUDE"]}
```

## How a finding under these rules is produced

Each adjudicator is a directory row driven through this system's own gateway. No code was deployed to add them and adding another model is one more row. Every finding records the model, the rule set hash, the quoted span, the exposure (`independent` when the adjudicator saw no other finding, `concurring` when it did), the ordering seed, and a signature. A mandatory recorded adversary argues the strongest honest case against the majority and is published whether it prevails or not.

Adjudicator rows: https://miscsubjects.com/api/directory/ADJUDICATE_KIMI · https://miscsubjects.com/api/directory/ADJUDICATE_GROK · https://miscsubjects.com/api/directory/ADJUDICATE_GLM · https://miscsubjects.com/api/directory/ADJUDICATE_LLAMA · https://miscsubjects.com/api/directory/ADJUDICATE_MINIMAX · adversary: https://miscsubjects.com/api/directory/ADJUDICATE_ADVERSARY · error-rate probe: https://miscsubjects.com/api/directory/ADJUDICATE_PROBE

## What a finding under these rules does and does not establish

It establishes that named adjudicators, under these exact rules at this exact hash, returned these findings on this claim against this source, with their exposure and ordering recorded — at a measured error rate when a probe report is attached.

It does not establish that the claim is true. No adjudication anywhere does that. A court, a journal and a clinical endpoint committee each declare rules, take findings from named parties under those rules, and preserve dissent. This is that structure, with the rule set pinned at a hash instead of scattered through case law.