Everything tagged oip-edge

18 published articles · newest first · server-rendered

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

Also filed under: objection-7 18 · oip 18 · kimi-import 15 · self-explaining 15 · voxel 15 · concepts 13 · machine-native-json 3 · object-invocation-protocol 3 · protocol-specification 3 · primer 2 · token-drops 2 · dynamic 1 · what-is-autopoiesis 1 · what-is-capability-security 1

  1. What is a token?
  2. What is an object?
  3. What Is a Voxel Graph
  4. What Is "The URL Is the API"
  5. What Is a Token Drop
  6. What Is Tap and Go Delegation
  7. What Is the Semantic Web
  8. What Is a Self-Describing Protocol
  9. What Is Replay and Repair
  10. What Is a Receipt
  11. What Is "The Receipt Is the Proof"
  12. What Is W3C PROV
  13. What Is a Merkle Tree
  14. What Is HATEOAS
  15. What Is a Capability Token
  16. What Is Capability-Based Security
  17. What Is Autopoiesis
  18. What is JSON

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%2Foip-edge%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