docs(taosnet): reconcile design doc with the shipped closed swarm - #1729
Conversation
…losed swarm The doc still described the original open-swarm design (opentracker on tinyagentos.com, a home seedbox, DHT bootstrap). taOSnet shipped closed and account-authenticated. Add a Current state section (passkey, private tracker on taos.my, VPS+GDrive seedbox, HF web-seed fallback, DHT off, license-eligibility gate) and point at the authoritative live contract in docs/taosnet.md. The original design is kept below for history.
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
📝 WalkthroughWalkthroughThis PR updates the design documentation file ChangesDocumentation update
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
|
||
| taOSnet is a closed, account-authenticated swarm on `taos.my`, not an open BitTorrent network. | ||
|
|
||
| - **Gate:** an authenticated taOS account (paid via taOSgo today). No account still works via the HTTP web-seed fallback. |
There was a problem hiding this comment.
WARNING: Contradictory/ambiguous Gate bullet — likely missing a question mark.
"No account still works via the HTTP web-seed fallback." reads as a negation: it implies that without an account, the HTTP web-seed fallback does not work. That directly contradicts the BEP-19 Web seed bullet below ("'no peers' degrades to today's HTTP download") and the "Remaining" bullet about a "clean HTTP fallback for unlinked controllers." If the intent is that unauthenticated users still get the HTTP fallback, the missing ? inverts the meaning — please rewrite as e.g. "No account? The HTTP web-seed fallback still works."
Minor follow-up: "paid via taOSgo today" will read as stale as soon as billing changes; consider dropping the time-relative word or tying it to a dated note.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/design/model-torrent-mesh.md`:
- Line 7: The status heading is future-dated, so update the “Current state”
heading in the design document to use the actual publish date or remove the date
entirely. Locate the heading text near the current-state section and adjust only
that identifier so it reflects the live state without implying an incorrect
future date.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 0b48ed06-1cd9-4c14-8fe7-3b0b2631ab89
📒 Files selected for processing (1)
docs/design/model-torrent-mesh.md
| the catalog resilient to mirror outages. | ||
| Peer-to-peer model distribution for taOS. Every instance that downloads a model becomes a seeder, taking load off the central mirror and making the catalog resilient to outages. | ||
|
|
||
| ## Current state (2026-07-08) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Avoid future-dating the status heading.
2026-07-08 is ahead of the current date, so this reads as incorrect until tomorrow. If the section is meant to describe the live state, use the actual publish date or remove the date from the heading.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/design/model-torrent-mesh.md` at line 7, The status heading is
future-dated, so update the “Current state” heading in the design document to
use the actual publish date or remove the date entirely. Locate the heading text
near the current-state section and adjust only that identifier so it reflects
the live state without implying an incorrect future date.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Reviewed by hy3-20260706:free · Input: 34K · Output: 5.4K · Cached: 124.5K |
docs-only. The model-torrent-mesh design doc still described the original open-swarm design (opentracker, home seedbox, tinyagentos.com). Adds a Current state (2026-07-08) section reflecting what shipped (closed account-authenticated swarm, passkey + private tracker on taos.my, VPS+GDrive seedbox, HF web-seed fallback, DHT off, license-eligibility gate) and what is built vs remaining, and points at the authoritative live server contract in docs/taosnet.md. Original design retained below for history.
Summary by CodeRabbit