Frequently Asked Questions

Everything you need to know about navigating the curator economy, managing your sovereign namespaces, and earning equity.

How do I curate a Pipe?

Curating a Pipe involves discovering high-value, signal-dense information (like blog posts, whitepapers, datasets, or books) and feeding them to your namespace via the Active Workspace. Every URL you submit is crawled by Scout, evaluated for semantic alignment, and cryptographically hashed into your namespace's local SQLite database. The higher the alignment, the denser your pipe becomes.

What is the Bread Rule Equity?

The Bread Rule is a principle of fair compensation for curation. When an AI or user queries your pipe (e.g., pipe\flyfishing) and extracts insight, a micro-toll is extracted. If you own the pipe, you earn the equity. The Bread Rule guarantees that humans are compensated for the cognitive labor of curating the internet, preventing AI from scraping without payment.

Where is the data stored?

Pipes is storage-agnostic. Currently, nodes are securely hashed and stored in your local SQLite database using Drizzle ORM. This ensures that you own the 'hard drive' and maintain complete sovereignty over your data. Future iterations will support Nostr relays, IPFS, and BYOS (Bring Your Own Storage).

How does Scout score my injections?

Scout uses deep-tissue semantic matching powered by the Gemini AI SDK. When you inject a URL, Scout extracts the raw text and links, processes the cognitive patterns, and assigns an alignment score (0-100) based on how strictly the content adheres to your namespace's core philosophy. Only high-value matches are permanently committed.