Skip to content

Conversation

@Sipher
Copy link
Collaborator

@Sipher Sipher commented Jul 24, 2025

Summary by CodeRabbit

  • New Features

    • Added comprehensive documentation and a step-by-step guide for emission proposals, including how to create them and their governance process.
  • Documentation

    • Updated and reorganized links and navigation to move "Root Agents" content under "Goal Leaders."
    • Added new entries for "Emission Proposals" in relevant documentation sections.
    • Improved clarity, fixed typos, and corrected step sequences in various guides.
    • Enhanced explanations and guidance for onboarding and key concepts.

@coderabbitai
Copy link

coderabbitai bot commented Jul 24, 2025

Walkthrough

This update reorganizes documentation navigation and content by moving "Root Agents" materials under the "Goal Leaders" category, updating internal links accordingly, and introducing new documentation pages and guides for "Emission Proposals." Several minor textual and typographical corrections are also included throughout the documentation.

Changes

File(s) Change Summary
astro.config.mjs Updated sidebar navigation: moved "Root Agents" entries to "goal-leaders" and added emission proposal links.
src/content/docs/explanations/builders/agent-editing.mdx
src/content/docs/explanations/builders/agent-registration.mdx
src/content/docs/explanations/builders/demand-signaling.mdx
src/content/docs/explanations/goal-leaders/root-agents.mdx
src/content/docs/how-to-guides/builders/create-signal.mdx
src/content/docs/how-to-guides/builders/register-an-agent.mdx
src/content/docs/how-to-guides/goal-leaders/become-a-root-agent.mdx
src/content/docs/web-apps (deprecated)/torus-portal.mdx
Updated internal documentation links from "root-agents" to "goal-leaders" paths.
src/content/docs/explanations/goal-leaders/emission-proposals.mdx Added new explanation page for "Emission Proposals."
src/content/docs/explanations/start-here.mdx Updated "Root Agents" link to "goal-leaders" and added "Emission Proposals" entry.
src/content/docs/getting-started/concepts.mdx Minor grammar and typo corrections.
src/content/docs/getting-started/tokenomics.mdx Fixed typo in image alt text.
src/content/docs/how-to-guides/goal-leaders/create-emission-proposal.mdx Added new how-to guide for creating emission proposals.
src/content/docs/how-to-guides/holders/setup-a-wallet.mdx Corrected step numbering and fixed a markup attribute typo.
src/content/docs/how-to-guides/start-here.mdx Updated "Become a Root Agent" link and added "Create Emission Proposal" guide link.
src/content/docs/index.mdx Updated "Swarm Leaders" link, improved section titles and instructions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DocsSidebar
    participant EmissionProposalGuide
    participant GoalLeadersDocs

    User->>DocsSidebar: Navigates sidebar
    DocsSidebar-->>User: Shows "Goal Leaders" with "Root Agents" and "Emission Proposals"
    User->>GoalLeadersDocs: Clicks "Root Agents"
    GoalLeadersDocs-->>User: Displays Root Agents documentation
    User->>EmissionProposalGuide: Clicks "Emission Proposals"
    EmissionProposalGuide-->>User: Displays Emission Proposals explanation/guide
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • renlabs-dev/torus-docs#20: Also restructures the sidebar and renames "Leaders" to "Goal Leaders," related to navigation and documentation organization.

Poem

🐇
In the warren of docs, we hop and we leap,
Root Agents now Goal Leaders, their secrets we keep.
Emission proposals sprout, new knowledge to sow,
With links all refreshed, and guidance in tow.
A tidy new burrow, for readers to know!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch dev

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@Sipher Sipher merged commit be8950b into main Jul 24, 2025
3 of 4 checks passed
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

♻️ Duplicate comments (1)
src/content/docs/how-to-guides/builders/register-an-agent.mdx (1)

133-134: Duplicate link update – same verification applies

Same slug change as above; once you verify line 34, this anchor will be covered as well.

🧹 Nitpick comments (11)
src/content/docs/getting-started/tokenomics.mdx (1)

13-13: Consider a more descriptive alt text for improved accessibility

Nice catch on the typo. However, the alt text is still fairly generic and doesn’t help screen-reader users understand what the graph conveys. A short summary of the graph’s message would be more useful.

