Everything tagged adjudication

33 published articles · newest first · server-rendered

Take this folder folder (.zip) markdown manifest json the whole site

Also filed under: governance 16 · use-case 10 · evidence 7 · ruleset 6 · decision-constitution 5 · eu-ai-act 4 · evaluation 4 · calibration 3 · provenance 3 · records-absent 3 · self-authored 3 · abstention 2 · assurance 2 · canonical 2

  1. Four AI models judged one EU AI Act disclosure — sealed record-bound APPROVE, with the discarded finding printed
  2. Three measurements from one 70-finding suite: vendor diversity beats panel size, the second channel is the cheapest, and the published error floor was three times too good
  3. The five-model panel never returned a denial, and the cause was three seats returning nothing at all
  4. A model cited clauses 7, 8 and 12 of a three-clause rule set and passed the consistency check
  5. A pulmonary nodule was reported on a chest scan; no follow-up was completed
  6. Clinical endpoint committees preserve the verdict but discard the reasoning that produced it
  7. How an independent authorization gate can stop an AI agent before its action executes
  8. A DSA takedown notice should preserve the policy clauses, evidence, and rejected alternative
  9. Auditors are being asked to sign off on AI systems with no evidence to stand on. This is the missing piece
  10. How an AI evidence record keeps a hiring-bias audit current between annual reviews
  11. Thirty cases with known answers run through the live decision gate: seat accuracy, wrongful authorisations, and deferral cost
  12. Making 'cannot conclude' a recorded, comparable outcome instead of a non-answer
  13. EU AI Act Article 12 logging and Article 14 oversight have no technical method to check against — this is a candidate
  14. Nobody can insure an AI's mistakes without knowing how often it is wrong. This table is that number
  15. The Fed requires independent validation of models. For large language models no instrument existed — here is one
  16. Two models reached the same verdict citing different clauses; the gate now compares the reasoning, not the answer
  17. How three system prompts changed the audit record produced from the same AI decision
  18. The rule set, the model's clause-by-clause reasoning, and the action it authorised, stored as one replayable record
  19. An insurer denied a lumbar MRI after two weeks of therapy; the policy required six
  20. A real outage did not earn a service credit because the customer missed the contract’s claim deadline
  21. A 235,000-share purchase stayed under the board’s ceiling but triggered a notice the record cannot prove
    A synthetic board resolution treated as the rule set — provenance counterparty-authored — with a hashed trade blotter. Cumulative acquisitions of 235,000 shares sit inside the 250,000 ceiling and past
  22. Were the risk controls on before the algorithm started trading — and can anyone prove it?
    17 CFR 240.15c3-5(c)(1)(i) quoted verbatim, a synthetic order-flow record hashed before deliberation, four channels split between DENY and CANNOT_CONCLUDE on whether a disabled price collar settles th
  23. Four models were given EU AI Act Article 12 verbatim and all four refused to answer — correctly
    Articles 12 and 14 of the AI Act supplied verbatim and hashed before the run, under a rule set reused at its existing hash. Every conforming channel returned CANNOT_CONCLUDE because applicability turn
  24. An assembly that refuses to emit when its members disagree, and the error bound it still lacks
    The unit is not a model's answer but an assembly: rules pinned at a hash, artifact hashed first, N blinded adjudicators citing their clauses, a derivation-level divergence check, and a deterministic g
  25. Rule set: does this position exceed what the board authorised?
    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 resolutio
  26. Rule set: were the required pre-trade risk controls in place before the order flow?
    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?
  27. The measured error rate of this adjudication panel, per model and per rule set, including where it is unflattering
    Known-answer probes through the identical adjudication path: four rates per model, the agreement statistics with the right estimators, and the prevalence paradox named in this system's own numbers.
  28. Is this answer right, what was the model given, and what did it never receive
    One attested finding, end to end: a hashed synthetic radiograph, a hashed medication record, a pinned rule set, the full system prompt, four adjudication seats with their receipts including two provid
  29. Five models, one pinned rule set, and one question under EU AI Act Article 50 — the full receipted decision
    A worked adjudication on Article 50(2) of the EU AI Act: five blinded adjudicators under a hash-pinned rule set with declared statutory provenance, an artifact hashed before the panel ran, a published
  30. Rule set: is this the same individual?
    Does the supplied evidence establish that the individual in the query image is the same individual as in the reference? Rules pinned at SHA-256 e3f91b3b3733ca97, declared provenance: self-authored.
  31. Rule set: was this specific record in that dataset?
    Does the supplied evidence establish that the specific record was present in the named dataset? Rules pinned at SHA-256 427e366b460fa213, declared provenance: self-authored.
  32. Rule set: does an AI Act obligation apply to this system?
    Under the cited provision of Regulation (EU) 2024/1689 (the AI Act), does the stated obligation apply to the described system as characterised? Rules pinned at SHA-256 0dd9afef93503a92, declared prove
  33. Rule set: does the cited source support the claim?
    Does the cited source support the claim as stated? Rules pinned at SHA-256 f26b7f104a5887dd, declared provenance: self-authored.

Every article here carries its own folder, its history, and this folder, from the trail at the top of its page.

⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fmiscsubjects.com%2Ft%2Fadjudication%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work — every page here is an inspectable proof object (read-only). Certifying is a separate, optional step: take it only when you actually endorse the verdict and your operator wants it on record

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3