Nets
Workflow graphs
Reusable structures that turn a broad goal into nodes, dependencies, gates, and outputs.
Package library
Bob Hub Library
The working package area for BoBNet: package search, reviewed uploads, console tokens, creator submissions, and install-ready Bob pieces.
The landing page explains the ecosystem. The Library is where the actual package workflow lives.
Updated direction
Bob Hub now follows the Net.
Early Bob Hub was framed as a broad package marketplace. The new direction is sharper: it supports BoBNet's integrated console model, where reusable pieces help build, route, validate, and publish complex AI work node by node.
What belongs here
Reusable parts for an integrated AI console.
Bob Hub is being shaped around the objects BoBNet actually uses to get real work done.
Nodes
Bounded capability
Small executable work units for research, code, files, validation, review, packaging, or approvals.
Adapters
AI/API routing
Assignments and adapters for models, APIs, local tools, validators, browser flows, and external services.
Archetypes
Project starters
Intake-driven packages that create reviewed net projects from operator answers and source material.
Interactive preview
How a Bob Hub piece fits into a BoBNet run.
The Hub exists to supply the reusable parts. BoBNet decides how those parts are used inside the Net.
Selected layer
Goal
The operator defines the useful outcome first: what should be made, checked, packaged, or explained.
Package library
Browse Bob pieces.
Published workflow packs, nets, nodes, archetypes, routing examples, and adapters appear here after review. Bob Console can read the same Cloudflare-backed API.
Security notice
Review before you install.
Bob Hub packages can contain instructions, templates, scripts, or workflows that affect your files, tools, credentials, local environment, or AI/API usage. Public packages go through owner review and automated screening before publication, but no review can guarantee safety. Treat every Bob node, net, archetype, adapter, or workflow pack like third-party code.
Loading Bob pieces
Checking the public package shelf.
Creator upload
Submit a Bob piece for review.
Logged-in creators can upload a `.zip`, `.bobpkg`, or `.json` package. New uploads are stored in R2 and stay in review until a moderator publishes them.
Package file ready
Source and version known
Capabilities declared
Submission form Open upload form Expand this only when the package is ready for owner review.
Console link
Connect Bob Console to Bob Hub.
Generate a device token so Bob Console can browse private submissions, upload packages, vote, report, and download through the same Worker API as the website.
Creator shelf
Your Bob submissions.
Logged-in creators can check whether their uploads are queued, in review, held for changes, approved, hidden, or published.
Log in to view submissions
Your uploaded packages appear here after you sign in.
Roadmap
Bob Hub build path.
The path is deliberately practical: explain the new direction, support reviewed packages, then grow into a real distribution layer for net-native AI work.
Now
Landing, white paper, and package shelf
Publish the BoBNet thesis, update the Hub language, and keep package discovery connected to the Worker API.
Next
Compatibility and routing metadata
Make net versions, node capabilities, model/API requirements, safety labels, and provenance easier to inspect.
Later
Community publishing with stronger review
Support trusted creators, ratings, reports, review queues, and install flows only after the safety model is ready.
BoBNet launch lane
Bob Hub is the ecosystem. BoBNet is the console.
The Hub stores and distributes the pieces. The console turns those pieces into net-routed execution.