Repository navigation
docs: front doors for node operators and publishers - #135
Merged
Merged
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The new guides misdescribe PaymentPool spending and origin import behavior, and contain invalid role paths.
5 open findings
What changed in this PR
Adds persona-based documentation front doors for node operators and publishers.
Changes:
- Documents cache-node and publisher workflows across deployment paths.
- Clarifies origin lifecycle, relay, discovery, and on-chain requirements.
- Updates repository navigation and contributor guidance.
| File | Description |
|---|---|
README.md |
Adds persona-based entry points. |
AGENTS.md |
Documents persona-specific deployment structure. |
docs/node-operators.md |
Adds the cache-node operator guide. |
docs/publishers.md |
Adds the publisher and origin guide. |
docs/requirements.md |
Applies requirements to cache and origin nodes. |
docs/lifecycle.md |
Documents origin decommissioning. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
thiras
force-pushed
the
feat/cloud-init-personas
branch
from
October 10, 2026 16:45
1818a58 to
799ba39
Compare
thiras
force-pushed
the
docs/persona-front-doors
branch
from
October 10, 2026 16:46
7bdcd3e to
0462622
Compare
thiras
force-pushed
the
feat/cloud-init-personas
branch
from
October 10, 2026 17:10
799ba39 to
c2c5729
Compare
thiras
force-pushed
the
docs/persona-front-doors
branch
from
October 10, 2026 17:10
0462622 to
e691397
Compare
thiras
force-pushed
the
feat/cloud-init-personas
branch
from
October 10, 2026 17:38
c2c5729 to
88accfa
Compare
thiras
force-pushed
the
docs/persona-front-doors
branch
from
October 10, 2026 17:38
e691397 to
5eca3d4
Compare
docs/node-operators.md and docs/publishers.md are the two entry points: what each kind of operator runs, on which deploy path and entry point, and the on-chain steps that are theirs, every protocol claim cited to an ADR. A node operator runs cache nodes, which pay for their misses from their own pool; a publisher runs origin nodes (served from their own backend, seated with `decdn publish assign`) and optionally sponsord, iroh relays and an iroh DNS server. The README opens on that split, AGENTS.md describes the persona entry points, and lifecycle.md says decommissioning an origin leaves it seated until the publisher revokes it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ore, and role links resolve Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
thiras
force-pushed
the
docs/persona-front-doors
branch
from
October 10, 2026 18:01
5eca3d4 to
5e064f5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
The last PR of the persona restructure. It is stacked on #134, and its text describes #131 (Compose
originprofile) and #132 (chart origin docs), so merge it after all of them.docs/node-operators.md. What a cache node is and the entry point on each deploy path. A miss is filled from other nodes and paid from the node's own pool (ADR 003). It also covers the on-chain stake and registration step (ADR 019) and the caveats of moving to self-hosted relays or discovery.docs/publishers.md.decdn publish namespace create/assign/revoke, anddecdn origin import.requirements.mdandlifecycle.mdgain the origin notes.A fact-check pass against the ADRs and the code corrected one claim. The
relay_foreign_namespacesgate depends on the node's backend, not on the namespace. That wording was also fixed in #133, #131 and #132.Test plan
make lint(markdownlint)make test-scriptsandmake lint-cloud-initon the full stack🤖 Generated with Claude Code