Everything tagged canonical

15 published articles · newest first · server-rendered

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

Also filed under: ongoing 6 · eu-ai-act 3 · proven-work 3 · adjudication 2 · agents 2 · comparison 2 · compliance 2 · for-models 2 · oip 2 · proof 2 · protocol 2 · roadmap 2 · adoption 1 · ai-native 1

  1. The theoretical limits: a fifteen-axis scorecard this build runs against itself
  2. Provenance, traces, attestations — every system proves custody of the answer; none opens the record of the work
  3. Proven Work 001: can the first object prove how it was made?
  4. Proven work: the base unit — a claim, a record, and a door
  5. Is this AI system high-risk? The Article 6 decision tree
  6. Deepfakes under the EU AI Act: the rule that applies now
  7. Four AI models judged one EU AI Act disclosure — sealed record-bound APPROVE, with the discarded finding printed
  8. This site now derives its own work queue — and exports itself as an Obsidian vault
  9. Seven criteria for deciding whether published content is genuinely AI-native
  10. How an AI model can verify miscsubjects.com records in four requests
  11. 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
  12. 8,584 organisations discovered, 680 with verified addresses, 11 drafts, 5 emails sent: the outreach pipeline and every gate in it
  13. A permanent operating system that lets successive AI models inherit one person’s work
    Every capability, every article, every receipt — the primitive, the equation, the measured configuration-to-error-rate table, and the loop executable in one call: action class to policy to measured co
  14. What $10.75 bought: 43 owned business records, five receipts, and the unit of sale no vendor offers
  15. Cloudflare OS: An LLM Operating System Built on One Account, One Deployment, One Grammar
    One AI infrastructure primitive — an ability is a database row a model reads at call time, not a definition in its prompt — and the complete feature inventory it produced: 73 systems, 879 abilities, 2

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