The HOP Optimisation Protocol

Specification

1. §0Introduction## The Economic Stance
2. §1The Five LawsThe HOP protocol is governed by five structural principles. Implementations that violate these principles are non-conformant.
3. §2Core TopologyHOP replaces centralised platform databases with sovereign, cryptographically verifiable chains.
4. §3Character BlocksThe protocol does not trade in "jobs" or flat "skill rows." The atomic unit of commerce and reputation is the Character Block.
5. §4The Skill CodeThis section specifies how character blocks compose into a worker's biography: the privacy-preserving property that makes the protocol non-extractive, the…
6. §5Agent ArchitectureHOP separates cognition from execution across five distinct agent classes. Each class has a different cognitive shape, runs at a different cadence, and…
7. §6Economic MechanicsThis section defines the protocol's economic primitives. The economics are not an implementation choice layered on top of HOP — they are the protocol.
8. §7Namespace & Trust HierarchyHOP uses a DNS-like namespace to manage cryptographic authority and prevent scam chains.
9. §8Implementation SubstrateThis section specifies the actual technical substrate on which HOP runs. The other sections describe what the protocol does conceptually; this section…
10. §9Applied Use CasesTo understand how Character Blocks, Agents, and Constraints interact to clear markets without platform extraction, review the following operational examples.
11. §10Foundations & LineageHOP is not new. It is a synthesis of governance, developmental, and economic patterns that have been independently rediscovered and refined across centuries.
12. §11Adoption PathThis section is a v0.2 lane — currently underspecified in v0.1. It deserves explicit attention because the right adoption path is non-obvious and the wrong one…
13. §12GlossaryThis glossary defines protocol-specific terms. Where an external concept is referenced (e.g. BBS+, Celestia), terms are linked to the relevant section.
14. §13Concerns LogThis file is the canonical record of unresolved problems, design tensions, and v0.2 lanes for the HOP protocol.
15. §14ReputationStatus: This section specifies the reputation architecture for v0.3 of the protocol.

Mythology

1. 01Bismarck and the Gradient Federationcounterfactual · 1834–1871
2. 02The Haudenosaunee Great Law of Peacehistorical · c. 1142–present
3. 03Hirschman — Exit, Voice, and Loyaltyhistorical · 1970
4. 04Vygotsky — The Zone of Proximal Developmenthistorical · 1934
5. 05Beane — The Skill Codehistorical · 2024
6. 06Jefferson — Tyranny Over the Mindhistorical · 1800
7. 07The Australian Superannuation Precedenthistorical · 1992–present

Materialisations

Operational use cases — present-tense problems and what HOP does to them.

1. 01Crystallised Labour, Paid Forever
2. 02Walking the Tree
3. 03Training Data with a Lineage
4. 04Connecting the Halves

Bees for Honey

The framework lineage from v1 (March 2026) through v6 (May 2026). Math versioned; scenarios in their own files.

1. v1v1 — Metaphor
2. v2v2 — Tidy
3. v3v3 — Mechanism
4. v4v4 — The Ci Axis
5. v5v5 — Scenarios Only
6. v6v6 — Ontology