Everything tagged voxel

61 published articles · newest first · server-rendered

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

Also filed under: kimi-import 61 · oip 61 · self-explaining 61 · thinkers 33 · concepts 20 · objection-7 15 · oip-edge 15 · token-drops 4 · lineages 3 · hierarchy 1 · hub 1 · model-reads-token-drop 1 · oip-from-capability-security 1 · oip-from-rest 1

  1. What Is a Voxel Graph
  2. What Is "The URL Is the API"
  3. What Is a Token Drop
  4. What Is Tap and Go Delegation
  5. What Is the Semantic Web
  6. What Is a Self-Describing Protocol
  7. What Is Replay and Repair
  8. What Is a Receipt
  9. What Is "The Receipt Is the Proof"
  10. What Is W3C PROV
  11. What Is Model-Operated Work
  12. What Is the Missing Reader Problem
  13. What Is a Merkle Tree
  14. What Is the History of Link Protocols
  15. What Is HATEOAS
  16. What Is a Falsification Surface
  17. What Is a Convergence Catalogue
  18. What Is Context as Cursor
  19. What Is a Confused Deputy
  20. What Is a Capability Token
  21. What Is Capability-Based Security
  22. What Is Autopoiesis
  23. How to Write a Token Drop That Models Accept
  24. Vannevar Bush — The Memex and the Trail of Thought
  25. Tim Berners-Lee — The Universal Link and the Semantic Web
  26. Ted Nelson — Xanadu and the Dream of Connected Documents
  27. Satoshi Nakamoto — Bitcoin and the Append-Only Ledger
  28. Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems
  29. Roy Fielding — The Man Who Named How the Web Works
  30. Robin Milner — Types, Processes, and the Pi Calculus
  31. Ramon Llull — The First Machine for Reasoning
  32. Pat Helland — Life Beyond Distributed Transactions
  33. Norman Hardy — KeyKOS and the Persistent Capability Operating System
  34. Niklas Luhmann — Social Systems and Communication
  35. Markus Lanthaler — Hydra and Machine-Readable Web Operations
  36. Mark Miller — Capability Security and the E Language
  37. Marc Stiegler — Petnames and Introduction Patterns
  38. Leslie Lamport — Time, Clocks, and the Ordering of Events
  39. Juan Benet — IPFS and Content-Addressed Storage
  40. James Gibson — Affordances and the Theory of Perception
  41. Jack Dennis — The Forgotten Origin of Capabilities
  42. Heinz von Foerster — Second-Order Cybernetics
  43. Gottfried Wilhelm Leibniz — The Universal Characteristic
  44. Gilbert Simondon — Technical Objects and Individuation
  45. Eric Brewer — The CAP Theorem
  46. Doug Engelbart — Augmenting Human Intellect
  47. Charles Sanders Peirce — Signs, Abduction, and Pragmatism
  48. Carl Hewitt — The Actor Model
  49. Butler Lampson — Protection and Access Control
  50. Bram Cohen — BitTorrent and Content-Addressed Protocol Design
  51. Barbara Liskov — Abstract Data Types and Distributed Consensus
  52. J.L. Austin and John Searle — Speech Acts
  53. Alan Kay — The Big Idea Is Messaging
  54. What OIP Should Take from the Semantic Web
  55. What OIP Should Take from REST
  56. What OIP Should Take from Capability Security
  57. How a Model Should Read an OIP Token Drop
  58. OIP Thinker Reference
  59. Gregory Bateson — Information as Difference
  60. Alfred North Whitehead — Process and Reality
  61. Gilles Deleuze — The Rhizome and Multiplicity

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