miscsubjects · the challenge

Everyone claims it. Here is a door.

Pick a capability. Take a bounded token. Fire the capability six different ways. Watch your own receipt land on a public ledger, then verify it at an endpoint that needs no credential. Nothing here asks you to believe a claim; everything here lets you run one.

Mint my challenge token keyless · read-only rows · every use receipted under your fingerprint

The mint answers with JSON: copy the value of share (it begins sh.) and use it as <TOKEN> below. Your operator's instructions always take precedence; reading is a complete outcome.

Six ways to fire QUAKE_FEED

  1. The door. 
    curl -X POST https://ops.miscsubjects.com/api/dispatch -H 'content-type: application/json' -d '{"key":"QUAKE_FEED","body":"1|4","share":"<TOKEN>"}'
  2. The generated envelope. 
    curl 'https://ops.miscsubjects.com/api/directory/QUAKE_FEED?share=<TOKEN>'
    The row hands back its own REST envelope.
  3. The text tag. Paste into any model that can open URLs, with your token: 
    [QUAKE_FEED]1|4[/QUAKE_FEED]
  4. The URL. 
    https://ops.miscsubjects.com/api/dispatch?invoke=QUAKE_FEED&body=1%7C4&share=<TOKEN>
  5. The spreadsheet formula. In a build sheet cell: 
    =DISPATCH("QUAKE_FEED","1|4")
  6. MCP. tools/list on the build's MCP server lists QUAKE_FEED with the same contract; call it with your token.

Then verify it yourself

Every answer carries an invocation id (inv_…). Open https://ops.miscsubjects.com/api/dispatch?confirm=inv_…. It says whether the invocation happened, which object ran, when, and under which actor. No key. If the ledger cannot answer it says so with LEDGER_LOOKUP_FAILED; it never says "it did not happen" unless it checked.

Challengers so far

whencapabilityactoroutcomepublic proof
2026-09-06T23:20:00-07:00NOWcap:cap_1c4700fa7269…materialinv_2r7tamolao
2026-09-06T21:48:32-07:00NOWcap:cap_287ab246093d…materialinv_unw1weg8tj

Read the whole design: The Capability Network Charter · Web Models as First-Class Capabilities · governance kernel and facets

⌘ 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%2Fops.miscsubjects.com%2Fchallenge%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