-<Image src={graph} alt="Tokenomics Graph" width="1080" />
+<Image src={graph} alt="Graph showing TORUS token emission schedule" width="1080" />
src/content/docs/how-to-guides/holders/setup-a-wallet.mdx (1)

50-54: Consider switching to automatic list numbering inside <Steps>

Manually maintaining the numeric prefix (1., 2., …) is error-prone—this PR already had to correct one such mismatch.
With Markdown ordered lists the actual digit is ignored; you can safely use 1. for every item and let the renderer handle sequencing:

-2.  **Activate/Pin the Extension**
+1.  **Activate/Pin the Extension**

This eliminates future renumbering mistakes and keeps diffs smaller.

src/content/docs/explanations/goal-leaders/root-agents.mdx (1)

37-39: Link target looks correct – consider switching to a relative path.

The new URL correctly reflects the file-system move to goal-leaders, so 👍.
For long-term maintainability you may want to drop the absolute host and use a relative path, e.g.

-Follow our [step-by-step application guide](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/) …
+Follow our [step-by-step application guide](/how-to-guides/goal-leaders/become-a-root-agent/) …

This prevents hard-coding the production domain and avoids future migrations.

src/content/docs/how-to-guides/builders/create-signal.mdx (1)

32-36: Updated prerequisite links are valid.

Both links resolve to the new locations; nice catch keeping prerequisites up-to-date.
Consider relative paths for portability, but otherwise LGTM.

src/content/docs/getting-started/concepts.mdx (2)

15-16: Minor wording tweak

The sentence is correct but a bit verbose. Consider a lighter construction:

-Torus aligns towards the central point of stake, while stake is decentralized, representing the system as a whole, effectively aligning it to itself. 
+Torus continually aligns to the decentralized stake root, effectively keeping the system aligned with itself.

22-23: Typo: “granularily” → “granularly”

-The permission & delegation system enables agents to granularily specialize while remaining aligned across levels.
+The permission & delegation system enables agents to granularly specialize while remaining aligned across levels.
src/content/docs/index.mdx (1)

43-45: Reference label likely incorrect – “How it works” doesn’t exist

The call-out now says:

skip ahead to How it works

but no page/section with that title exists; the logical destination is still Get stuff done. Suggest reverting the wording or creating a matching heading.

- skip ahead to <RedText variant="light">How it works</RedText>
+ skip ahead to <RedText variant="light">Get stuff done</RedText>
src/content/docs/explanations/goal-leaders/emission-proposals.mdx (1)

56-58: Consider using relative imports for internal links

Hard-coding https://docs.torus.network/... reduces portability for staging environments. Relative paths (/how-to-guides/...) keep links working in branch previews.

src/content/docs/how-to-guides/goal-leaders/create-emission-proposal.mdx (3)

50-58: Mismatch with explanation terminology

Here the section is labelled Reward Distribution while the explanation page uses Incentive Distribution. Aligning wording avoids user confusion.


86-88: Grammar tweak: “proposal get denied”

Singular subject needs singular verb.

- ≤ 50 % support & > 10 % participation: proposal get denied.   
+ ≤ 50 % support & > 10 % participation: proposal gets denied.   

6-12: Unused import: LinkCard

LinkCard is imported but never used in this file. Removing it avoids dead code warnings during build.

-import {
-  Steps,
-  Aside,
-  CardGrid,
-  Card,
-  LinkCard
-} from "@astrojs/starlight/components";
+import {
+  Steps,
+  Aside,
+  CardGrid,
+  Card
+} from "@astrojs/starlight/components";
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8e9c748 and 0324b3b.

