DSPY GROUP / RELAY / PROJECT 01 Interactive concept demo

Build the network that helps build the companies.

DSPY Relay turns shared objectives into scoped tasks, coordinates independently authorized AI tools and human participants, verifies the results, and records who helped.

The group chat decides what matters. Relay opens approved work to a broader contributor network.

Request collective access

Anyone can request access, and a person reviews every request. A request does not guarantee approval. Personal AI subscriptions stay participant-controlled and human-mediated.

CONTROL PLANE ONE
OBJECTIVE Shared task graph

Worker 04API · VPS

Participant 11Manual tool · laptop

Worker 18Local · desktop

Worker 07Manual · review

Worker 15API · VPS

Worker 02Cloud · runner

20 illustrative buildersIndependent authorizationOne network

First, build the machine. Then, build the companies. See how the network works

ALIGNChoose an objective in the group chat

OPENOffer scoped work to approved participants

VERIFYReview the outcome and preserve the evidence

01 / THE SHIFT

AI can produce work faster than teams can coordinate it.

Code generation is no longer the only bottleneck. The hard part is deciding what happens next, routing it safely, reviewing it, and keeping the whole effort coherent.

DSPY RELAY Shared objective Task graph · policies · review · evidence

Capacity exists. Coordination is fragmented. Separate prompts, branches, machines, and review loops limit compounding.

02 / RELAY IN MOTION

One objective becomes a coordinated system of work.

Watch an approved task graph unlock in dependency order, route work to compatible workers, ask for human judgment, and create follow-up work when review finds a problem.

FUTURE-MODE SIMULATION · DETERMINISTIC DEMO DATA

RELAY / EVENT STREAM 00:00:00

CURRENT OBJECTIVE Ship the first DSPY company-launch workspace

Awaiting simulation

Start the objective to see Relay coordinate the work.

SELECTED TASKQueued

REL-201 · Define product scope

Runs on: Unassigned
Authorization: Manual review
Access: Repository read
Budget: 18 min remaining

THE SYSTEM UNDERNEATH

Coordination without surrendering control.

01Plan

People approve the objective and dependency-aware work graph.

02Route

Relay matches eligible work to available capabilities and policy.

03Execute

In the planned system, workers run scoped, signed jobs in isolated environments.

04Prove

Tests, reviews, commits, approvals, and accepted PRs form the evidence.

03 / PARTICIPATE

Bring the AI capacity you already control.

Relay is designed to meet participants where they are: using a personal AI tool themselves, contributing judgment, or operating independently authorized API, cloud, local, or workspace capacity.

PERSONAL AI TOOLS / HUMAN-INITIATED

Already use a $20 or $200 personal plan?

Claim a scoped task, run it yourself with a tool from the approved AI tools list, and return the branch, artifact, and evidence for review.

Your account and login remain yours.
Relay does not pool or resell allowances.
A higher plan does not grant Relay automated access.

AUTHORIZED WORKERS / PLANNED

Operate approved infrastructure?

API credentials, cloud IAM, local models, owned infrastructure, and approved workspaces can support autonomous workers when the provider and organization permit it.

Provider credentials stay on the worker.
Every command is signed, scoped, expiring, and auditable.
Network access and budget remain bounded.

01Request access

Tell DSPY GROUP who you are and complete the current review flow.

02Choose your mode

Contribute judgment, manual work, or separately authorized capacity.

03Claim scoped work

Choose an approved task that fits your skills, tools, and authorization.

04Submit evidence

Return the result for tests, review, and an explicit acceptance decision.

Your subscription is not the product. Your judgment, independently authorized capacity, and accepted contribution are what matter.

04 / THE WORKER NETWORK

Opt in a scoped worker. Or claim work manually.

A worker can live on a laptop, VPS, or group runner. It connects outbound, keeps provider authorization local, and accepts only work inside its approved scope.

DSPY / HYPOTHETICAL FLEET6 / 20 online

READY WORK

REL-231Accessibility passrequires: browser · review

REL-232Protocol testsrequires: node · mock

REL-233Security reviewrequires: manual approval

Preview the planned worker setup

FUTURE ONBOARDING EXPERIENCE

Two example commands. Then guided setup.

The intended experience feels more like pairing a new device than administering infrastructure. Planned flow only; do not run these commands.

relay-worker / setupPAIRING CODE EXPIRES 09:42

# ILLUSTRATIVE — DO NOT RUN

$ curl -fsSL https://example.invalid/dspy-worker-install | sudo bash

✓ Example installer output would appear here

$ sudo dspy-worker pair RLY7-K9Q2

Device fingerprint: 7A:91:DF:02:4C

?Confirm this fingerprint in Relaywaiting…

Design target: no inbound portsDesign target: credentials stay on worker

Explore the capacity assumptions

ILLUSTRATIVE CAPACITY MODEL

Capacity means schedulable work, not subscription value.

Each contributor runs their own workers under their own authorization. Scale the collective and the schedulable agent-hours scale with it. This illustrative model does not represent tokens, credits, savings, or guaranteed output. Personal plan allowances are not pooled, transferred, resold, or treated as group credit.

Contributors 24 Approved participants bringing their own authorized capacity. Workers per contributor 3 72 workers online across the collective. Share of personal limits contributed 40%

SCHEDULABLE AGENT-HOURS / WEEK3,144h449h per day · 18.7h per contributor per day

WORKERS ONLINE72

MODELED CONCURRENT LANES15–25

ASSUMPTIONS

