You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Network Public: design-doc series — tracking #796–#801
A series of six design-doc PRs proposing how to evolve JAR towards what the underlying paper calls a Network Public: a substrate that is structurally prevented from being privately enclosed, including by its own future operators.
The series is purely documentation. No consensus changes, no Cargo / Lake changes, no roadmap reprioritisation — every concrete mechanism described here sits as services on top of the existing Refine-Accumulate model, or as RFC-grade thinking that may inform future work. Nothing here asks maintainers to deprioritise the P0 mainnet-readiness work tracked in #172.
Plus a norms layer (#800 inference shapes) that defines minimum service-author obligations for any inference service running on the substrate, so that base-layer neutrality doesn't quietly re-enclose users at the service tier.
Reading order
The PRs are designed to be read in this sequence. Each builds context the next assumes.
docs: JAR as a Network Public #796 — JAR as a Network Public(parent thesis; maps the four separations onto existing JAR primitives, names the gaps, completes the genesis.md → coinless.md → network-public.md arc)
docs: the patience tax — delayed-settlement escrow #799 — The patience tax(delayed-settlement escrow funding traversal-weighted attribution and the negation layer; connects Coinless JAR's revenue model to upstream contribution)
Roadmap Grey: mainnet-launch-ready node roadmap #172. Nothing in this series competes with P0 mainnet-readiness work. The deliverables are doc PRs intended to inform later phases.
Status
All six PRs are open as drafts so contributors can comment without time pressure. They will be marked ready for review once the conversation in this issue settles direction.
Network Public: design-doc series — tracking #796–#801
A series of six design-doc PRs proposing how to evolve JAR towards what the underlying paper calls a Network Public: a substrate that is structurally prevented from being privately enclosed, including by its own future operators.
The series is purely documentation. No consensus changes, no Cargo / Lake changes, no roadmap reprioritisation — every concrete mechanism described here sits as services on top of the existing Refine-Accumulate model, or as RFC-grade thinking that may inform future work. Nothing here asks maintainers to deprioritise the P0 mainnet-readiness work tracked in #172.
The source paper
PR #796 is a synthesis / repo-resident counterpart to that paper. The other five PRs each isolate one mechanism the paper proposes.
The four functional separations the paper introduces
Plus a norms layer (#800 inference shapes) that defines minimum service-author obligations for any inference service running on the substrate, so that base-layer neutrality doesn't quietly re-enclose users at the service tier.
Reading order
The PRs are designed to be read in this sequence. Each builds context the next assumes.
genesis.md → coinless.md → network-public.mdarc)Relationship to existing threads
Status
All six PRs are open as drafts so contributors can comment without time pressure. They will be marked ready for review once the conversation in this issue settles direction.
cc @sorpaas @olanod