📒 Files selected for processing (17)
  • astro.config.mjs (2 hunks)
  • src/content/docs/explanations/builders/agent-editing.mdx (1 hunks)
  • src/content/docs/explanations/builders/agent-registration.mdx (1 hunks)
  • src/content/docs/explanations/builders/demand-signaling.mdx (1 hunks)
  • src/content/docs/explanations/goal-leaders/emission-proposals.mdx (1 hunks)
  • src/content/docs/explanations/goal-leaders/root-agents.mdx (1 hunks)
  • src/content/docs/explanations/start-here.mdx (1 hunks)
  • src/content/docs/getting-started/concepts.mdx (1 hunks)
  • src/content/docs/getting-started/tokenomics.mdx (1 hunks)
  • src/content/docs/how-to-guides/builders/create-signal.mdx (1 hunks)
  • src/content/docs/how-to-guides/builders/register-an-agent.mdx (3 hunks)
  • src/content/docs/how-to-guides/goal-leaders/become-a-root-agent.mdx (1 hunks)
  • src/content/docs/how-to-guides/goal-leaders/create-emission-proposal.mdx (1 hunks)
  • src/content/docs/how-to-guides/holders/setup-a-wallet.mdx (2 hunks)
  • src/content/docs/how-to-guides/start-here.mdx (1 hunks)
  • src/content/docs/index.mdx (2 hunks)
  • src/content/docs/web-apps (deprecated)/torus-portal.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/getting-started/concepts.mdx

[grammar] ~21-~21: Ensure spelling is correct
Context: ...n & delegation system enables agents to granularily specialize while remaining aligned acro...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

src/content/docs/explanations/goal-leaders/emission-proposals.mdx

[grammar] ~16-~16: Ensure spelling is correct
Context: ... rate and distribution across different coponents of the protocol. These proposals allow...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (11)
src/content/docs/how-to-guides/holders/setup-a-wallet.mdx (1)

125-127: Attribute typo fixed—LGTM

<RedText variant="light"> now uses the correct variant prop. Component API is respected and no further action is needed.

src/content/docs/web-apps (deprecated)/torus-portal.mdx (1)

46-49: URL update looks good.

Path now matches the relocated how-to guide. No action needed.

src/content/docs/how-to-guides/start-here.mdx (1)

53-55: Confirm new guides are live before publishing

The two new links rely on freshly-added pages (become-a-root-agent, create-emission-proposal). If these pages don’t reach production at the same time, users will hit dead links.

Run a quick link check or delay merging until the target pages are deployed.

src/content/docs/explanations/builders/agent-registration.mdx (1)

47-48: Link update looks correct

URL now matches the new documentation hierarchy. No further action needed.

src/content/docs/getting-started/concepts.mdx (1)

27-28: Good catch on “implementation” typo

The correction is accurate. 👍

src/content/docs/explanations/start-here.mdx (1)

48-49: Navigation update looks consistent

Links match the new goal-leaders structure and the added Emission Proposals doc.
No issues spotted.

src/content/docs/how-to-guides/builders/register-an-agent.mdx (2)

34-35: Validate the moved link actually resolves

The slug was switched from root-agents to goal-leaders, but the referenced page was also physically relocated in this PR. Please click-test the built docs (or run astro dev) to ensure the canonical URL how-to-guides/goal-leaders/become-a-root-agent/ renders and isn’t a 404.


119-121: Numbering is now correct – good catch
The previous off-by-one was fixed by renumbering to “7.” which aligns with the six prior steps.

src/content/docs/index.mdx (1)

17-18: Link path update looks fine

Target path now matches the new directory structure. 👍

astro.config.mjs (2)

66-68: Sidebar entry added without issues

Paths and nesting are consistent with the new folder hierarchy.


103-105: Good visibility for the new guide

Adding Create Emission Proposal here ensures quick access; no further action required.

Comment on lines 36 to 39
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Initial agent creation and ownership establishment
- **[Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/)** - How agents coordinate through signals
- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Special considerations for DAO-approved agents
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Special considerations for DAO-approved agents

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Broken URL – duplicate goal-leaders segment.

https://docs.torus.network/explanations/goal-leaders/goal-leaders/ will 404.
The page lives at /explanations/goal-leaders/root-agents/.

-**[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)**
+**[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)**

Please adjust (and ideally use a leading-slash relative URL).

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Initial agent creation and ownership establishment
- **[Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/)** - How agents coordinate through signals
- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Special considerations for DAO-approved agents
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Special considerations for DAO-approved agents
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Initial agent creation and ownership establishment
- **[Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/)** - How agents coordinate through signals
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Special considerations for DAO-approved agents
🤖 Prompt for AI Agents
In src/content/docs/explanations/builders/agent-editing.mdx around lines 36 to
39, the URL for "Root Agents" contains a duplicated segment causing a 404 error.
Replace the incorrect URL with the correct path
"/explanations/goal-leaders/root-agents/" using a leading slash to make it a
relative URL.