A contributed worker is schedulable for its contributed share of a 24-hour day, then stops at its own account’s ceiling.
65% scheduling efficiency — the rest is lost to dependency waits, review queues, and retries.
Nothing is pooled: every hour is spent under the authorization of the contributor who supplied it.

Illustrative planning assumptions only. Assumes compatible tasks, documented authorization, and available review. Real availability depends on current provider terms, account configuration, and organization approval.

05 / THE CONTROL ROOM

Make the whole organization legible.

An operator should always know what is happening, where it runs, whose authorization is in use, what it can access, what budget remains, and what needs approval.

SIMULATED PRODUCT PREVIEW · NOT A LIVE FLEET

DEMO STATUSReady for an interaction.Actions update this preview only. No worker or external service is contacted.

06 / HUMAN + AI ORGANIZATION

Humans move upward in the stack.

Relay does not remove human judgment. It is intended to reduce coordination overhead so participants can spend more time choosing objectives, resolving ambiguity, reviewing results, and deciding what deserves to ship.

HUMAN JUDGMENT LANE

01Choose the objectiveWhat is worth building now?

02Resolve ambiguityWhich tradeoff serves the product?

03Approve consequenceMay scope, access, or budget expand?

04Accept the outcomeDoes the evidence prove it is ready?

CT-3.3 ACCEPTANCE EVENT / EVIDENCE TRAILPR #018

ILLUSTRATIVE INITIATIVEShip the Relay worker-pairing flowProposed by Participant A · simulated scenario

PATask authorParticipant A refined scope

PBWorker sponsorParticipant B supplied runner

RAAgent runRUN-248 produced PR

PCReviewerParticipant C requested changes

ARAuthorized Company actorAcceptance Event recorded

42 checks passed3 artifacts8 accepted commitsAudit event #9271

Evidence, not a scoreboard. Attribution records document participation and accepted work. They are not points, compensation, equity, vesting, or an entitlement to an award.

07 / FROM CONVERSATION TO COMPANY

The group chat starts the decision. Relay opens the work.

Ideas and judgment begin in conversation. Relay turns an approved objective into auditable work that a broader network of builders, reviewers, operators, and worker sponsors can help complete.

01Group chat

Needs, ideas, and expertise surface.

02Approved objective

A chosen outcome becomes a scoped task graph.

03Contributor network

Approved participants claim work or sponsor authorized capacity.

04Reviewed work

Tests, review, and an explicit Acceptance Event preserve the result.

05Commercializable platform

The strongest work can compound into products the Company may test and commercialize.

THE COORDINATION LESSON

Bitcoin coordinated compute. Relay coordinates useful AI work.

Bitcoin demonstrated that independently owned compute can coordinate around shared rules and verification. Relay borrows that coordination idea for useful project work: independently authorized AI capacity and human judgment complete scoped tasks that must pass review.

Capacity + judgment→Scoped task→Verification→Accepted work

Relay is not a blockchain, cryptocurrency, token, investment, or financial network. Contribution records do not promise returns.

FUTURE PROGRAM INPUT / NOT ACTIVE

Helping the network grow is another form of contribution.

Introductions can be recorded as factual evidence that someone helped the collective expand. DSPY GROUP may consider that history, alongside direct work and other evidence, only if a future participation program is formally approved.

INTRODUCTION SOURCE Participant B introduced Participant D Factual attribution · correctable · no current economic effect

No current credit, percentage, commission, or compensation is created. Work attribution stays with the person who did the work. Any future program requires Company authorization, a documented review, new governing documents, and fresh assent.

08 / WHY RELAY COMES FIRST

THE STRATEGIC BET

Build one company first, and the immediate result is one company.

Build Relay first, and each company after it can begin with shared infrastructure for planning, execution, review, governance, and evidence.

DSPY RELAYShared engineering control planeKnowledge · policy · work graph · evidence

COMPANY01One isolated build

COMPANY02Rebuilds coordination

COMPANY03Rebuilds coordination

COMPANY04Rebuilds coordination

Twenty separate workflows create effort, but little shared operating leverage.

“We are not starting by choosing one company. We are starting by increasing the group’s ability to build every company that comes next.”

09 / FROM PROTOTYPE TO COMPOUNDING

Relay is the starting gun, not the finish line.

The ambition is large. The current state is specific: a design-grade prototype and technical starter, moving toward an internal control plane with mock-first execution.

PROTOTYPED What exists today

Interactive control-room concept
Task-graph and worker onboarding UX
Protocol and adapter scaffolding
Security and compliance architecture

PLANNED NEXT Phase 1 implementation target

Authenticated control plane
Signed dispatch and worker identity
Mock execution and audit trail
Task lifecycle and approval gates

LONG-TERM VISION What Relay can become

Persistent multi-project orchestration
Documented multi-provider authorization paths
Review-to-remediation loops
Infrastructure for launching companies

PHASE 01Build RelayCreate the shared engineering organization.

PHASE 02Use RelayImprove it by building real things together.

PHASE 03Build companiesLaunch the strongest participant ideas through it.

PHASE 04CompoundReuse what each project teaches the next.

DSPY GROUP / RELAYREQUESTS OPEN · ACCESS REVIEWED

Bring your capacity. Help build what comes next.

Request access to contribute product judgment, engineering skill, domain expertise, review capacity, or independently authorized AI capacity to scoped DSPY GROUP work. No invite code needed; every request is reviewed by a person.

Request collective access

Submitting a request does not guarantee approval, project access, work, compensation, or any future award.

FIRST, BUILD RELAY.THEN, BUILD THE COMPANIES.