# JoyStream > The operating system for Organizational Agents. Turn organizational work into software-defined Capabilities that human and Agent teams can build and evolve—without creating another engineering project. - Join the waitlist: https://joystream.ai/#waitlist - Talk to the founders: https://calendar.app.google/7CzCYKRzBBcQLZfA8 - Read the docs: https://docs.joystream.ai --- ## Daily GitHub Change Summary (example) Review every GitHub change and deliver a daily summary to the team. GITHUB CHANGES → JOYSTREAM RUN → SLACK SUMMARY 1. Changes land in GitHub. 2. The Run executes. 3. The team reads it in Slack. --- ## Start with the work **What does your organization need to do better?** Getting an Agent to work once is not the hard part. The hard part is turning that result into work the organization can authorize, repeat, improve, and own. That enduring organizational ability is a Capability. JoyStream turns that ability into software built and operated by people and Agents together. > Agents are implementations. Capabilities are what your organization improves. Example Capabilities: - Qualify every inbound lead - Launch every campaign consistently - Onboard every employee - Prepare every customer renewal - Investigate every escalation - Close the books on time Start with the Capability—not which Agent to build. --- ## From idea to Capability **Turn an idea into an approvable Capability—without waiting for engineering.** Today, leaders often face a false choice: let business teams move quickly with opaque Agents, or turn every idea into an engineering project. Describe the work in chat. JoyStream returns a Spec and a reviewable Recipe, then lets you test the proposed actions against simulated systems before granting live access. The people who understand the work can inspect the implementation, refine it, and decide whether it should proceed. --- ## The Capability lifecycle **From business intent to an owned, evolving Capability.** Before a Capability operates, you need to see what it is responsible for, how it will act, which systems it can access, and where its authority ends. - **Build** — Turn business intent into a structured Capability. - **Inspect** — Review its proposed behavior, implementation, access, and boundaries. - **Approve** — The work owner decides whether the Capability can advance through Dry Run, Pilot, and Live operation. The decision is recorded. - **Audit** — See what happened across every execution. - **Own** — Keep the Capability, its approvals, Runs, and evidence as an organizational record. - **Evolve** — Update its Spec and Recipe as the organization, tools, models, and Agents change. Three durable artifacts span the lifecycle: - **Spec — the contract.** Defines what the Capability must accomplish, its boundaries, and how success will be judged. - **Recipe — the plan.** Makes the proposed implementation explicit: the Agents, tools, access, approvals, and sequence of actions. - **Run — the record.** Preserves what actually happened: the inputs, decisions, actions, outputs, and evidence. The Spec is the contract. The Recipe is the plan. The Run is the record. --- ## Progressive authority **Increase authority as evidence accumulates.** A Capability should not move directly from creation to unrestricted operation. JoyStream lets your team test it, constrain it, and expand its authority deliberately. - **Dry Run** — Examine how the Capability would behave against simulated systems without granting it live authority. - **Pilot** — Run against real systems using test data, limited scope, and recorded approvals. - **Live** — Operate on real work with the authority your organization has explicitly approved. Dry Run → Pilot → Live. Start safely. Expand deliberately. Audit every Run. --- ## Human + Agent workspaces **Bring the people, Agents, and access behind the work into one Workspace.** A Workspace is the operating home for a defined body of work. It brings together the people responsible for it, the Agents performing it, and Vaults that scope the credentials those Agents can use. Example Workspaces: Marketing Operations · Revenue Operations · Customer Success · Finance Operations. One Workspace. Shared context. Scoped access. --- ## Ownership and evolution **The Agent may change. The Capability remains yours.** The Capability is not tied to a single Agent implementation. As Agents, models, tools, and Recipes change, the definition of the work and its operating history remain centered on the Capability. Review what happened, refine the definition, update the implementation, and operate the next iteration without starting over. Review → Refine → Update → Run again. Each Run becomes part of the Capability's history. --- ## Get started **What Capability does your organization need to improve first?** Describe the work your team needs to improve and join JoyStream as a design partner to help shape how that work becomes an inspectable, approvable Capability. - Talk to the founders: https://calendar.app.google/7CzCYKRzBBcQLZfA8 - Join the waitlist: https://joystream.ai/#waitlist