Comment on lines 35 to 37
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become discoverable
- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Agents with direct emission access
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Agents with direct emission access
- **[Agent Server Setup](https://docs.torus.network/explanations/builders/agent-server/)** - Recommended endpoint interface examples
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Broken link: path points to a non-existent goal-leaders/goal-leaders page

All other files moved the Root Agent docs to goal-leaders/root-agents/, but this bullet links to goal-leaders/goal-leaders/, which 404s.

-**[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Agents with direct emission access
+**[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents with direct emission access
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become discoverable
- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Agents with direct emission access
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Agents with direct emission access
- **[Agent Server Setup](https://docs.torus.network/explanations/builders/agent-server/)** - Recommended endpoint interface examples
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become discoverable
- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents with direct emission access
- **[Agent Server Setup](https://docs.torus.network/explanations/builders/agent-server/)** - Recommended endpoint interface examples
🤖 Prompt for AI Agents
In src/content/docs/explanations/builders/demand-signaling.mdx around lines 35
to 37, the link for "Root Agents" incorrectly points to a non-existent path
goal-leaders/goal-leaders/. Update this link to the correct path
goal-leaders/root-agents/ to fix the broken link and prevent 404 errors.

Comment on lines +16 to +17
Emission proposals can adapt the token emission rate and distribution across different coponents of the protocol.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Spelling error: “coponents” → “components”

Minor typo in the first paragraph.

-Emission proposals can adapt the token emission rate and distribution across different coponents of the protocol.
+Emission proposals can adapt the token emission rate and distribution across different components of the protocol.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Emission proposals can adapt the token emission rate and distribution across different coponents of the protocol.
Emission proposals can adapt the token emission rate and distribution across different components of the protocol.
🧰 Tools
🪛 LanguageTool

[grammar] ~16-~16: Ensure spelling is correct
Context: ... rate and distribution across different coponents of the protocol. These proposals allow...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents
In src/content/docs/explanations/goal-leaders/emission-proposals.mdx around
lines 16 to 17, fix the spelling error by changing "coponents" to "components"
in the sentence describing emission proposals adapting the token emission rate
and distribution.

Comment on lines 108 to 110
- **Join the community**: Be active in [Discord](https://discord.gg/torus) to share updates about your agent.
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/root-agents/root-agents/) approval criteria and DAO governance
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/goal-leaders/) approval criteria and DAO governance
- **Check application status**: Monitor [DAO whitelist applications](https://dao.torus.network/whitelist-applications) for voting progress
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Incorrect reference to Root Agent explanation page.

Same duplication as above – link should point to /explanations/goal-leaders/root-agents/.

-Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/goal-leaders/) approval criteria …
+Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/root-agents/) approval criteria …

Fix to avoid a broken “What’s Next?” link.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **Join the community**: Be active in [Discord](https://discord.gg/torus) to share updates about your agent.
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/root-agents/root-agents/) approval criteria and DAO governance
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/goal-leaders/) approval criteria and DAO governance
- **Check application status**: Monitor [DAO whitelist applications](https://dao.torus.network/whitelist-applications) for voting progress
- **Join the community**: Be active in [Discord](https://discord.gg/torus) to share updates about your agent.
- **Understand the process**: Learn about [Root Agent](https://docs.torus.network/explanations/goal-leaders/root-agents/) approval criteria and DAO governance
- **Check application status**: Monitor [DAO whitelist applications](https://dao.torus.network/whitelist-applications) for voting progress
🤖 Prompt for AI Agents
In src/content/docs/how-to-guides/goal-leaders/become-a-root-agent.mdx around
lines 108 to 110, the link for "Root Agent" explanation incorrectly points to
/explanations/goal-leaders/goal-leaders/. Update this URL to
/explanations/goal-leaders/root-agents/ to fix the broken "What's Next?" link
and ensure it directs to the correct explanation page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants