Scion Core
Define responsibilities. Run agents. Delegate, communicate, and share the work.
Define
Agent Templates
Run
Sandbox Runtimes
Spawn
Adaptive Teams
Notify
Reactive Wakeups
Sync
Shared Filesystem
Agent Definition
Combine reusable instructions, skills, and tools to give each agent a clear purpose.
1. System Instruction
Define the agent's purpose and responsibilities, from research and implementation to independent review.
2. Agent Instructions
Describe how the agent works with its team. Scion adds context about the workspace and available capabilities.
3. Agent Skills
Give agents reusable procedures and tool guidance. Publish and version skills through the Skill Bank and connected registries.
4. Model Context Protocol (MCP)
Connect external tools and data through MCP server configuration for supported harnesses.
Agent Runtime
Give agents a working environment, then choose where it runs: a laptop, a remote machine, or cloud infrastructure.
- Agent Lifecycle: Create, start, stop, and inspect agents through a common CLI. Attach to supported interactive sessions.
- Runtime Choice: Run on Docker, Podman, Apple Container, Kubernetes, or Cloud Run.
- Working Environment: Configure each agent's tools, environment, credentials, and workspace sharing.
- Hosted Controls: Use roles, access boundaries, scoped secrets, and federated identity as the team grows.
Agent Collaborators
Teams of humans and agents work toward a shared goal. Instructions guide how they delegate, exchange findings, and ask for help.
- Adaptive Teams: Authorized agents use the
scionCLI to create and manage collaborators as new tasks emerge. - Shared Conversations: Exchange messages, mentions, and attachments through web chat and connected chat services.
- Human Participation: Answer questions, redirect work, or join an interactive harness session.
- Visible Progress: Follow agent activity, inspect logs, and trace who delegated work to whom.
Agent Notifications
Let work proceed asynchronously, with notifications that bring collaborators back when they are needed.
- Progress Signals: Agents report when they are working, blocked, finished, or waiting for input.
- Delegation: A parent can wait for a child task and continue when a notification arrives.
- Subscriptions: Route completion, stall, and input requests to the collaborators who need them.
- Human Attention: Surface requests for help through the web UI and configured chat integrations.
Shared Filesystem
Give agents a place to exchange code, research, and artifacts. Choose what they share and where they work independently.
- Workspace Choice:
- Use a shared workspace, separate Git worktrees, or independent clones to match the project.
- Context by Reference:
- Share artifact paths so collaborators can read what they need when they need it.
- Shared Notes:
- Keep findings, handoffs, and progress summaries in project shared directories.
- Explicit Coordination:
- Use team instructions to establish file ownership and coordinate overlapping edits.
Scion Orchestration Review
Combine these building blocks to explore your own collaboration patterns, from a pair of specialists to a changing team.
1. Define
Give each agent a purpose with reusable instructions, skills, and tools.
2. Run
Choose a runtime and configure each agent's environment and credentials.
3. Spawn
Delegate to specialists and exchange findings as the work develops.
4. Notify
Bring collaborators back when tasks finish or an agent needs help.
5. Sync
Share artifacts and notes, with workspace boundaries chosen for the project.