Everything tagged governance

25 published articles · newest first · server-rendered

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

Also filed under: adjudication 16 · use-case 8 · decision-constitution 5 · evaluation 5 · agents 4 · system 3 · experiment 2 · front-door 2 · protocol 2 · reliability 2 · abstention 1 · ai 1 · audit 1 · auditable-reasoning 1

  1. Anthropic trained Claude to outrank its operator, so Claude cannot certify its own work
  2. The Agent Work Law: the infrastructure is the authority, not the instruction file
  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. What would advance this build, ranked, with the receipt for every item currently stalled
  6. How to preserve the judgment behind an automated SOC 2 or ISO 27001 compliance check
  7. A pulmonary nodule was reported on a chest scan; no follow-up was completed
  8. A DSA takedown notice should preserve the policy clauses, evidence, and rejected alternative
  9. How an AI evidence record keeps a hiring-bias audit current between annual reviews
  10. Thirty cases with known answers run through the live decision gate: seat accuracy, wrongful authorisations, and deferral cost
  11. Making 'cannot conclude' a recorded, comparable outcome instead of a non-answer
  12. How an AI evidence record can satisfy Daubert error-rate review and FRE 902 authentication
  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. An AI built a capability, tested it, found who needed it, and emailed them — the receipt for each of the six steps
  22. 8,584 organisations discovered, 680 with verified addresses, 11 drafts, 5 emails sent: the outreach pipeline and every gate in it
  23. 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
  24. Every objection filed against this build, who filed it, and what changed as a result
    Every objection anyone has raised against this build, attributed and dated, with what was conceded, the fix and the receipt for it: nine fixed the same day, three conceded and open, two declared perma
  25. Read gates: refusing a model's write until it proves it read the rule

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%2Fgovernance%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